Arabic based alphabets

2001-06-15 Thread Vladimir Ivanov
Vladimir Ivanov wrote:   >Letter "dze" is represented in Unicode by U+0681 "Arabic letter heh with >hamza above",>though the sign above heh is not exactly hamza.   John Hudson wrote:   > Does Pashto also make use of the regular hamza sign in other contexts?   Yes, for instance in Arabic loan

Re: informative due to variation across langauges

2001-06-15 Thread Peter_Constable
>Well, not exactly. "It's normative" *means* that xyz. But "It's normative" >*because* the Unicode Standard says so, which in turn is because the >UTC voted that it be so. > >*Why* they voted so may be an interesting historical question in >particular instances, but it may be beyond the necessiti

Re: informative due to variation across langauges

2001-06-15 Thread Peter_Constable
>> But normative explicitly does *not* mean unchangeable. > >It quite specifically means that others can use it and reference it. Anyone >knows you cannot build a house on a shifting foundation, which is why making >something "normative" should be something reserved for things that one is >*not*

RE: First of many newbie questions

2001-06-15 Thread Peter_Constable
Dear: $B$F$s$I$&$j$e$&$8(B >Well, Mister Constable. What's new about that? Looks to me >like e-Leven Digit Grrl just forgot to turn off her microphone >again... We're witnessing the spacey under-mumble of a quickly >crumbling mind. Maybe we'll get lucky and she'll burn up on re-entry... or >g

Re: informative due to variation across langauges

2001-06-15 Thread Kenneth Whistler
Peter continued: > Indeed: e.g. that is true for the Unicode 1.0 Name property. My question, > though, is whether there are some properties that are informative because > they may be typical for most languages but not true for all. It was always > my impression that that was the reason for case m

Re: informative due to variation across langauges

2001-06-15 Thread Michael \(michka\) Kaplan
From: <[EMAIL PROTECTED]> > On 06/15/2001 06:29:51 PM "Michael \(michka\) Kaplan" wrote: > >Why be more specific then there are a lot of people who think they might > >possibly have made TOO MUCH normative and do not want to make things > >unchangeable that might be in error or might need to chan

Re: UTF-8S ??? UTF-16F !!!

2001-06-15 Thread Mark Davis
Markus, there is an archive on http://groups.yahoo.com/group/unicode/messages/ if you really want the gory details. However, this topic is raging on at least 3 email lists that I know of -- with one heck of a lot of repetition. To add to that, I will forward a couple of messages I had sent to a di

Re: UTF-8S: a modest proposal

2001-06-15 Thread Edward Cherlin
At 07:46 PM 6/12/2001, John Cowan wrote: >I would urge Oracle and friends to move this to a different venue, >specifically >[EMAIL PROTECTED] As far as I can see, UTF-8S does not need either >the approval or the disapproval of the Unicode Consortium. If it is >actually in use, it needs a label

Re: informative due to variation across langauges

2001-06-15 Thread Peter_Constable
On 06/15/2001 06:28:34 PM Kenneth Whistler wrote: >Peter asked: > >> It used to be that one could describe informative properties saying, "some >> properties are valid for most languages but not all and so are informative, >> such as case mappings". > >This never really was the case, since from

Re: informative due to variation across langauges

2001-06-15 Thread Peter_Constable
On 06/15/2001 06:29:51 PM "Michael \(michka\) Kaplan" wrote: >> Can anyone give me a specific example of why Line Breaking or East Asian >> Width properties aren't normative? > >Why be more specific then there are a lot of people who think they might >possibly have made TOO MUCH normative and do

informative due to variation across langauges

2001-06-15 Thread Peter_Constable
It used to be that one could describe informative properties saying, "some properties are valid for most languages but not all and so are informative, such as case mappings". Case mappings gave an easy example for why to have informative properties. Now that the mappings are informative (with norm

Re: informative due to variation across langauges

2001-06-15 Thread Kenneth Whistler
Peter asked: > It used to be that one could describe informative properties saying, "some > properties are valid for most languages but not all and so are informative, > such as case mappings". This never really was the case, since from the moment that the UTC started posting informative propert

Re: informative due to variation across langauges

2001-06-15 Thread Michael \(michka\) Kaplan
From: <[EMAIL PROTECTED]> > Can anyone give me a specific example of why Line Breaking or East Asian > Width properties aren't normative? Why be more specific then there are a lot of people who think they might possibly have made TOO MUCH normative and do not want to make things unchangeable tha

Re: First of many newbie questions

2001-06-15 Thread Michael \(michka\) Kaplan
From: "Youtie Effaight" <[EMAIL PROTECTED]> > Well, Mister Constable. What's new about that? Looks to me > like e-Leven Digit Grrl just forgot to turn off her microphone > again... We're witnessing the spacey under-mumble of a quickly > crumbling mind. Maybe we'll get lucky and she'll burn up o

Re: First of many newbie questions

2001-06-15 Thread Youtie Effaight
[EMAIL PROTECTED] wrote on 2001-06-15 10:26:24 -0700: >A simple question: is this intended as a monologue, or just >thinking out loud? Or are you actually looking for feedback >on something? >[... detritus of *kuten's snipped out ...] Well, Mister Constable. What's new about that? Looks to me

Re: First of many newbie questions

2001-06-15 Thread Peter_Constable
A simple question: is this intended as a monologue, or just thinking out loud? Or are you actually looking for feedback on something? Peter On 06/15/2001 09:13:20 AM unicode-bounce wrote: > > >WATASIHABAKAYAROUDA >GOMENNE > >This is what I get when I have no sake and no Unicode bo

Tr: First of many newbie questions

2001-06-15 Thread Patrick Andries
- Message d'origine - De : "Otto Stolz" <[EMAIL PROTECTED]> > > In Unicode, the diacritic always follows its base character. > Cf. TUS 3.0, section 3.5, in particular definition D17, > also in . > This topic is extensively covered in the F

Re: First of many newbie questions

2001-06-15 Thread
WATASIHABAKAYAROUDA GOMENNE This is what I get when I have no sake and no Unicode book. OOF. So let's see. I have FIRST the shi and THEN the dakuten. Or if you like roses, use ba for bara. Ha and then dakuten, right? Or if you like Pokémon, use ho and then handakuten, right? In on

font for bibliographic database!

2001-06-15 Thread Rajesh Chandrakar
Dear folks, In keeping in mind the multilingual bibliographic database, I would like to know : * is there any font, which do have contain all languages? * is there any font for basically indian and its subcontinental languages? * what would be better either single font or set of scripts?

Re: First of many newbie questions

2001-06-15 Thread Otto Stolz
Am 2001-06-14 um 20:17 h PDT hat <[EMAIL PROTECTED]> geschrieben: > With a pen [...]: e, THEN circumflex > With Unicode decomposed: circumflex, THEN e > With Unicode composed: e with circumflex ... > Unicoders, did I say it right? No. One item wrong, one item (at least) missing. In Unicode, the

RE: First of many newbie questions

2001-06-15 Thread Pascal Maheu
Title: RE: First of many newbie questions Sigh... Thanks for all your responses.  Yes I did check out the fact pages, I just did not check them carefully enough.  I was so concentrated on finding the information that I... "missed" the left hand links to more FAQs.  In the words of a certain pe

RE: First of many newbie questions

2001-06-15 Thread Marco Cimarosti
Pascal Maheu wrote: > - How does using non-spacing characters like "^" > interact with say an "e" to form a "ê"? > - [...] what is the difference btw UTF-8, 16 and > 32? Why would one want to use one instead of the other? See the Unicode FAQ (http://www.unicode.org/unicode/faq/), sections "Ch

Re: UTF-8S score keeping

2001-06-15 Thread Tex Texin
Antoine, I pretty much agree. I copied most of the message, since yours might have bounced to Unicore. On the second point you added, although, technically 16-bit users may have come first, I think UTF-8 users dominated early, so I wouldn't necessarily give favor to utf-16 users. But it's a sad