Not to mention the annoyance/impracticality of having to manipulate, edit,
maintain, translate, and otherwise use files that consist of an endless
stream of NCRs. Plus, this doesn't solve the "code page of the user"
problem--if the user can't display the character anyway, what good does it
do? ::sigh:: we're back to font support for the character set....
<firstname.lastname@example.org To: "Unicode List" <email@example.com>
n.com> cc: Unicode List <firstname.lastname@example.org>
Subject: Re: Multilingual Documents [was: HTML forms and UTF-8]
Jonathan Rosenne wrote:
> Please note that according the HTML 4 the document character set is
> the full UCS, independent of the character encoding used. Even if the
> document is encoded in ISO-8858-1 or US-ASCII, is can use any character
> the UCS by means of numeric character references (NCRs). I have seen
> consisting entirely of NCRs.
Known, but not usabl. Most of the folks who are our customers' customers
not have HTML 4.0 capabilities, so we cannot code to it. It's coming, but
not there yet.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:56 EDT