Re: Response to Everson Phoenician and why June 7?

James Kass wrote: > As a member of the Latin script user community, I'd not be threatened > by a separate encoding for Fraktur. I have Fraktur books in my > library. Whether I've got their titles stored in my database using > Latin characters or abusing math variables is best left to > speculat

Re: Response to Everson Phoenician and why June 7?

Dean Snyder replied, > >Many people believe that the Dead Sea Scrolls were written by the Essenes, > >but there are some who believe otherwise. Discussion among knowledgeable > >historians of the alphabet as to its origins may be lively and entertaining, > >but, its identity as a separate script

Re: ISO 15924

From: "Michael Everson" <[EMAIL PROTECTED]> > Beta files are now available for testing and verification at > http://www.unicode.org/iso15294. The Registrar thanks everyone who > has commented on the ISO 15924 website to date, and looks forward to > final corrections if any should be required. Not

Re: Response to Everson Phoenician and why June 7?

Dean Snyder wrote, > Doesn't the idea that so many people will embrace a new Fraktur range > imply that it's the right thing to do? It might, if it were true. During the course of this discussion, I've often lamented that there is no evidence whatsoever that Semitic mathematicians ever used pal

Re: Response to Everson Phoenician and why June 7?

Dean Snyder wrote: >>> Doesn't the idea that so many people will embrace a new Fraktur >>> range imply that it's the right thing to do? >> >> Who has ever asked for that? > > I have no one in mind. There is no one for you to have in mind. > But, by analogy, so should no one think thusly about P

Re: Response to Everson Phoenician and why June 7?

Dean Snyder wrote: > Doesn't the idea that so many people will embrace a new Fraktur range > imply that it's the right thing to do? Who has ever asked for that? -Doug Ewell Fullerton, California http://users.adelphia.net/~dewell/

Re: Response to Everson Phoenician and why June 7?

Doug Ewell wrote at 9:27 PM on Thursday, May 20, 2004: >Dean Snyder wrote: > >> Doesn't the idea that so many people will embrace a new Fraktur range >> imply that it's the right thing to do? > >Who has ever asked for that? I have no one in mind. But, by analogy, so should no one think thusly a

Re: Response to Everson Phoenician and why June 7?

James Kass wrote at 4:06 AM on Friday, May 21, 2004: >Dean Snyder wrote, > >> I know Phoenician has been sexy, provocative, glamorous, and enthralling >> to historians of the alphabet for centuries - it was a part of the Greek >> cultural psyche that they got their letters from the Phoenicians; an

Re: Response to Everson Phoenician and why June 7?

James Kass wrote at 4:06 AM on Friday, May 21, 2004: >Doesn't the idea that so many people will embrace a new Phoenician range >imply that it's the right thing to do? Doesn't the idea that so many people will embrace a new Fraktur range imply that it's the right thing to do? Respectfully, Dean

Re: Response to Everson Phoenician and why June 7?

Dean Snyder wrote, > Your seven-repeated "reasonable" analysis of this engineering issue does > not even mention once, much less address, the PROBLEMS that will be > caused by encoding this diascript. There seems to be a fear among those opposed to the Phoenician proposal that many people will w

Re: ISO 15924 codes for ConScript

Curtis Clark wrote: >>> One person wrote, regarding Qaak for Klingon: >>> It's a shame you didn't pick something that could be pronounced in tlhIngan Hol, perhaps Qaap for pIqaD. >> >> Identifiers are identifiers, not words. > > That's why I sent my message to Doug off-list; it was a jo

Re: ISO 15924

<<>> MichKa P.S. Hint: the subject is smarter than the body. - Original Message - From: "Mahesh T. Pai" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 20, 2004 7:49 PM Subject: Re: ISO 15924 > Michael Everson said on Fri, May 21, 2004 at 12:56:44AM +0100,: > > > htt

Re: Response to Everson Phoenician and why June 7?

A kind list member has advised privately that CAL does now use Unicode for Syriac text. I must not have been looking in the right places. >From this page, http://cal1.cn.huc.edu/fonts/fontinfo.html "Most of our Aramaic text display is now done in Unicode, for which see our page hebun

Re: ISO 15924

