> Frank, may I suggest you either put down the enormous weight of that chip
> on your shoulder, or submit this theory to the Weekly World News? We are
> all trying to get Unicode implemented here, so the constant implication of
> evil intentions gets a little tiresome after awhile.
>
I agree. And pointless too. CP1252 is everywhere; Microsoft has indeed
"created a fact". But I'm not here to indict Microsoft. I'm here to stick
up for standards, such as the one all of us are working on together.

I'm happy if this discussion has given pause to any readers who honestly did
not even KNOW that CP1252 was NOT a standard, or that there might be
anything
wrong with putting it -- or any other private character set (or document
format, etc) -- on the Internet.

> Ironically, for some reason it is from the Unix user group from which we
> have to take the most guff.
>
Like me? I'm a Windows developer! But I develop software for Windows that
accesses non-Windows platforms such as Unix, VMS, VOS, and IBM mainframes
using open, standard methods and formats such as ISO 2022, ISO 8859, and
UTF8 (not to mention TCP/IP and Kerberos).

The Unix group, by and large, is just as committed to UTF8 as Microsoft and
Apple, but doesn't have the same resources or degree of organization.
Perhaps more to the point, it has to spend inordinate amounts of time on
detours to accommodate PC code pages all over the Internet instead of moving
straight ahead to Unicode.