> Again, does anybody really advocate three different forms of UTF-16 for
I have looked upon the registration of UTF-16LE, UTF-16BE as a pre-emptive
strike against teeming hordes of anarchist loonies who persist in registering
loads of what Ken has so charmingly deemed "c**p".
Personally, I advocate big-endian interchange only, since that is already
de-facto Network byte order. However... SOME people apparently wish to
interchange -- or at least unambiguously IDENTIFY -- UTF-16 data that is NOT
in big-endian order. It is better to register three related keys correctly
than to allow some random anarchist to come in and register something similar
but not quite what we wanted later on.
Or is there some magic way of preventing unwanted things from being
registered (and used) over good objections?
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:51 EDT