-BEGIN PGP SIGNED MESSAGE-
Lars Kristan wrote:
John Cowan wrote:
Frankly, your problem is insoluble, because you have set up
self-contradictory requirements. Suppose you are dealing with a
filesystem where some names are to be interpreted as Latin-1 and others
as Latin-2. The
-BEGIN PGP SIGNED MESSAGE-
Lars Kristan wrote:
Doug Ewell wrote:
fine (as are LF-CRLF, stripped BOM's, and maybe even some edge cases
like converting between tabs and spaces). If there are any
security or spoofing concerns, it's best to leave everything completely
untouched.
At 09:52 PM 2/18/02 -0800, Doug Ewell wrote:
So if some language turns out to need
a with horn in the future, its readers will have to cross its fingers
that rendering engines become capable of displaying U+0061 U+031B
properly.
Support for such arbitrary combination is apparently in the works
David Hopwood scripsit:
(I've just checked whether NTFS allows ill-formed UTF-16 filenames; it does,
at least on NT4.0, but you could reasonably treat that as an error.)
NTFS filenames are UCS-2, not UTF-16, so ill-formed has no meaning.
--
John Cowan http://www.ccil.org/~cowan
Omotola A. Awofolu wrote:
- I do not know how to use diacritics in either JAVA or XML, and for
coding with Yoruba I need to be able to use diacritics for
some of the characters
To use Unicode combining diacritics, you simply put the required
diacritic(s) AFTER the base letter. So, say that
Could I ask that discussion on language names be confined just to the
lists _other_than_ [EMAIL PROTECTED], to avoid multiple postings?
Examples are recent postings on names of various Sami (or Saami)
languages.
It is already widely discussed on [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL
On Monday, February 18, 2002, at 10:52 PM, Doug Ewell wrote:
In the '90s, when UTC and WG2 were more open to encoding precomposed
forms, this approach was not too problematic, since any legitimate
diacriticized character in an alphabetic script probably had its own
precomposed form. Today,
-BEGIN PGP SIGNED MESSAGE-
John Cowan wrote:
David Hopwood scripsit:
(I've just checked whether NTFS allows ill-formed UTF-16 filenames;
it does, at least on NT4.0, but you could reasonably treat that as
an error.)
NTFS filenames are UCS-2, not UTF-16, so ill-formed has no
Asmus Freytag [EMAIL PROTECTED] wrote:
So if some language turns out to need
a with horn in the future, its readers will have to cross its fingers
that rendering engines become capable of displaying U+0061 U+031B
properly.
Support for such arbitrary combination is apparently in the works
Doug Ewell wrote:
[...]
And judging from Marco's unrelated post about Yoruba q-tilde,
in which I
*did* see the tilde positioned correctly (more or less) over the q, I
guess support is more advanced than I thought. Terrific.
Probably you didn't mean this, however: I don't think that q with
Marco Cimarosti [EMAIL PROTECTED] wrote:
And judging from Marco's unrelated post about Yoruba q-tilde,
in which I
*did* see the tilde positioned correctly (more or less) over the q, I
guess support is more advanced than I thought. Terrific.
Probably you didn't mean this, however: I don't
At 17:38 +0100 2002-02-19, Keld Jørn Simonsen wrote:
You might care to have a look at the following URL:
http://www.iso.org/iso/en/commcentre/pressreleases/2002/Ref815.html
where information on the ISO/IEC JTC 1 Marketing trial may be found.
CHF 44.00 is EUR 29.74 is USD 25.89
I note with
Can someone on the list help me respond to this query. Thanks.
Magda.
-Original Message-
From: Kevin Brown [EMAIL PROTECTED]
Date: 2002-02-18 21:05:52 -0800
To: [EMAIL PROTECTED]
Subject: list of abbreviated character names
Hello
I work professionally with type and am constantly using
I am desperately looking for a list which gives NOT the full character
description given in the Names List (eg LATIN CAPITAL S WITH CARON) but
the abbreviated name (eg Scaron)
This extremely useful shorthand method of naming the glyphs is used in
font-editing applications such as
Lars Kristan wrote:
...
The same thing should work the other way around, store Windows filenames
directly into a UTF-16 database and use UTF-8 = UTF-16 conversion for UNIX
filenames. Hoping that some day most of the data will be UTF-8 makes this
even more appealing. As for any data that is
What you are looking for is the mapping of Adobe PS glyph names to Unicode
characters. This is contained in a document called the Adobe Glyph List,
which can be found online along with Adobe's extended glyph naming rules at
http://partners.adobe.com/asn/developer/type/unicodegn.html
-Original Message-
From: george lingas [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 19, 2002 2:10 AM
To: Magda Danish (Unicode)
Subject: RE: unicode_help
Dear Magda Danish,
Thank you very much for your help,
but i still cant find the unicode standart for symbols
such as oxia
George,
Polytonic Greek is a complicated issue, mainly because of the distinction
between combining diacritical marks (which most software today doesn't
support well) and precomposed combinations of letters and marks. If you
looked on the Unicode website under the Greek range you didn't find
At 08:13 AM 2/19/02 -0800, Doug Ewell wrote:
Asmus Freytag [EMAIL PROTECTED] wrote:
So if some language turns out to need
a with horn in the future, its readers will have to cross its fingers
that rendering engines become capable of displaying U+0061 U+031B
properly.
Support for such
Greetings,
I just noticed that utf-8 encoding is finally working at hotmail.
UTF-8 works in the subject as well as the body of a letter. Late
last year I saw that UTF-8 would not display properly at hotmail,
even when the letter body was HTML with the encoding set right.
Anyone here know for
Perhaps that was true of NT4. On WindowsXP NTFS uses UTF-16 - it handles
Extension B filenames just fine.
Chris
Sent with OfficeXP on WindowsXP
-Original Message-
From: John Cowan [mailto:[EMAIL PROTECTED]]
Sent: February 19, 2002 5:04 AM
To: David Hopwood
Cc: [EMAIL PROTECTED]
Even better, use Word2002 and get all that, plus the ability to *edit*
the file and then save it back in any encoding, controlling CRLF/LF/CR
or whatever...
Actually, this problem of remembering encoding is not specific to
notepad - it happens for any text editor. The issue is that often the
22 matches
Mail list logo
