On 7/28/2010 9:32 PM, Doug Ewell wrote:
Murray Sargent murrays at exchange dot microsoft dot com wrote:
It's worth remembering that plain text is a format that was
introduced due to the limitations of early computers. Books have
always been rendered with at least some degree of rich text. And
On Wed, Jul 28, 2010 at 11:37:28AM -0700, Asmus Freytag wrote:
On 7/28/2010 10:09 AM, Murray Sargent wrote:
Contextual rendering is getting to be more common thanks to
adoption of OpenType features. For example, both MS Publisher 2010
and MS Word 2010 support various contextually dependent
Persian and Urdu write [g] using a kaf character with a line above U+06AF,
while Pashto uses kaf with a ring U+06AB. It really should be that simple.
I seem to remember, that Persian used kaf with three dots above (like your
Moroccan example) at least in the 19th century. No idea when they
Den 2010-07-29 08.47, skrev Khaled Hosny khaledho...@eglug.org:
I have few fonts where I implemented a 'locl' OpenType feature that maps
European to Arabic digits, and contextual substitution feature that
replaces the dot with Arabic decimal separator when it comes between two
Arabic
On Wed, Jul 28, 2010 at 7:20 PM, Murray Sargent
murr...@exchange.microsoft.com wrote:
Andreas Prilop commented A native speaker of English does not
/automatically/ know better about English grammar, English punctuation than
an informed Frenchman. So true, so true. Most native speakers of English
2010/7/28 Asmus Freytag asm...@ix.netcom.com
On 7/28/2010 9:30 AM, André Szabolcs Szelp wrote:
You really all say, that general property Sk (DOT ABOVE) rather than Po
(FULL STOP, COMMA, MIDDLE DOT) (compared with all other decimal point
characters) can not cause any problems ever in certain
On Thu, Jul 29, 2010 at 10:01:37AM +0200, Kent Karlsson wrote:
Den 2010-07-29 08.47, skrev Khaled Hosny khaledho...@eglug.org:
I have few fonts where I implemented a 'locl' OpenType feature that maps
European to Arabic digits, and contextual substitution feature that
replaces the dot
On 29 Jul 2010, at 08:53, Michael Everson wrote:
No. We will put it in the Currency Symbols block because the character does
not belong to either the Devanagari or the Latin script. Please note that all
of the reference glyphs
... in that block use a Times-like font as the basis for the
I had thought that the glyphs were not part of the UNICODE or ISO 10646
standards and only serve as a reference.
See the Disclaimer in http://www.unicode.org/versions/Unicode5.2.0/ch17.pdf.
Jony
-Original Message-
From: unicode-bou...@unicode.org [mailto:unicode-bou...@unicode.org] On
On Thu, Jul 29, 2010 at 10:15, Khaled Hosny khaledho...@eglug.org wrote:
Also, I don't buy in Unicode idea of
encoding different sets of decimal digits separately, they are all
different graphical presentations of the same thing.
Not in a document where the author is discussing the
Sirs,
There are certain corrections required for Kannada characters. Actually
correctness varies with the version of the windows OS and the version of MS
office!
Now, my questions are:Is this problem concerned with the unicode consortium Can
a private party develop an engine that generates
Everywhere below, the Unicode property value alias is missing an 'l'.
- In HTML table 1:
Egyp050 Egyptian hieroglyphshiéroglyphes égyptiens Egyptian
_Hierogyphs 2009-06-01
- In HTML table 2:
050 EgypEgyptian hieroglyphshiéroglyphes égyptiens Egyptian
_Hierogyphs
On Wed, Jul 28, 2010 at 10:43 PM, Tulasi tulas...@gmail.com wrote:
I do not see any Unicode role on India
Rupee symbol :)
why?
Here is the rupee sign in a Tamil newspaper:
http://epaper.dinakaran.com/pdf/2010/07/28/20100728c_014101005.jpg
N. Ganesan
Martin J. Dürst due...@it.aoyama.ac.jp wrote:
On 2010/07/29 13:33, karl williamson wrote:
Asmus Freytag wrote:
On 7/25/2010 6:05 PM, Martin J. Dürst wrote:
Well, there actually is such a script, namely Han. The digits (一、
二、三、四、五、六、七、八、九、〇) are used both as letters and as
decimal
Thanks all for responding. Of course it was my mistake to forget that
there are other countries using the Rupee currency. Maybe the new
character will be named the INDIAN RUPEE SIGN to underline the fact that
this sign is only for India.
--
Shriramana Sharma
Mark
*— Il meglio è l’inimico del bene —*
On Thu, Jul 29, 2010 at 05:57, Philippe Verdy verd...@wanadoo.fr wrote:
Martin J. Dürst due...@it.aoyama.ac.jp wrote:
On 2010/07/29 13:33, karl williamson wrote:
Asmus Freytag wrote:
On 7/25/2010 6:05 PM, Martin J. Dürst wrote:
Well,
Mark Davis ☕ m...@macchiato.com
It is not so strange. Read
http://www.unicode.org/reports/tr24/proposed.html#Multiple_Script_Values,
and other parts of #24 describing Common.
It is exactly because I had read this proposed update for UTS#24 that
I used my argument (if not, I would have not
That just really isn't a script issue; it is more an issue of which language
orthographies use which characters, and we have provision for that
information in CLDR.
Mark
*— Il meglio è l’inimico del bene —*
On Thu, Jul 29, 2010 at 09:07, Philippe Verdy verd...@wanadoo.fr wrote:
Mark Davis ☕
Date: Thu, 29 Jul 2010 14:57:17 +0200
Subject: Digit/letter variants in the same unified script (was: stability
policy on numeric type = decimal)
From: verd...@wanadoo.fr
To: due...@it.aoyama.ac.jp; pub...@khwilliamson.com
CC: asm...@ix.netcom.com; kent.karlsso...@telia.com;
Mark Davis ☕ wrote:
Mark
/— Il meglio è l’inimico del bene —/
On Thu, Jul 29, 2010 at 05:57, Philippe Verdy verd...@wanadoo.fr
mailto:verd...@wanadoo.fr wrote:
Martin J. Dürst due...@it.aoyama.ac.jp
mailto:due...@it.aoyama.ac.jp wrote:
On 2010/07/29 13:33, karl
Philippe Verdy noted:
Everywhere below, the Unicode property value alias is missing an 'l'.
- In HTML table 1:
Egyp 050 Egyptian hieroglyphshiéroglyphes égyptiens Egyptian
_Hierogyphs 2009-06-01
etc.
These errors in the tables have been corrected by the Registration
Asmus Freytag wrote:
Having Nd be limited to characters that
a) are used in decimal radix numbers
b) are part of a complete, ordered sequence 0..9
would make this property regular enough to serve
implementers. You could script the creation of
relevant data for your implementation based on that
On 2010/07/29 19:51, Juanma Barranquero wrote:
On Thu, Jul 29, 2010 at 10:15, Khaled Hosnykhaledho...@eglug.org wrote:
Also, I don't buy in Unicode idea of
encoding different sets of decimal digits separately, they are all
different graphical presentations of the same thing.
Not in a
On Fri, Jul 30, 2010 at 04:52, Martin J. Dürst due...@it.aoyama.ac.jp wrote:
It's very clear that we would get nowhere if we wanted to encode
all these.
The comment I respondend to talked about characters that are already encoded.
In simpler words, you cannot use the needs of discussions
karl williamson pub...@khwilliamson.com wrote:
This discussion doesn't make sense to me. The original proposal to
encode 19DA says that there is one set of digits in New Tai Lue, but
there is an extra digit '1' (the one that got put at 19DA), used when
the other digit '1' is visually
Hello Joanma,
On 2010/07/30 12:05, Juanma Barranquero wrote:
On Fri, Jul 30, 2010 at 04:52, Martin J. Dürstdue...@it.aoyama.ac.jp wrote:
It's very clear that we would get nowhere if we wanted to encode
all these.
The comment I respondend to talked about characters that are already encoded.
26 matches
Mail list logo
