add "a12n" to the list...
http://lists.kabissa.org/mailman/listinfo/a12n-collaboration wasn't there a Red Hat Chili Peppers song called c13n? Barry
Re: Origin of the term i18n/top 10 list
Guys, Poor Mark was just expressing a preference, it hardly requires a debate. And he was right to correct my comment about numeronyming (can I make it a verb?) not being a trend. Probably creating them is a trend. Actually using them seems to be rare. (I have been doing a few more searches after Mark's mail. I am starting to wonder if search engines parse strings like "i18n" correctly or perhaps throw them away as uninteresting for search purposes.) However, if we must debate the value of i18n vs. internationalization, let's make it more interesting. For example, I will express my reasons for being the i18nguy instead of the internationalizationguy or the internationalizationmalehumanbeing or the intn'lguy as a top 10 list. (Would you abbreviate that acronymically as T10L or numeronymically as t10t now?) Here is: The I18nGuy's top ten list of "reasons Tex chose to be I18nGuy": 10: Size- I18nGuy fits on a license plate, parking space, bus. card. 9: Accessibility- Even if Dave had broken both thumbs he still has enough digits left to count to 18. 8: Collation- It sorts ahead of L10nGuy 7: Uniqueness- Contractions like "In'l'n" means something else in Hawaiian. (Somebody tell me what it means.) 6: Secrecy- Brits and Ozzies can't tell from the spelling I am American! 5: Panache- It gives me an air of mystery! 4: G11n- In Turkey, there are only 2 spellings, with and without the dot on the "i", instead of 16! (4 i's in i18n) 3: Style- I can order my drinks "shaken, not stirred" like that other numeronym: 007 2: Speed- Typing i18n instead of internationalization, get's me back to the bar faster... And the number one reason, I went with "I18nGuy"... 1: Dollars- Saving a fortune paying by the letter for personal ads "seeking I18nDoll" ;-) OK, I am going back to the bar... i18nguy David Possin wrote: > > I am thankful that these short forms exist, as I must use them a lot in my > work where space is priceless: charts, tables, project plans, etc. > > Not only does it save a lot of time (especially now where I can type only > with 1.5 hands - broken thumb) but it looks more neat in overall > documentation. I agree, in a text or book I would not necessarily use them > if I wasn't sure who the readers are and what their level of knowledge in > our area is. > > Definitely better than InTeRn@i*nAlIʒ@i*n which OE automatically identifies > as an email address ... > > Dave -- - Tex Texin cell: +1 781 789 1898 mailto:Tex@;XenCraft.com Xen Master http://www.i18nGuy.com XenCrafthttp://www.XenCraft.com Making e-Business Work Around the World -
Re: GCGID for U+03B8
Asmus Freytag wrote: >> IBM has a Web page containing many PDF charts of code pages, and they >> have the same problem: some show one GCGID for U+03B8, others show the >> other one. > > Wouldn't you be able to tell by the shape associated with the GCGID? There were no shapes to look at. The tables in the Unicode 1.0 book, and tables-in-electronic-form associated with Unicode 1.1, identified the Unicode character U+03B8 with GT61 in the mapping tables for MS-DOS code page 869 and EBCDIC code page 875, and with GT610002 for Windows code page 1253 and various East Asian DBCS code pages. In both the Unicode 1.0 and 3.0 books, U+03B8 is represented with the "straight" theta glyph, while U+03D1 (not listed in any of the Unicode 1.x tables) is represented with the "loopy" glyph. Markus's answer seems to indicate that GT61 is what really identifies the Greek lower-case theta. The "0001" suffix specifically calls for the loopy glyph and "0002" calls for the straight glyph, while "" is a generic suffix (exact glyph unspecified). But as I wrote in a separate message to Markus, it gets worse; there are other Unicode characters (mainly symbols) for which two or more *very* different GCGIDs are listed, depending on which reference source you use. It seems that GCGIDs predate any formal distinction between character and glyph of the type adopted by Unicode, making it somewhere between difficult and impossible to create a 1-to-1 mapping table between GCGIDs and Unicode -Doug Ewell Fullerton, California
Re: Origin of the term i18n
I c u rn't up 2 date - we R there - check chat & messenger - urgh D2e - Original Message - From: "Kenneth Whistler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, October 11, 2002 4:23 PM Subject: Re: Origin of the term i18n > Mark, > > > > Mark, I am curious why you find this term so distasteful? Is it the > > > algorithm itself or just a general objection to acronyms and the like? Or > > > something else entirely? > > > > I find this particular way of forming abbreviations particularly ugly and > > obscure. It is also usually unnecessary; looking at any of the messages > > brought up by Google, the percentage of 'saved' keystrokes is a very small > > proportion of the total count. And when it leaks out into the general > > programmer community, it just looks odd. > > > > For me, it is on the same order as using "nite" for "night", or "cpy" for > > "copy". > > u shuld just be glad u wont live to see the day when netspeak roolz > and ur goofy language is rOxXoRed! > > --K1n >
Re: Origin of the term i18n
I am thankful that these short forms exist, as I must use them a lot in my work where space is priceless: charts, tables, project plans, etc. Not only does it save a lot of time (especially now where I can type only with 1.5 hands - broken thumb) but it looks more neat in overall documentation. I agree, in a text or book I would not necessarily use them if I wasn't sure who the readers are and what their level of knowledge in our area is. Definitely better than InTeRn@i*nAlIʒ@i*n which OE automatically identifies as an email address ... Dave - Original Message - From: "Barry Caplan" <[EMAIL PROTECTED]> To: "Mark Davis" <[EMAIL PROTECTED]>; "Tex Texin" <[EMAIL PROTECTED]>; "Unicoders" <[EMAIL PROTECTED]>; "NE Localization SIG" <[EMAIL PROTECTED]> Sent: Friday, October 11, 2002 4:08 PM Subject: Re: Origin of the term i18n > At 12:20 PM 10/11/2002 -0700, Mark Davis wrote: > >> Mark, I am curious why you find this term so distasteful? Is it the > >algorithm itself or just a general objection to acronyms and the like? Or > >something else entirely? > > > >I find this particular way of forming abbreviations particularly ugly and > >obscure. > > I think it is a meme that is catching on and it serves various purposes more important than "saving keystrokes": > > - these are important words that describe entire fields of study in many specialties > - many of them (internationalization, globalization, e.g) are in the common vernacular, with vague denotations and possibly negative connotations in the general public > - As such the words are seriously overloaded and confusing > - Not only that, but they are spelled differently in various parts of the English speaking world, which affects indexing. > - They are long and hard to spell for non-native speakers (and probably most US native speakers too) > - They are toungue twisters for all, especially for some non-native English speakers > - The overloading of definitions, even within scholarly fields, is calling out for a separation and branding (do a search on localization and see how many branches of science you get) > - Long words really suck for design purposes. You would be limited to about 9 point type on your business card if anything other than your title included "Internationalization" > --snip--
Re: Capital Letter H with line below
Kevin Brown wrote: > I have a map of Israel which has the transliterated names Hadera and > Hefa typeset with a line below their first letter, CAPITAL H. > > On the same map, I have yet to find a place name that uses the > LOWERCASE h with line below. Try Reẖovot, about 60 km south by west of H̱adera. -Doug Ewell Fullerton, California