Dear Colleagues,
In processing a document, I came across a punctuation character which
I was not able to find in Unicode. As I find it hard to believe that
the character has not been encoded yet, I must think my search was
incomplete, and I'd be hoping that you can point me to the correct
Op dinsdag 27 juli 2010 21:07 schreef karl williamson:
They are U+2107 and U+210E respectively. Chapter 4 of TUS seems to
indicate that neither should, since they both are operands, and it
says this property applies to mathematical operators.
Operands are not operators, e.g. in a+b, a and b
André Szabolcs Szelp wrote:
Generally, for the decimal point . (U+002E FULLSTOP) and , (U+002C
COMMA) is used in the SI world. However, earlier conventions could use
different notation, such as the common British raised dot which
centers with the lining digits (i.e. that would be U+00B7 MIDDLE
Den 2010-07-28 09.50, skrev Jukka K. Korpela jkorp...@cs.tut.fi:
André Szabolcs Szelp wrote:
Generally, for the decimal point . (U+002E FULLSTOP) and , (U+002C
COMMA) is used in the SI world. However, earlier conventions could use
different notation, such as the common British raised dot
This is a somewhat late mail and please forgive me if this question has
already been asked but there are too many hits for 20A8 Rupee when
searching through the lists. Isn't it possible to just change the glyph
of 20A8? To my knowledge, few people actually use 20A8 to display the
existing
Shriramana Sharma said on Wed, Jul 28, 2010 at 02:52:46PM +0530,:
This is a somewhat late mail and please forgive me if this question
has already been asked but there are too many hits for 20A8 Rupee
when searching through the lists. Isn't it possible to just change
the glyph of 20A8? To
On 28/07/10 10:22, Shriramana Sharma wrote:
This is a somewhat late mail and please forgive me if this question
has already been asked but there are too many hits for 20A8 Rupee when
searching through the lists. Isn't it possible to just change the
glyph of 20A8? To my knowledge, few people
Op wo 28 juli 2010 11:22 schreef Shriramana Sharma:
This is a somewhat late mail and please forgive me if this question has
already been asked but there are too many hits for 20A8 Rupee when
searching through the lists. Isn't it possible to just change the glyph
of 20A8? To my knowledge, few
On Tue, 27 Jul 2010, Arno Schmitt wrote:
Since U+0649 is called alif maqsura it should be used for alif maqsura.
But that argument, you must use U+0027 for an apostrophe instead
of U+2019.
The Unicode names for characters are often hictorical and
you should not infer anything from such names.
Hi Kamal,
Thanks for the helpful comment -- especially the URLs. A quick check
showed that at least on the BBC, U+064A and U+06CC are used
interchangeably, even in final position where the glyphs differ. My
Pashto is extremely weak, but even I can recognize that in the
following article,
Alex notes Operands are not operators, e.g. in a+b, a and b are operands, + is
an operator. I'm sure Karl Williamson knows that, but the mathematical
alphanumerics also aren't operators and they nevertheless have the math
property. We need to change the description of the math property to
On Tue, 27 Jul 2010, David Starner wrote:
MacArabic, Windows-1256 and ISO-8859-6 are all standards for
the encoding of Arabic. Thus U+0649 must be an Arabic character;
existing use in both those sets and in Unicode say that is.
By that circular logic, S with cedilla and T with cedilla
must be
On Wed, Jul 28, 2010 at 04:33:12PM +0200, Andreas Prilop wrote:
On Tue, 27 Jul 2010, Khaled Hosny wrote:
it just happen not to get in those two positions
in modern orthography, but it can be seen in Quran
which is still written in the old, early Islamic orthography.
If you argue with
Kent Karlsson wrote:
And the Nameslist says:
002EFULL STOP
= period, dot, decimal point
* may be rendered as a raised decimal point in old style numbers
Right, I remembered there is such a comment somewhere but did not remember
where.
However, I think that is a bad idea: firstly
On Wed, Jul 28, 2010 at 10:51 AM, Andreas Prilop
prilop4...@trashmail.net wrote:
On Tue, 27 Jul 2010, David Starner wrote:
MacArabic, Windows-1256 and ISO-8859-6 are all standards for
the encoding of Arabic. Thus U+0649 must be an Arabic character;
existing use in both those sets and in
On Tue, 27 Jul 2010, Khaled Hosny wrote:
According to Grammatik des klassischen Arabisch by Wolfdietrich Fischer,
page 9, the ya is written two dots in such cases, too.
Except that this is not a Yaa and not pronounced like a Yaa, it is an
Alef (note the small dagger Alef above it).
That is
On 7/28/2010 2:02 AM, Kent Karlsson wrote:
Den 2010-07-28 09.50, skrev Jukka K. Korpela jkorp...@cs.tut.fi:
André Szabolcs Szelp wrote:
Generally, for the decimal point . (U+002E FULLSTOP) and , (U+002C
COMMA) is used in the SI world. However, earlier conventions could use
different
On Wed, Jul 28, 2010 at 05:32:21PM +0200, Andreas Prilop wrote:
On Tue, 27 Jul 2010, Khaled Hosny wrote:
According to Grammatik des klassischen Arabisch by Wolfdietrich Fischer,
page 9, the ya is written two dots in such cases, too.
Except that this is not a Yaa and not pronounced like
Den 2010-07-28 17.09, skrev Jukka K. Korpela jkorp...@cs.tut.fi:
Kent Karlsson wrote:
And the Nameslist says:
002EFULL STOP
= period, dot, decimal point
* may be rendered as a raised decimal point in old style numbers
Right, I remembered there is such a comment somewhere but
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 algorithms?
Szabolcs
Quoting Andreas Prilop prilop4...@trashmail.net:
Hi Andreas,
Thanks for the references to the old 7-bit and 8-bit Arabic character sets.
http://www.itscj.ipsj.or.jp/ISO-IR/089.pdf
http://www.itscj.ipsj.or.jp/ISO-IR/127.pdf
I think these clearly show that alef maksura was the intention
On Tue, 27 Jul 2010, Khaled Hosny wrote:
According to Grammatik des klassischen Arabisch by Wolfdietrich Fischer,
page 9, the ya is written two dots in such cases, too.
Except that this is not a Yaa and not pronounced like a Yaa, it is an
Alef (note the small dagger Alef above it).
That is
All three Pashto Yeh characters represent significant phonetic differences.
06CC is used for the /i/ sound while 06D0 (with two vertical dots below) stands
for /e/.
According to some sources, the third one (06CD) represents /ej/ and is not
consistently used for all dialects.
I think the
On Wed, 28 Jul 2010, lingu...@artstein.org wrote:
Here's an arbitrary page from today's Al-Ahram newspaper,
[...]
On my computer this looks particularly jarring,
You can find enough pages from Continental Europe and Latin
America that have an acute accent instead of an apostrophe
due to
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 OpenType features at the user's discretion. The
choice of glyph for U+002E could be chosen according to an
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 have only limited
understanding of English grammar. At least in my country. They
On 28 Jul 2010, at 18:09, 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 OpenType features at the user's
discretion. The choice of
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 OpenType features at the user's discretion. The choice of glyph for
Murray Sargent murr...@exchange.microsoft.com wrote:
Alex notes Operands are not operators, e.g. in a+b, a and b are operands,
+ is an operator.
Not always true, this depends on the domain of definition, see below,
and all operators can also be themselves operands of another operator.
The
Asmus asks, Which implementation makes the required context analysis to
determine whether 002E is part of a number during layout? If it does make this
determination, which OpenType feature does it invoke? Which font supports this
particular OpenType feature?
I haven't looked to see if our
Michael asks, Are or will be OT features supported in, say, filenames? The
answer depends on the renderer. For example, if you display filenames in
NotePad using the Calibri font, default English ligatures are used
automatically using OpenType table info.
Murray
On 28 Jul 2010, at 21:25, Murray Sargent wrote:
Michael asks, Are or will be OT features supported in, say, filenames? The
answer depends on the renderer. For example, if you display filenames in
NotePad using the Calibri font, default English ligatures are used
automatically using
Michael asks, Are or will be OT features supported in, say, filenames? The
answer depends on the
renderer. For example, if you display filenames in NotePad using the Calibri
font, default English
ligatures are used automatically using OpenType table info.
I meant on the desktop or in the
Message du 26/07/10 18:45
De : Markus Scherer markus@gmail.com
A : verd...@wanadoo.fr
Copie à : Unicode Mailing List unicode@unicode.org
Objet : Re: Using Combining Double Breve and expressing characters perhaps as
if struck out.
There are 857 combining marks with combining
On 15 July 2010 13:02, Jim Breen jimbr...@gmail.com wrote:
John H. Jenkins wrote:
We hope to have it back in the next few days.
Two weeks have passed, and it's still:
The Unihan Database is down for maintenance.
Sure I can grep the text file, but it's not the same.
Jim
--
Jim Breen
On 28 July 2010 18:41, Michael Everson ever...@evertype.com 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 OpenType features at the user's
On 28 July 2010 22:09, Philippe Verdy verd...@wanadoo.fr wrote:
You've not understood what I wanted to say.
Maybe if you said less people would understand more .
I don't know how much free time you must have on your hands to write
hundreds of lines in reply to almost every message on this list
Quoting CE Whitehead cewcat...@hotmail.com:
'g' is a non-Arabic sound ... and there is no g in Standard
Arabic although there are two ways to write it ...
Oh, there are many more than two ways to write the [g] sound in
Arabic. Standard Arabic traditionally transcribes foreign [g] as ghain
Hi Eric,
thank you for sharing this.
Robert
On 2010/07/28 17:35, Eric Muller wrote:
http://www.idsgn.org/posts/the-end-of-movable-type-in-china/
Markus Scherer
There are 857 combining marks with combining class of 0:
http://unicode.org/cldr/utility/list-unicodeset.jsp?a=[[:M:]%26[:ccc%3D0:]]abb=ong=
So what ? I perfectly know that there are a lot of diacritics with cc of 0.
It's DEFINITELY NOT me that contested that on this list
It is good that M. Everson's proposal and Govt. of India
proposal are converging. Both ask for Indian Rupee Sign
in the Currency block.
N. Ganesan
I agree; when the nuggets of useful information are so overwhelmed by the
volume of rubble, you just can't afford the time to sift them out.
Mark
*— Il meglio è l’inimico del bene —*
On Wed, Jul 28, 2010 at 14:46, Andrew West andrewcw...@gmail.com wrote:
On 28 July 2010 22:09, Philippe Verdy
On 2010/07/28 0:36, John Dlugosz wrote:
I can imagine supporting national representations for numbers for outputting
reports,
but I don't imagine anyone writing in a programming language would be compelled
to
type 四佰六十 instead of 560.
Well, indeed, I hope nobody would do that. 四佰六十 would
It is good that M. Everson's proposal
and Govt. of India proposal are converging.
No its not good!
M. Everson's proposal be withdrawn, he rushed hastily.
His font design is out of his mind, not from the drawing.
He cut left vertical bar of English alphabet R from an existing TTF font,
then
Asmus Freytag wrote:
On 7/25/2010 6:05 PM, Martin J. Dürst wrote:
On 2010/07/26 4:37, Asmus Freytag wrote:
PPS: a very hypothetical tough case would be a script where letters
serve both as letters and as decimal place-value digits, and with modern
living practice.
Well, there actually is
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 due to the
complexity of Unicode, even
On 2010/07/29 06:33, karl williamson wrote:
Is it the case that a sequence of just these characters, without any
intervening characters, and not adjacent to the special characters you
mention always mean a place-value decimal number?
One common counter-example would be 七五三 (Shichi-Go-San
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 place-value digits, and they are scattered widely, and
Doug comments:
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 due to the
On 7/28/2010 10:13 PM, Martin J. Dürst wrote:
Sequences of numeric Kanji are also used in names and word-plays, and
as sequences of individual small numbers.
But the same applies to our digits. A very simple example is to use
them as a ruler in plain text:
1 2 3
50 matches
Mail list logo
