[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Display types?
>>>>> "Ben" == Ben Laurie <firstname.lastname@example.org> writes:
Ben> Paul Koning wrote:
>> >>>>> "Ben" == Ben Laurie <email@example.com> writes:
Ben> I don't get it either, but in my case its because I thought
Ben> Unicode allowed either byte order, and which you are using is
Ben> obvious because of the leadin character (0xfffe).
>> Right. That's a typical bad committee solution to the problem.
>> The right solution is to fix the order, that way only half the
>> platforms have to do extra work rather than all the platforms
>> having to do twice as much extra work.
>> Imagine how poorly the internet would run if TCP had the byte
>> order in its headers selected by the first byte of the header.
>> Even OSI never did that...
Ben> That's as may be, but Unicode did.
Right. And that's why it's bad news. For that reason it should not
If you use the fix Niels suggested (i.e., require only one of the two
byte orders to be used) that's different. If you do that then you
have a sensible encoding, the main remaining drawback then is that
it's different from what all other protocols are using.