characters alone isn't enough... is that on the right
track?
Best regards,
Gary
At 02:00 AM 11/21/2002 , Joseph Boyle [EMAIL PROTECTED] wrote:
The page already has the corrected appearance when I view it on IE6 /
XP, but the incorrect appearance on IE5.5 / NT4. I am guessing that his
Windows
Working in a large organization whose product includes a large number of configuration
and data files in text formats, I can say something about what we have found to work
during development, localization, and release engineering, across multiple platforms .
We have eliminated UTF-16 text file
To: Doug Ewell; Unicode Mailing List
Cc: Murray Sargent; Joseph Boyle
Subject: Re: Names for UTF-8 with and without BOM
Little probability that right double quote would appear at the start of a
document either. Doesn't mean that you are free to delete it (*and* say that
you are not modifying
in an argument separate from the charset name?
As said before this unnecessarily requires extra logic.
Joseph
-Original Message-
From: Michael (michka) Kaplan [mailto:michka;trigeminal.com]
Sent: Monday, November 04, 2002 7:23 AM
To: Joseph Boyle; Unicode Mailing List
Subject: Re: PRODUCING
Yes, it's trivial to check. What's missing is the notation to tell the
checker what to check for.
Sorry, but that is incorrect. If they know its UTF-8, then its either a BOM
or its not. It is three specific bytes.
No, the notation to say BOM required (report any files without BOM), BOM
not
The first time I thought of UTF-8Y it sounded too flippant, but actually it
is fairly self-explanatory if UTF-8 is taken as a given, and has the virtue
of being short.
UTF-8S for signature would also make sense, but is the same as the name of
Toby Phipps's proposal which eventually became CESU-8.
-
From: Michael (michka) Kaplan [mailto:michka;trigeminal.com]
Sent: Saturday, November 02, 2002 10:16 AM
To: Joseph Boyle; Mark Davis; Murray Sargent
Cc: [EMAIL PROTECTED]
Subject: Re: Names for UTF-8 with and without BOM
From: Joseph Boyle [EMAIL PROTECTED]
Type Encoding Comment
.txt UTF-8BOM
It would be useful to have official names to distinguish UTF-8 with and
without BOM. (or, with, without, and agnostic) Here are a couple of examples
I'm currently involved with:
* I'm writing an encoding checker to validate a long list of text file
formats we use internally. HTML and XML only
8 matches
Mail list logo