Asmus Freytag wrote:
From: [EMAIL PROTECTED]
[...]
we are a manufacturer of time and attendance terminals which
aretransfering data using 8-Bit character streams
[...]
Now here is my question: Is there a method to add any
Unicode character to a 8-Bit ASCII stream?
[...]
There are
New WG2 documents are available:
N2410 Revised proposal to encode the Limbu script in the UCS.
http://www.dkuug.dk/jtc1/sc2/wg2/docs/n2410.pdf
(This document provides corrections to the Limbu set under ballot)
N2411 Proposal to add two Greek letters for Bactrian to the UCS.
At 02:24 -0500 2002-02-06, [EMAIL PROTECTED] wrote:
ISO keyboards have the section-sign (§) key, next to the 1 key
above the tab key on the left of the keyboards. Some US keyboards
(for instance the Mac PowerBook G3) don't have this key, but instead
have the grave key there, while on the ISO
Found that somewhat old e-mail from Clive, but the web site is still there
...
Good luck
Arnold
-Original Message-
From: Hohberger, Clive [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 5:34 AM
To: '[EMAIL PROTECTED]'
Subject: Bar codes using unicode
Speaking as a member of the
Here is a summary of all the answers I received to my historical
questions.
Sorry for the length of this post, but I think that many people will find
this worth reading. Thanks again to all the people who took the time to
reply.
_ Marco
--- --- --- ---
Q: When did the Unicode project start,
Thanks, Arnold.
Good time for an update...
The public domain specification (an AIM International Technical Standard)for
black/white Ultracode(R) will be released sometime this year, probably
around 4Q2002. We will have prototype encoding (UTF-8 to symbol graphic) and
codeword-to-UTF-8 software
JC It's pretty much a given that a normalization form that meddles with
JC plain ASCII text isn't going to get used.
I had to think about it, but it does makes sense.
JC The U+1Fxx ones are the spacing compatibility equivalents,
Compatibility who with?
Thanks a lot for the explanations.
KW There is no good reason to invent composite combining marks
KW involving two accents together. (In fact, there are good reasons
KW *not* to do so.) The few that exist, e.g. U+0344, cause
KW implementation problems and are discouraged from use.
What are
Apple calls what I have on my desk an ISO extended keyboard. It came
with my Cube. It has the section key next to the 1, and the grave key
next to the z. My Powerbook has the grave key next to the 1, and no
key next to the z.
--
Michael Everson *** Everson Typography ***
Here is the response I got from the Cherokee Nation, to whom I cc'd my
original question about the Cherokee accent mark.
So, is this a candidate for encoding?
-8-begin forwarded message-8-
The accent is to be used on the syllable with the accent when pronouncing
the word,
In a message dated 2002-02-06 3:39:14 Pacific Standard Time,
[EMAIL PROTECTED] writes:
ISO keyboards have the section-sign (§) key, next to the 1 key
above the tab key on the left of the keyboards. Some US keyboards
(for instance the Mac PowerBook G3) don't have this key, but instead
At 12:01 -0500 2002-02-06, [EMAIL PROTECTED] wrote:
Here is the response I got from the Cherokee Nation, to whom I cc'd my
original question about the Cherokee accent mark.
So, is this a candidate for encoding?
I think I'll talk to her and see.
--
Michael Everson *** Everson Typography ***
Hello,
Mark Davis and I developed a concrete, MIME-friendly version of the BOCU algorithm
that we presented earlier
(http://oss.software.ibm.com/icu/docs/papers/binary_ordered_compression_for_unicode.html).
We have a summary and spec with sample code at
On Wednesday, February 6, 2002, at 11:12 AM, Lars Kristan wrote:
Maybe digitally signed messages and bank accounts are not that good of an
example, since people would be more careful there. Another case where this
may get exploited will be domain names, once Unicode is allowed there.
While
The slides from the IUC20 talk titled Querying XML Documents,
given by Paul Cotton and Jonathan Robie, are now available at:
http://www.w3.org/2002/01/xquery-unicode.pdf
Misha Wolf
-- --
Visit our Internet site at
Well, I was tempted to join the discussion for a while now, but one of the
things that stopped me was that I didn't quite understand why it was so
focused on the bidi stuff.
To make a certain portion of the text look like something else should be
easier than that. OK, invisible non-spacing
Juliusz continued:
KW There is no good reason to invent composite combining marks
KW involving two accents together. (In fact, there are good reasons
KW *not* to do so.) The few that exist, e.g. U+0344, cause
KW implementation problems and are discouraged from use.
What are those
Well, nothing wrong with Unicode of course. Just means that there will
need
to be an option in your browser to reject any site without a digital
certificate, and perhaps it will need to be turned on by default. So,
Nothing prevents sites running frauds to get a certificate matching their
On Wed, Feb 06, 2002 at 07:12:19PM +0100, Lars Kristan wrote:
Well, I was tempted to join the discussion for a while now, but one of the
things that stopped me was that I didn't quite understand why it was so
focused on the bidi stuff.
Because it can have a dramatic effect, whereas changing
At 11:54 AM 2/6/2002 -0700, John H. Jenkins wrote:
The original focus was on digital signatures, and I still don't get the
objection. Because I don't know *precisely* what bytes Microsoft Word or
Adobe Acrobat use, do I refuse to sign documents they create? Is that the
idea? I mean, good
The ALA/LC romanization tables ar at: lcweb.loc.gov/catdir/cpso/roman.html
( not .../romanization.html as in my earlier note)
Sorry,
Jim Agenbroad ( [EMAIL PROTECTED] )
It is not true that people stop pursuing their dreams because they
grow old, they grow old because they
Wednesday, February 6, 2002
The scanned pages of the 1997 ALA/LC romanization tables are now available
on the Web: http://lcweb.loc.gov/catdir/cpso/romanization.html
Note that in lieu of the Wade Giles pages there is a note that pinyin
guidelines are
-BEGIN PGP SIGNED MESSAGE-
Kenneth Whistler wrote:
... See CompositionExclusions.txt, which
has a special section mentioning just these four oddballs:
#
# (4) Non-Starter Decompositions
# These characters can be derived from the
23 matches
Mail list logo
