A. Vine wrote:
FYI, we are well aware of this shortcoming (modified UTF-8), and with
each release try to mitigate it even further. The problem is that it is
so deep in the code (note that it is since Java 1.0) that it is not easy
to eliminate without breaking a lot of existing stuff, something
http://www.nytimes.com/2004/11/12/international/africa/12africa.html?ex=1101365144ei=1en=b4b60fe9706acc9b
http://www.nytimes.com/2004/11/12/international/africa/12africa.html?ex=1101365144ei=1en=b4b60fe9706acc9b
Eric.
Theodore H. Smith scripsit:
I'm just curious about the \0 thing. What problems would having a \0 in
UTF-8 present, that are not presented by having \0 in ASCII? I can't
see any advantage there.
AFAICT it was a hack so that arbitrary Java strings could be encoded
as C strings; that is, with
The article describes efforts to create a Yoruba keyboard:
To accomplish the same result with fewer, more comfortable keystrokes,
Mr. Adegbola made a keyboard without the letters Q, Z, X, C and V,
which Yoruba does not use. He repositioned the vowels, which are high-
frequency, to more
I babbled incoherently:
I'll bet the folks at Bisharat and elsewhere would be surprised at
the efforts that have been made to create keyboards for Yoruba.
Should have been more like:
I'll bet Mr. Adegbola would be surprised at the efforts that have been
made by the folks at Bisharat and
From: A. Vine [EMAIL PROTECTED]
I'm just curious about the \0 thing. What problems would having a \0 in
UTF-8 present, that are not presented by having \0 in ASCII? I can't see
any advantage there.
Beats me, I wasn't there. None of the Java folks I know were there
either.
The problem is in the
6 matches
Mail list logo
