Patrick Andries wrote:
Latin numerals are not based on the position of the letter in
the alphabet, contrarily to Greek for instance.
Latin numerals are not based on the first letter of the word
they represent, with the exception of C and M, perhaps (*).
...
(L, for instance was
Dean Snyder scripsit:
What are the properties which will trigger separate Unicode encodings for
characters typically or always represented by identically shaped glyphs?
Well, whyn't you say so?
The normative ones, exactly and precisely. Casing is normative, so
if language A claims that
At 05:34 AM 11/21/2002, Gary P. Grosso wrote:
As this will likely come up in my line of work (tech support and
troubleshooting for products which, among other things, export HTML),
I would be interested in any more detail/explanation (or pointers to
such) about using Uniscribe for complex text
On 2002.11.19, 13:50, Marco Cimarosti [EMAIL PROTECTED]
wrote:
(Thinking of it, this is the probably also the reason why Roman
numerals in page numbers are lowercase: to avoid confusing pages I and
II with pages 1 and 11.)
At least in Portugal, roman numbers are *never* lower case.
--
On 2002.11.18, 10:44, Otto Stolz [EMAIL PROTECTED] wrote:
I was under the impression that all three Morse code elements are
already in Unicode:
U+00B7
U+2013
U+0020
For context:
_
Date: Tue, 23 Jul 2002
The same is true for M which had, amongst its many early
forms, a form close
to (I), [...]
Cf. U+2180 in http://www.unicode.org/charts/PDF/U2150.pdf.
Note that V is half an X (the upper half),
L emerged from half a C (the upper half of its original form),
D is half a U+2180 (the
Stefan,
The point that I was making was not to actually encode Unicode in Morse but
to make people think of Unicode in a different light. Morse code is a
different media and its purposes are different from most applications that
employ Unicode.
Mapping between Morse and Unicode is like
Anto'nio Martins-Tuva'lkin posted:
Note that a more or less correct (content) display of the morse symbols
depends on the typeface used (presentation), and probably this should
not be so.
Normally Morse code appears in text through a cypher font containing
complete sets of dots and dashes
At 18:29 + 2002-11-21, Anto'nio Martins-Tuva'lkin wrote:
On 2002.11.19, 13:50, Marco Cimarosti [EMAIL PROTECTED]
wrote:
(Thinking of it, this is the probably also the reason why Roman
numerals in page numbers are lowercase: to avoid confusing pages I and
II with pages 1 and 11.)
At
The point that I was making was not to actually encode Unicode in Morse but
to make people think of Unicode in a different light. Morse code is a
different media and its purposes are different from most applications that
employ Unicode.
Mapping between Morse and Unicode is like translating
Firstly, thanks to all who answered so far.
Kenneth Whistler wrote:
Because oldstyle numerals aren't really lowercase in the same
sense as small letters (though some typographers think of them that
way; see[1]). They're just glyph variants of the uniform-height
lining numerals, so yeah,
Changing IE6's Devanagari font from Mangal to Arial Unicode MS breaks reordering on my
XP, so it looks like the main issue is presence of OpenType reordering info in the
font, and not Uniscribe. Arial Unicode MS does not appear to be an OpenType font.
Uniscribe is included with IE 5.0 and
Earlier today Andy White asked:
Is the Unicode FAQ officially part of the Unicode standard?
Since nobody else has picked this up, I'll venture an answer. The answer
is no. The FAQ pages are not part of the standard.
If not why not?
The FAQ pages are interpretations of the standard about
Rick investigated, and came up with:
In a specific case, Andy asked about Khanda Ta, and pointed to a WG2
resolution that contradicts the Unicode FAQ on the same topic. I looked up
a paper listing an action item as follows, taken from document
Dear Folks,
Let me tell you my experience of Hindi language with the MS Sql 2000, MS
Access 2000, MS Word 2000 and Outlook express.
My system is running on Windows 2000 Professional. I have installed the
Indian languages patch provided with the Windows 2000 OS.
When I use the Hindi Tradition
At 08:55 PM 11/21/2002, [EMAIL PROTECTED] wrote:
It does not waste any space. but when I use the language in MS Access and MS
word 2000, I get like this रा जे श
It gets one space after each hindi letter.
What could be the problem with Access and Word?
This is a known issue in Office 2000
Anto'nio Martins-Tuva'lkin antonio at tuvalkin dot web dot pt wrote:
BTW, which characters should be used to encode the dot and dash of
Morse in a typographically correct way?
...
It looks best on some rounded fonts, like Vag. But in regular fonts
(both sans and serif) a middle dot and a
Thomas Lotze thomas dot lotze at uni dash jena dot de wrote:
So can it be summarized that figures (both arabic and latin) actually
come in only one flavor (upper or lowercase), the other being a
variant glyph, and both kinds of roman numerals being encoded for
reasons other than their
Now, what should I do to fix this bug in my system by using the Windows 2000
OS?
Rajesh
- Original Message -
From: John Hudson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, November 22, 2002 10:37 AM
Subject: Re: Anyone who can write Hindi on the Unicode List?
19 matches
Mail list logo
