[no subject]

[Note: message resent using another domain. Visibly the Unicode mailing list rejects as spam all emails posted from Gmail's webmail, and containing all relevant tracking mime headers and regularly signed by Google and my proven identity]. 2015-03-28 12:30 GMT+01:00 Michael Norton : > > Thanks D

Prepending vowel exception in Lontara/Buginese script ?

If I look in the Unicode 6.0 charts for the Buginese script, I see that vowel /e/ (U+1A19) is prepended visually on the left of the base consonnant to which it applies. This should mean that the vowel has to be encoded ilogically in texts AFTER the base consonnant to which it applies. However,

Re: Draft Proposal to add Variation Sequences for Latin and=D=A Cyrillic letters

"Michael Everson" > On 6 Aug 2010, at 22:20, Karl Pentzlin wrote: > > > Am Dienstag, 3. August 2010 um 09:45 schrieb Michael Everson: > > > > ME> ... In particular the implications > > ME> for Serbian orthography would be most unwelcome. > > > > As I have outlined in the revised introduction of

Re:=D=A Standard fallback characters (was: Draft Proposal to add Variation� Sequences for Latin and Cyrillic letters)

"Asmus Freytag" > > If a text was initially using a round s, nothing prohibits it being > > rendered in Fraktur style, but even in this case, the conversion to "long s" will be inappropriate. So use the Fraktur "round s" directly. > > > This statement makes clear that you don't understand the

Re: UTS#10 (UCA) 7.1.3 Implicit Weights, Unassigned and Other Code=D=A Points

"Kenneth Whistler" > > Currently, if the Unicode scalar value (or invalid code unit) is > > (unsigned 32-bit value), then they are treated as expansions to > > ignorable collation elements: > > [....] > > That statement is incorrect. The UCA currently specifies that > ill-for

re: Dialects and orthographies in BCP 47 (was: Re: Draft Proposal=D=A to add Variation Sequences for Latin and Cyrillic letters)

"Doug Ewell" wrote: > There is no "formal model" in the sense of a standard N-letter subtag > for dialects, because the concept of a dialect is too open-ended and > unsystematic. The word means different things to different people. > What may be a dialect to one person might be a full-blown Natio

Standard fallback characters (was: Draft Proposal to add Variation=D=A Sequences for Latin and Cyrillic letters)

"Asmus Freytag" wrote: > The Fraktur problem is one where one typestyle requires additional > information (e.g. when to select long s) that is not required for > rendering the same text in another typestyle. If it is indeed desirable > (and possible) to create a correctly encoded string that ca

Re: Draft Proposal to add Variation Se=D=A quences for Latin and Cyrillic  letters

"John W Kennedy" wrote: > On Aug 4, 2010, at 8:20 AM, Andreas Stötzner wrote: > > Am 03.08.2010 um 02:47 schrieb David Starner: > >> Fraktur and Antiqua are different writing > >> systems with slightly different orthographies > > > > No. Fraktur and Antiqua are two (of many) different renderings o

Re: Draft Proposal to add Variation Sequences for Latin and=D=A Cyrillic =9letters (was Re: long s (was: Draft Proposal to add Variation=D=A Sequences for =9Latin and Cyrillic letters))

In my opinion, adding the s+VS1 variation sequence is completely unneeded. If you really want a "long s", use the code assigned to the long s. fonts or renderers should still provide a reasonnable fallback to "s" if the glyph is missing. This means that all existing ligatures will long s will c

Re: Indian new rupee sign

> De : "Michael Everson" > I like the video clip there. "Encoding in Indian standards will take about > six months. Encoding in the Unicode and IEC standards will take about 18 months to two years." > > Sounds as though our Government of India colleagues gave them good advice. > > Michael Ev

Re: Using Combining Double Breve and expressing characters perhaps as if struck out.

"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=on&g= 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 l

re: Using Combining Double Breve and expressing characters perhaps as if struck out.

> De : vanis...@boil.afraid.org > Guys, does nobody read the bloody Standard anymore!? > > You CAN currently add a diacritic on top of a double diacritic. The "other" > base character is called the Combining Grapheme Joiner (U+304F). Sorry, I had forgotten this one. Note that I was not sure abou

re: Using Combining Double Breve and expressing characters perhaps as if struck out.

"Philippe Verdy" wrote: > But even with this case, you wont be able to encode with the ZWJ trick > in plain text, such groupings that are expressed this way in TeX: > > \breve{ \breve{oo} x \breve{ o\acute{o} } } > > Because double diacritics encoded in Unicode can't be safely stacked > together

re: ISO 15924 update

I note this entry just added in last March: Narb 106 Old North Arabian (Ancient North Arabian) nor-arabien The French column is clearly containing a typo for the word "nord" in the compound (see also: nord-coréen, nord- américain). (And the adjective "arabien" was completely invented from an in

Re: UTS#10 (collation) : French backwards level 2, and word-breakers.

"Kenneth Whistler" > A : verd...@wanadoo.fr > Copie à : unicode@unicode.org, k...@sybase.com > Objet : Re: UTS#10 (collation) : French backwards level 2, and word-breakers. > > > Philippe Verdy said: > > > A basic word-breaker using inly the space separator would marvelously > > improve the spe