Thanks for this response Murray. It pointed out why I was uncomfortable with
the term, but was not directly thinking about; the differences in processing
DBCS versus Unicode characters.
A lot of people think that Unicode -IS- a DBCS, so I didn't really want to
leave it the way it was.
I wonder if "multibyte enabled" has the same connotations of processing
differences? A few people have suggested this as an acceptable option, but
now I'm trying to think back about whether there are processing methods for
MBCS that are similar to the old DBCS methods?
"Unicode enabled" is probably the clearest term, but I would appreciate
comments on historic use of "multibyte enabled".
----- Original Message -----
From: Murray Sargent <email@example.com>
To: 'Suzanne Topping' <firstname.lastname@example.org>
Cc: Unicode List <email@example.com>
Sent: Wednesday, April 05, 2000 6:14 PM
Subject: RE: Double Byte enabled
> "Double-byte enabled" is very different from "Unicode enabled". The
> refers to apps that can navigate, maybe edit, and display DBCS text such
> Shift-JIS. Typically the ASCII characters in a DBCS character repertoire
> are represented by single bytes and most, if not all, other characters are
> represented by a lead byte followed by a trail byte. So you have a mix of
> single and double byte characters. It gets particularly tricky, since
> lead bytes can also be trail bytes. Accordingly if you land in the middle
> of the text it can be tricky to figure out where a character boundary is
> (finding it used to be a favorite interview question at Microsoft).
> In your document, it would be better to say something about making sure
> applications are Unicode enabled. Double-byte enabling used to be
> desirable, but now it should only be needed for import/export code.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:00 EDT