At 08:19 +0530 2004-05-21, Mahesh T. Pai wrote: Michael Everson said on Fri, May 21, 2004 at 12:56:44AM +0100,: > http://www.unicode.org/iso15294. The Registrar thanks everyone who I am getting a 404 here? Sorry, it's http://www.unicode.org/iso15924 -- Michael Everson * * Everson Typography * * h

Re: Response to Everson Phoenician and why June 7?

At 22:31 -0400 2004-05-20, Dean Snyder wrote: >That proves nothing at all. In fact, I have a number of Phoenician fonts using Latin clones to represent Phoenician letters. I have yet to find a single font with Hebrew encoding and Phoenician glyphs. Where have you looked? On the internet, of course

Re: ISO 15924

Michael Everson said on Fri, May 21, 2004 at 12:56:44AM +0100,: > http://www.unicode.org/iso15294. The Registrar thanks everyone who I am getting a 404 here? -- "Those willing to give up a little liberty for a little security deserve neither security nor liberty"

Re: Response to Everson Phoenician and why June 7?

Kenneth Whistler wrote at 4:51 PM on Thursday, May 20, 2004: >John Hudson asked, again: > >> My question, again, is whether there is a need for the plain >> text distinction in the first place? > >And I claim that there is no final answer for this question. We >simply have irresolvable difference

Re: Response to Everson Phoenician and why June 7?

Kenneth Whistler wrote: A character encoding standard is an engineering construct, > not a revelation of truth Amen. I begin to suspect that part of the problem -- the problem of interminable debate, not any technical problem -- is due in part to different perceptions of the Unicode Standard.

U+0482

Why the general Category of U+0482 : CYRILLIC THOUSANDS SIGN is So [Symbol, Other] while the apparently equivalent characters in the U+2160 - U+2183 range are rather Nl [Number, Letter]. Granted that U+0482 is not a letter, but IMHO it should at least be No [Number, Other] -- "So" puts it in the s

Re: Response to Everson Phoenician and why June 7?

Michael Everson wrote at 2:45 AM on Friday, May 21, 2004: >At 21:28 -0400 2004-05-20, Dean Snyder wrote: >>Michael Everson wrote at 11:24 PM on Thursday, May 20, 2004: >> >>>At 14:59 -0700 2004-05-20, Patrick Andries wrote: >>> You may mean that the Unicode book does not document how Phoenicia

Re: Response to Everson Phoenician and why June 7?

Elaine Keown wrote, > Hi, > > > Does Dr. Kaufman speak for all professionals in the > > field, or would it be fair to say that Dr. Kaufman > > is speaking for only one such professional? > > Prof. Dr. Stephen Kaufman, of Hebrew Union College, > Cincinnati, is the leading computational Aramaist

Re: Unibook and Code2000

On 2004.05.20, 20:54, I wrote: > I just noticed that some UCS blocks are displayed in Unibook turned > 90 deg. counter-clockwise (apparently everything from U+2460 to > U+27B0); the only thing I changed recently was adding Code2000 OK, fixed by adding the font properly to . However, it should not

Re: Response to Everson Phoenician and why June 7?

At 21:28 -0400 2004-05-20, Dean Snyder wrote: Michael Everson wrote at 11:24 PM on Thursday, May 20, 2004: At 14:59 -0700 2004-05-20, Patrick Andries wrote: You may mean that the Unicode book does not document how Phoenician (or Paleo-Hebrew) may be encoded. This is not to say that no one is using

Re: Response to Everson Phoenician and why June 7?

Kenneth Whistler scripsit: > The question is rather, given the fundamental nature of the > Unicode Standard as enabling text processing for modern > software, it is cost-effective and *reasonable* to provide > a Unicode encoding for one particular script or another, > unencoded to date, so as to m

Re: Response to Everson Phoenician and why June 7?

Michael Everson wrote at 11:24 PM on Thursday, May 20, 2004: >At 14:59 -0700 2004-05-20, Patrick Andries wrote: > >>You may mean that the Unicode book does not document how Phoenician >>(or Paleo-Hebrew) may be encoded. This is not to say that no one is >>using Unicode to encode Paleo-Hebrew tex

Re: Response to Everson Phoenician and why June 7?

James Kass wrote at 9:04 PM on Thursday, May 20, 2004: >In this case, I think it's important to be picky because there are >no current Unicoding practices for Phoenician. Phoenician is not >yet encoded in the standard. That's like saying Fraktur is not yet encoded in the standard. Respectful

