Will the Unicode bar codes have a built-in encoding so you won't have to waste your
time trying to tell big-endian from little-endian or UTF-8 or whatever?
I mean, if I have a $B2V(B, is it just "a $B2V(B is a $B2V(B is a $B2V(B" or
do I need extra info to tell it's not a $B@P(B or so
In Chinese, I think 100 is $B0lI4(B ("one hundred"), whereas in Japanese 100 is just
$BI4(B ("hundred"). And in Japanese, zeros are not used when writing numbers a
certain way: 205 is $BFsI48^(B, not $BFsI4Nm8^(B, although it can be $BFs!;8^(B.
This is why to me the HTML option "number
All my fault?
IE consistently garbles the XML in its error messages (it was garbled on
previous versions as well). Look at the XML line itself, which I had
included below the indented error message, as in my previous messages. I
reproduce it again, for your reading pleasure.
No "illegal value
I tried that, and it now gets further. However, it blows up on a pure UTF-8
version (without the NCRs). I posted that version also on my site so you
can pick it up.
Error message is:
The code is 1D7CF, which is in UTF-8 (according to my converter) F0 9D 9F
8F. Don't know why that particular
I sent out a message earlier on the list. It's at
http://www.macchiato.com/utc/UCD.zip. I put the version without the IE hack
in there too.
Mark
___
Mark Davis, IBM GCoC, Cupertino
(408) 777-5850 [fax: 5892], [EMAIL PROTECTED], [EMAIL PROTECTED]
http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=102
: We are currently under a certain amount of pressure to implement
: ISO 2022 in XTerm. I've been thinking about taking your approach --
: putting a pty within XTerm, and keeping the conversion between
: whatever ISO 2022 subset you're using and Unicode in a separate
: process. It's good to kno
Michel,
I am glad the file is useful. I generated a version without the hack for
IE, and went to the page: http://msdn.microsoft.com/xml/ and downloaded
MSXML Parser 3.0 Service Pack 1 Release, and installed. Rebooted. Tried to
view the UCD.xml file. Got the message: "
> DM> Now, we added UTF-8 support to the ANSI task following the
> DM> ISO-IR 196 specification.
>
I assume we're talking about some kind X-based terminal emulator?
> DM> Does anyone know of any examples of host computers or operating
> DM> systems that actually use UTF-8 on an ISO 6429 impleme
Darren,
DM> Now, we added UTF-8 support to the ANSI task following the
DM> ISO-IR 196 specification.
This is great to hear.
DM> Does anyone know of any examples of host computers or operating
DM> systems that actually use UTF-8 on an ISO 6429 implementation?
Currently, the main application th
On 11/05/2001 03:59 Misha Wolfe wrote:
>The only one I recall is Ultracode. See:
>B3: Ultracode: A Barcode Symbology Encoding Unicode 2.0
> at: http://www.unicode.org/iuc/iuc10/program.html
On 07/05/2001 20:27:28 Markus Scherer wrote:
>
> I seem to remember an email from a while ago (a year or m
10 matches
Mail list logo