Re: HTML - i18n / NCR & charsets

# Some possible solutions are proposed:

If people have old documents with illegal numeric character references
references. All of your proposed solutions are inferior.

can use content negotiation based on the user agent string:

- send old ("illegal numeric character references") to browsers that
  can't handle I18N but can display windows codepage (this is a
  relatively small subset of deployed browsers, e.g., old
  versions of MSIE on windows only )

- send standards compliant stuff (text/html;charset=iso8859-1) to
  anyone else (including netscape, alis, any browser on a platform
  that doesn't support windows codepage, robot & search engines,
  unix, newer versions of windows).

characters really annoying since they don't display properly anyway.

# target charset change (i.e in Unicode rather than the announced