Re: ISO 15924 codes for ConScript

on 2004-05-20 07:52 Peter Constable wrote: One person wrote, regarding Qaak for Klingon: It's a shame you didn't pick something that could be pronounced in tlhIngan Hol, perhaps Qaap for pIqaD. Identifiers are identifiers, not words. That's why I sent my message to Doug off-list; it was a joke.

Re: Response to Everson Phoenician and why June 7?

Elaine Keown Tucson Hi, > Does Dr. Kaufman speak for all professionals in the > field, or would it be fair to say that Dr. Kaufman > is speaking for only one such professional? Prof. Dr. Stephen Kaufman, of Hebrew Union College, Cincinnati, is the leading computational Aramaist

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> > At 00:05 +0200 2004-05-21, Philippe Verdy wrote: > > >This (below) is my own plain text version (still using the field and row order > >of table 3 by english name, instead of the order of table 1 by code)... Some > >entries are commented out with %. > >

Variation Sequences as Substitute for Fonts or for Encoding a Script (Was... Phoenician ...)

Ernest indicated: > Whether using variation sequences to separate > Phoenician from Square Hebrew would be daft > would depend upon a number of factors. > > How often would both glyph repertoires appear in > the same document? > > How frequently would non-Square Hebrew glyphs > be used? > > How

ISO 15924

Beta files are now available for testing and verification at http://www.unicode.org/iso15294. The Registrar thanks everyone who has commented on the ISO 15924 website to date, and looks forward to final corrections if any should be required. -- Michael Everson * * Everson Typography * * http://

Re: Response to Everson Phoenician and why June 7?

Patrick said: > >In this case, I think it's important to be picky because there are > >no current Unicoding practices for Phoenician. > > > You may mean that the Unicode book does not document how Phoenician (or > Paleo-Hebrew) may be encoded. This is not to say that no one is using > Unicode t

Re: ISO 15924 draft fixes

