RE: Unicode in source

From: Chris Pratley (
Date: Sat Jul 24 1999 - 03:08:25 EDT

FWIW, Word2000 also imports/exports Big-Endian Unicode plain text. If the
incoming file is Big-Endian, that is preserved when the file is next saved
as Encoded text, and the BE BOM is written. Internal storage is still
Little-Endian of course, for performance reasons.

-----Original Message-----
From: F. Avery Bishop []
Sent: Friday, July 23, 1999 11:57 AM
To: Unicode List
Subject: RE: Unicode in source

On Windows 2000 with notepad you can choose to save a file as Big-Endian
Unicode. When you reopen the file, it will recognize the format and handle
it correctly. Thereafter, it will save that file in big-endian format by
default unless you override it.

I wouldn't want to use notepad for programming, but I wrote my first Windows
programs (including the rc file!) eons ago using emacs and nmake. Oh, for
the good ol' days :-) .

F. Avery Bishop

-----Original Message-----
From: John Cowan []
Sent: Friday, July 23, 1999 10:24 AM
To: Unicode List
Subject: Re: Unicode in source

Rick McGowan wrote:

> John Cowan wrote:
> > Yes, sorry, WinNT supports UTF-16-LE, and writes a correct BOM,
> > (first two bytes are FE FF), but it will not process UTF-16-BE
> > even *with* a correct BOM; it assumes the local code page instead.
> Huh? {FE,FF} is a big-endian BOM. {FF,FE} would be a little-endian BOM.
> Which is it really?

I die. My bloated and stinking corpse is belatedly found buried under
a terabyte database. It corrupts the database. The database corrupts
the entire world. All die. O, the embarrassment.

(In other words, Rick is right and I am wrong.)

        John Cowan
Schlingt dreifach einen Kreis um dies! / Schliesst euer Aug vor heiliger
Denn er genoss vom Honig-Tau / Und trank die Milch vom Paradies.
                        -- Coleridge / Politzer

This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:50 EDT