From: "Peter Constable" <[EMAIL PROTECTED]> > > From: Philippe Verdy [mailto:[EMAIL PROTECTED] > > > No the structure is correct, however the text file was prepared by > copy/pasting > > HTML text inserted in empty cells, namely the " " character > reference (that > > contains a syntaxic semicolon

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> > I could use a little help rendering this into French, lest I > embarrass myself > > "The Property Value Alias is defined as part of the Unicode Standard > and is provided informatively in the tables here to show how entries > in the ISO 15924 code t

Re: Response to Everson Phoenician and why June 7?

> [Original Message] > From: John Hudson <[EMAIL PROTECTED]> > > Peter, are we talking about the same thing? Ernest is > suggesting bizarre measures to deal with a problem > -- in my opinion, a non-existent one -- that he sees in > *unification*. You are arguing against Michael's > *dis-unificat

Re: ISO 15924 draft fixes

At 00:05 +0200 2004-05-21, Philippe Verdy wrote: This (below) is my own plain text version (still using the field and row order of table 3 by english name, instead of the order of table 1 by code)... Some entries are commented out with %. The RA has no intention whatsoever of making use of this fil

Re: Response to Everson Phoenician and why June 7?

At 14:59 -0700 2004-05-20, Patrick Andries wrote: You may mean that the Unicode book does not document how Phoenician (or Paleo-Hebrew) may be encoded. This is not to say that no one is using Unicode to encode Paleo-Hebrew texts. The several Phoenician fonts which I have are *all* Latin clones. -

Unibook and Code2000

I just noticed that some UCS blocks are displayed in Unibook turned 90 deg. counter-clockwise (apparently everything from U+2460 to U+27B0); the only thing I changed recently was adding Code2000 to the list of usable fonts (this does not happend with Arial Unicode, f.i.). FWIW, Code2000 displays co

RE: ISO 15924 draft fixes

> From: Philippe Verdy [mailto:[EMAIL PROTECTED] > No the structure is correct, however the text file was prepared by copy/pasting > HTML text inserted in empty cells, namely the " " character reference (that > contains a syntaxic semicolon conflicting with the CSV separator). IMO, the structure

Re: ISO 15924 draft fixes

"Peter Constable" wrote: > > Michael Everson wrote: > > >Also, it appears you have not fixed a serious error in the > > >plain-text file: it is not well-structured. Some rows have 6 > > >columns, and some have 7. > > > > That might be fixed in the newest one. > > It is not fixed in the file that's

Re: ISO 15924 draft fixes

From: "Antoine Leca" <[EMAIL PROTECTED]> > > Antoine Leca a écrit : > > > >> The French name for Hang looks strange. It happened to be "hangul > >> (hangul, hangeul)" (after quite a bit of discussion.) > > Sorry guys. For reasons known to itself, my mailer refused to post in UTF-8 > this morning. I

Re: Response to Everson Phoenician and why June 7?

James Kass a Ãcrit : Ernest Cline wrote, In order for Phoenician to be "disunified" from Hebrew, it must first have been unified with Hebrew. This is not the case. Well then, nonunification if you wish to be picky about it. Sorry if I offended. Many on this list have referred to th

Re: ISO 15924 draft fixes

At 23:21 +0200 2004-05-20, Philippe Verdy wrote: Micheal has just changed the online version (but with the wrong dates...that's irritating). Patience... Unchanged codes will retain 2004-05-01 as the starting date. Changed codes have (as of the current BETA draft which is uploaded for testing purp

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> > Is the format order satisfactory? English_Name;Code;Nº;Nom_français;PVA;Date > Or would it be preferable to have it in the > format of Table 1 > (Code;Nº;English_Name;Nom_français;PVA;Date) I vote for the order of table 1; the Code is the most importan

Re: Response to Everson Phoenician and why June 7?

Peter Kirk wrote: This is not a practical use of variation sequences if, by this, you mean use of variation selectors. What are you going to do, add a variation selector after every single base character in the text? ... ... ... Are you expecting fonts to support the tiny stylistic variations be

RE: ISO 15924 draft fixes

At 13:49 -0700 2004-05-20, Peter Constable wrote: I agree with Addison here: the most important thing is stability, but it makes sense that the first and second columns be the symbolic code and the numeric code, especially if this is *the* plain-text version and normative reference. That's going to

Re: ISO 15924 draft fixes

From: "Peter Constable" <[EMAIL PROTECTED]> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf > > Of Michael Everson > > > I hope this satisfies you. > http://www.unicode.org/iso15924/codelists.html > > If they are consistent and reliable, I'm satisfied with them. I hope you > will

Re: Response to Everson Phoenician and why June 7?

[EMAIL PROTECTED] wrote: In order for Phoenician to be "disunified" from Hebrew, it must first have been unified with Hebrew. This is not the case. Okay, un-unified, non-unified, kept-separate-from ... pick your term. At the moment Phoenician is neither unified nor non-unified with Hebrew *because

Re: ISO 15924 "code"s and "ID"s

From: "Peter Constable" <[EMAIL PROTECTED]> > Could someone please explain why the data tables for ISO 15924 list both > "codes" and "ID"s? ("ID"s are not discussed in the text of the > standard.) My opinion is that "Codes" where defined to be locale-neutral, and easily parsable in locale identifi

Re: Response to Everson Phoenician and why June 7?

Ernest Cline wrote, > > In order for Phoenician to be "disunified" from Hebrew, it must > > first have been unified with Hebrew. This is not the case. > > Well then, nonunification if you wish to be picky about it. Sorry if I offended. Many on this list have referred to the current proposal a

RE: ISO 15924 draft fixes

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Addison Phillips [wM] > I don't care about the order, so long as it is stable over time. Personally I find the > latter form more logical (with the identifier, i.e. the code, first). I agree with Addison here: the most important

RE: ISO 15924 draft fixes

I could use a little help rendering this into French, lest I embarrass myself "The Property Value Alias is defined as part of the Unicode Standard and is provided informatively in the tables here to show how entries in the ISO 15924 code table relate to script names defined in Unicode." -

RE: ISO 15924 "code"s and "ID"s

At 12:02 -0700 2004-05-20, Peter Constable wrote: Well, how about as comments in the plain-text file and on the HTML pages: "The Property Value Alias is defined as part of the Unicode Standard and is provided here as informative information *giggles* to show how entries in the ISO 15924 code table

Re: Response to Everson Phoenician and why June 7?

> [Original Message] > From: <[EMAIL PROTECTED]> > > Ernest Cline wrote, > > > ... This indicates to me that variation > > sequences are a potential solution that should be considered, > > even if it ends up being rejected in favor of disunification. > > In order for Phoenician to be "disunified"

RE: ISO 15924 draft fixes

I don't care about the order, so long as it is stable over time. Personally I find the latter form more logical (with the identifier, i.e. the code, first). I view the English and French names and the "PVA" as merely descriptive or informative information. The code and the ID number should go fi

RE: ISO 15924 draft fixes

At 12:07 -0700 2004-05-20, Peter Constable wrote: > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Everson >Also, it appears you have not fixed a serious error in the >plain-text file: it is not well-structured. Some rows have 6 >columns, and some have 7. That might b

Re: Response to Everson Phoenician and why June 7?

Peter Constable wrote, > I'm sure even Youtie would go for this. Except that she's too busy writing new lyrics for Janis Joplin tunes. Ernest Cline wrote, > ... This indicates to me that variation > sequences are a potential solution that should be considered, > even if it ends up being reject

Re: Response to Everson Phoenician and why June 7?

Peter Kirk wrote, > The solution may be a catch-all, but the problem is a real one. Dr > Kaufman's response makes it clear that to professionals in the field > Everson's proposal is not just questionable but ridiculous. There is > certainly some PR work to be done in this area, not name-callin

RE: ISO 15924 draft fixes

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Michael Everson > >Also, it appears you have not fixed a serious error in the > >plain-text file: it is not well-structured. Some rows have 6 > >columns, and some have 7. > > That might be fixed in the newest one. It is not fix

Re: ISO 15924 draft fixes

> Antoine Leca a écrit : > >> The French name for Hang looks strange. It happened to be "hangul >> (hangul, hangeul)" (after quite a bit of discussion.) Sorry guys. For reasons known to itself, my mailer refused to post in UTF-8 this morning. I meant "hangul(hangul, hangeul)". According to a nati

RE: ISO 15924 "code"s and "ID"s

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Michael Everson > >Calling the other thing "Property Value Alias" would solve the > >problem, but it really ought to be defined somewhere; > > The heading links to it. Not good enough: the plain-text file does not contain links.

RE: Response to Everson Phoenician and why June 7?

I think we should be careful not to introduce new features, such as variation selectors, to new scripts, unless there is a strong reason to do so. The fact that VS are now standard in Unicode does not require every Hebrew software to support them, even by ignoring them. There is a huge cost invol

RE: ISO 15924 draft fixes

At 10:00 -0700 2004-05-20, Addison Phillips [wM] wrote: I concur with Peter. If there are multiple documents now, then I'd like to see a single normative document... It will be the plain-text version, and for the purposes of fixing the current regrettable mess I'm taking it as read that the pla

RE: ISO 15924 "code"s and "ID"s

At 10:14 -0700 2004-05-20, Peter Constable wrote: Calling the other thing "Property Value Alias" would solve the problem, but it really ought to be defined somewhere; The heading links to it. and since it's not mentioned in the standard, then it's status must be informative, and that should be in

RE: ISO 15924 draft fixes

At 09:49 -0700 2004-05-20, Peter Constable wrote: > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Everson I hope this satisfies you. http://www.unicode.org/iso15924/codelists.html If they are consistent and reliable, I'm satisfied with them. I hope you will be preparing

RE: ISO 15924 draft fixes

I concur with Peter. If there are multiple documents now, then I'd like to see a single normative document... and furthermore I would like it to *be* normative (and I'd like to know which one it is). The text file is listed on the web site as the "alternative"... By all means correct errors. Sp

RE: ISO 15924 "code"s and "ID"s

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Michael Everson > There is no solving the problem of the use of "code" in the TC37 and > TC46 standards. That is an old, old argument. True, but making a distinction between "ID" and the "code" can be solved. Calling the other thi

RE: ISO 15924 draft fixes

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Michael Everson > I hope this satisfies you. http://www.unicode.org/iso15924/codelists.html If they are consistent and reliable, I'm satisfied with them. I hope you will be preparing a page for corrigenda / errata. It's not a big

Re: ISO 15924 "code"s and "ID"s

I could change the column heading to "Property Value Alias" and link it to http://www.unicode.org/Public/UNIDATA/PropertyValueAliases.txt -- Michael Everson * * Everson Typography * * http://www.evertype.com

RE: ISO 15924 draft fixes

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Michael Everson > Taking time to put up "an immediate warning" isn't a > good use of my time. I didn't ask for an immediate warning. I will note, though, that incorporating bad data into a product may not be a good use of time fo

Re: ISO 15924 "code"s and "ID"s

At 08:59 -0700 2004-05-20, Peter Constable wrote: Could someone please explain why the data tables for ISO 15924 list both "codes" and "ID"s? ("ID"s are not discussed in the text of the standard.) The Registration Authority (The Unicode Consortium) requested it be added to that tables. Perhaps add

ISO 15924 "code"s and "ID"s

Could someone please explain why the data tables for ISO 15924 list both "codes" and "ID"s? ("ID"s are not discussed in the text of the standard.) I find the inclusion of both under these labels somewhat less than ideal. The term "code" is not consistently used. Most people do use "code" to refer

RE: ISO 15924 draft fixes

Peter, Philippe, I hope this satisfies you. http://www.unicode.org/iso15924/codelists.html It is enough work finding and fixing and figuring out whatever it is that a perl script is and how to make it work. It may seem obvious to you, but it is not obvious to me. -- Michael Everson * * Everson Ty

RE: Response to Everson Phoenician and why June 7?

> Even with a separate Phoenician script, it might be a good idea > to provide variation sequences Hmmm, gives me an idea: For those people that want to unify, would it help if all of the Phoenician characters were considered as variation sequences of Hebrew characters, but for convenience we used

RE: ISO 15924 draft fixes

At 08:10 -0700 2004-05-20, Peter Constable wrote: > >For now I suggest an immediate warning in the ISO15924 web pages, > >explicitly stating that these published tables were in beta, and > >contain incoherences, which are being corrected. > > No. This is purely cosmetic. Let us move on. I find

RE: ISO 15924 draft fixes

> >For now I suggest an immediate warning in the ISO15924 web pages, > >explicitly stating that these published tables were in beta, and > >contain incoherences, which are being corrected. > > No. This is purely cosmetic. Let us move on. I find this cavalier attitude a bit disconcerting. Errors i

RE: ISO 15924 codes for ConScript

> One person wrote, regarding Qaak for Klingon: > > > It's a shame you didn't pick something that could be pronounced in > > tlhIngan Hol, perhaps Qaap for pIqaD. Identifiers are identifiers, not words. Peter Peter Constable Globalization Infrastructure and Font Technologies Microsoft Windo

Re: Response to Everson Phoenician and why June 7?

On 19/05/2004 20:54, John Hudson wrote: Ernest Cline wrote: I would be very surprised if there were such a cybercafe. One that had both a Hebrew-Phoenican and a Hebrew-Hebrew font with the Hebrew-Phoenician as the default would be much easier to believe as a possibility. Still, it is a valid poin

Re: Response to Everson Phoenician and why June 7?

> [Original Message] > From: John Hudson <[EMAIL PROTECTED]> > > Ernest Cline wrote: > > > I would be very surprised if there were such a cybercafe. One > > that had both a Hebrew-Phoenican and a Hebrew-Hebrew font > > with the Hebrew-Phoenician as the default would be much easier > > to believe

Re: ISO 15924 draft fixes

At 06:51 -0700 2004-05-20, Patrick Andries wrote: Antoine Leca a écrit : The French name for Hang looks strange. It happened to be "hangul (hangul, hangeul)" (after quite a bit of discussion.) The name in ISO/CEI 10646 (F) is « hangûl » from a Corean dictionary and a Corean grammar published by

Re: ISO 15924 draft fixes

To terminate with this discussion, I have put online the corrected tables. http://www.rodage.org/pub/iso15924-sheets.html (this is a Excel workbook in HTML format with frames but without "Excel interactivity", that references other URLs in a subfolder; it can be navigated by the tabs at the bottom

Re: ISO 15924 draft fixes

Antoine Leca a Ãcrit : The French name for Hang looks strange. It happened to be "hangul (hangul, hangeul)" (after quite a bit of discussion.) The name in ISO/CEI 10646 (F) is  hangÃl  from a Corean dictionary and a Corean grammar published by the Inalco (Langues O'). Another suggested for

Re: ISO 15924 draft fixes

At 14:44 +0200 2004-05-20, Philippe Verdy wrote: From: "Michael Everson" <[EMAIL PROTECTED]> >It can't be Unicode's UTC alone, as there are >already codes for bibliographic references that >are not (and will never) be encoded separately >in Unicode,so I suppose that there are librarian >or pub

Re: Phoenician (was, Response to Everson Phoenician and why June 7?; was, Archaic-Greek/Palaeo-Hebrew; was, interleaved ordering; was, Phoenician)

On Wednesday, May 19, 2004 9:11 PM, John Jenkins wrote: > You go down to your local cybercafe to read your email from your > grandmother telling you all about your nephew's bar-mitzvah. > Unfortunately, your local cybercafe has no modern Hebrew (or Yiddish) > installed, but they *do* have a Phonec

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> > >It can't be Unicode's UTC alone, as there are > >already codes for bibliographic references that > >are not (and will never) be encoded separately > >in Unicode,so I suppose that there are librarian > >or publishers members with which you have to > >di

Re: ISO 15924 draft fixes

At 13:37 +0200 2004-05-20, Philippe Verdy wrote: > I added Coptic unilaterally. I can't see Coptic for now in your source zip file. It isn't in that file. There are other "duplicate" lines for name aliases that should be listed in changes: I'm not going to list those changes. There is no code or n

Re: ISO 15924 draft fixes

- Original Message - From: "Michael Everson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 19, 2004 10:40 PM Subject: ISO 15924 draft fixes > The Registrar wishes to thank everyone who has taken an interest in > the ISO 15924 data pages, and regrets the imperfections

Re: ISO 15924 draft fixes

At 13:00 +0200 2004-05-20, Philippe Verdy wrote: (I wonder why this file is zipped, given its small size, If uncompressed, downloading it opens it in the browser rather than downloading it. and the fact that the text file is coded in Unix-style end-of-line format, I used Mac OS X TextEdit. not in

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> > At 11:16 +0200 2004-05-20, Philippe Verdy wrote: > >From: "Michael Everson" <[EMAIL PROTECTED]> > >At 03:28 +0200 2004-05-20, Philippe Verdy wrote: > >> >It was in the previous list (see the online HTML table 2). > >> What do

Re: Qamats Qatan (was Response to Everson Phoenician and why June 7?)

At 22:18 -0700 2004-05-19, John Hudson wrote: I don't automatically accept the argument, made by Michael earlier today, that 'There is a requirement for distinction for X in plain-text'. The Universal Character Set is supposed to contain all the scripts of the world. For generations students of

Re: Response to Everson Phoenician and why June 7?

At 20:54 -0700 2004-05-19, John Hudson wrote: Some people seem keen on variation selectors in the same way that others are keen on PUA: as a catch-all solution to non-existent problems. I agree. My mantra is "Variation selectors are pseudo-coding." -- Michael Everson * * Everson Typography * * h

Re: ISO 15924 draft fixes

At 11:52 +0200 2004-05-20, Antoine Leca wrote: [Mailed _and_ posted to the list; UTF-8] On Wednesday, May 19th, 2004 10:40 PM, Michael Everson wrote: I would appreciate it if interested persons could look this over and inform me if they find any further discrepancies between the two which are wo

Re: ISO 15924 draft fixes

At 11:16 +0200 2004-05-20, Philippe Verdy wrote: From: "Michael Everson" <[EMAIL PROTECTED]> At 03:28 +0200 2004-05-20, Philippe Verdy wrote: >It was in the previous list (see the online HTML table 2). What does that refer to? See

Re: ISO 15924 draft fixes

[Mailed _and_ posted to the list; UTF-8] On Wednesday, May 19th, 2004 10:40 PM, Michael Everson wrote: > I would appreciate it if interested persons could look this over and > inform me if they find any further discrepancies between the two > which are worth troubling about. Then we will proceed

Re: ISO 15924 draft fixes

From: "Michael Everson" <[EMAIL PROTECTED]> At 03:28 +0200 2004-05-20, Philippe Verdy wrote:> >It was in the previous list (see the online HTML table 2).> What does that refer to? See http://www.unicode.org/iso15924/iso15924-codes.html (sorry it was Table 1): Sylo 316 Sylot

Re: ISO 15924 codes for ConScript

Two people wrote offline that Seussian Latin Extensions should be Latn, rather than having its own code. This makes perfect sense. I'll change it and add a note to the page. One person wrote, regarding Qaak for Klingon: > It's a shame you didn't pick something that could be pronounced in > tlhI