Re: Common Locale Data Repository Project

2004-04-23 Thread Hideki Hiura - [EMAIL PROTECTED]
> From: "Peter Constable" <[EMAIL PROTECTED]>
> > due to the strong perception of OpenI18N.org as
> > opensource/Linux advocates, even though CLDR project is not
> > specifically bound to Linux.
> It is hard to look at OpenI18N.org's spec and not get the impression
> that all of that group's projects are not bound to some flavour of Unix.

We understand what you mean. Sometime perception is very important, 
and that's why we thought it was a good idea to transfer CLDR.

As we started as Linux Internationalization Initiative(li18nux.org) and
later changed name and charter as OpenI18N.org to accommodate wider
platforms and platform neutral I18N technology developments, any
projects at OpenI18N.org are not limited to Linux/Unix.

> CLDR doesn't have to be tied to any particular platform -- after all,
> it's just a collection of data.

Yup! So hopefully this move would help more parties to join the
projects.
That would definitely help global interoperability for all platforms
and help everybody.

> But I don't think you can honestly say that OpenI18N isn't tied to a
> particular family of platforms

Most of our current projects are mainly for some flavour of Unix,
since most of the participants' expertise and interests are for those
platforms but we are not limited nor have to be bound to them.

The only requirement for the projects in OpenI18N.org is to be open to
everyone, to be developed in open process and to be opensourced.

For example, one of the projects I run, the platform neutral
multilingual distributed Unicode input method framework, IIIMF, runs
on Windows as well, and I honestly hope Microsoft to adapt to IIIMF in
the future release of Windows, so that we can unite unicode input
method framework regardless of platform.

Best Regards,
--
[EMAIL PROTECTED],OpenI18N.org,li18nux.org,unicode.org,sun.com} 
Chair, OpenI18N.org/The Free Standards Group  http://www.OpenI18N.org
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA   eFAX: 509-693-8356



Re: Common Locale Data Repository Project

2004-04-22 Thread Hideki Hiura - [EMAIL PROTECTED]
> From: "Philippe Verdy" <[EMAIL PROTECTED]>
> Is that a contribution of the Unicode Consortium to the OpenI18n.org
> project (former li18nux.org, maintained with most help from the
> FSF), or a decision to make the OpenI18n.org project be more open by
> pushing it to a more visible standard?

More on the latter, but slightly different. We believe it would be
good for both opensource community and commercial IT industry that we
transfer (at least a part of) the project to Unicode Consortium, after
hearing the concerns on difficulty of some commercial companies to
join the project due to the strong perception of OpenI18N.org as
opensource/Linux advocates, even though CLDR project is not
specifically bound to Linux.

We hope this transfer would gain further participations from wider
audiences.

Regarding confusions, I have to say it is anticipated, since the project
is still in transition(for example, OpenI18N.org side has not been
finished necessary procedure to finalize this, so OpenI18N.org does
not have a press release statement ready yet - this announcement is a
little too early), I guess it will all be sorted out as time goes by. 

--
[EMAIL PROTECTED],OpenI18N.org,li18nux.org,unicode.org,sun.com} 
Chair, OpenI18N.org/The Free Standards Group  http://www.OpenI18N.org
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA   eFAX: 509-693-8356




Re: Historians- what is origin of i18n, l10n, etc.?

2002-10-10 Thread Hideki Hiura

> From: Markus Scherer <[EMAIL PROTECTED]>
> Barry Caplan wrote:
> > There is a link with the story on the fron page of www.i18n.com
> Nice story, similar to the one with Gary Miller. It seems like we
> have three stories of origin now (with mid-'80s DEC).  The i18n.com
> version does not date the MIT meeting, does it?

It must be '89, when the X Window System Internationalization
team at MIT got formed for X11R5 release, as what the article
on i18n.com refers as, "a committee working on the standards for
xwindows". (By the way, "xwindows" is incorrect, no plural please ;-)
it should be written as X Window System :). 
The statement I posted earlier,

hiura> The acronym "I18N" appeared before 1991, since I recall I have
hiura> already used I18N in '89 ;-).

was exactly refering to the use of "I18N" in the committee the article
on i18n.com referring.  As some of you may remember ;-), I was a part
of this committee, so I know this committee was not the origin of the
term I18N.

We've created two mailing lists at MIT for the X Window System
Internationalization activity, called mltalk(multilingual talk) and
i18n-si (Internationalization sample implementation) back on those
days.

DEC was heavily involved in the development of X Window System
since very early phase, I can imagine there were some idea exchanges
on the naming, so it is possible that the rep. of DEC passed the
hint to this committee.

--
hiura@{freestandards.org,OpenI18N.org,li18nux.org,unicode.org,sun.com} 
Chair, Li18nux/Linux Internationalization Initiative,  http://www.li18nux.org
Chair, OpenI18N/Open Internationalization Initiative, http://www.OpenI18N.org
Board of Directors, Free Standards Group,http://www.freestandards.org
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA   eFAX: 509-693-8356












Re: Historians- what is origin of i18n, l10n, etc.?

2002-10-10 Thread Hideki Hiura

> From: "Winkler, Arnold F" <[EMAIL PROTECTED]>
> Sometime around 1991 in a IEEE P1003.1 (POSIX) meeting, Gary Miller (IBM)
> was writing on the blackboard.  After having spelled out
> Internationalization a few times, he first abbreviated it to I--n and a bit
> later (obviously after counting the letters in between) used I18N.  Sandra
> might have been at the meeting, and Keld - they might be able to confirm my
> recollection.

The acronym "I18N" appeared before 1991, since I recall I have
already used I18N in '89 ;-).

The beginning of this kind of acronym was S12N(Scherpenhuizen) at
DEC, as far as on the record, as an email address for him on DEC VMS.

By 1985, I18N became an acronym for Internationalization in the I18N 
team at DEC, by following this Scherpenhuizen's S12N convention.

Among the standard organizations, the /usr/group (It became UniForum
later) was the first one using I18N as an acronym for
Internationalization, in '88.

--
hiura@{freestandards.org,OpenI18N.org,li18nux.org,unicode.org,sun.com} 
Chair, Li18nux/Linux Internationalization Initiative,  http://www.li18nux.org
Board of Directors, Free Standards Group,http://www.freestandards.org
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA   eFAX: 509-693-8356






Re: TIM - A Table-base Input Method Module

2002-07-22 Thread Hideki Hiura
> From: Arthit Suriyawongkul <[EMAIL PROTECTED]>
> anybody here interesting in this Table-based Input Method ?
>   http://sourceforge.net/projects/wenju/
> i've got this site from gtk-i18n-list.

I have not looked at this one yet, but you may also want to take a look at
IIIMF(http://www.li18nux.org/subgroup/im/IIIMF) which has something similar,
called ude(user defined engine) as a table based IM.
Also recently, XML based IM, EIMIL(Extensible IM interface Language) is 
ntroduced to IIIMF, which you can combine the table based IM, the
portable XML based logics, and backend dictionay lookup server.

You can retrive the source of this as follows;

cvs -d -d:pserver:[EMAIL PROTECTED]:/cvsroot co -r exp-EIMIL-1 im-sdk

The following is the sample XML based IM definition, which you can
find in im-sdk/server/programs/language_engines/canna.

This sample shows how you can combine those table/logic and backend
dictionary lookup server(in this case, Japanese Canna dictionary
lookup server).

---




  



  


  

  
  

  
"a""あ"
"i""い"
"u""う"
"e""え"
"o""お"

"xa"   "ぁ"
"xi"   "ぃ"
"xu"   "ぅ"
"xe"   "ぇ"
"xo"   "ぉ"

"ka"   "か"
"ki"   "き"
"ku"   "く"
"ke"   "け"
"ko"   "こ"

"kya"  "きゃ"
"kyi"  "きぃ"
"kyu"  "きゅ"
"kye"  "きぇ"
"kyo"  "きょ"

"ga"   "が"
"gi"   "ぎ"
"gu"   "ぐ"
"ge"   "げ"
"go"   "ご"

"gya"  "ぎゃ"
"gyi"  "ぎぃ"
"gyu"  "ぎゅ"
"gye"  "ぎぇ"
"gyo"  "ぎょ"

"sa"   "さ"
"si"   "し"
"su"   "す"
"se"   "せ"
"so"   "そ"

"sha"  "しゃ"
"shi"  "し"
"shu"  "しゅ"
"she"  "しぇ"
"sho"  "しょ"

"sya"  "しゃ"
"syi"  "しぃ"
"syu"  "しゅ"
"sye"  "しぇ"
"syo"  "しょ"

"za"   "ざ"
"zi"   "じ"
"zu"   "ず"
"ze"   "ぜ"
"zo"   "ぞ"

"ja"   "じゃ"
"ji"   "じ"
"ju"   "じゅ"
"je"   "じぇ"
"jo"   "じょ"

"zya"  "じゃ"
"zyi"  "じぃ"
"zyu"  "じゅ"
"zye"  "じぇ"
"zyo"  "じょ"

"ta"   "た"
"ti"   "ち"
"tu"   "つ"
"te"   "て"
"to"   "と"

"cha"  "ちゃ"
"chi"  "ち"
"chu"  "ちゅ"
"che"  "ちぇ"
"cho"  "ちょ"

"tya"  "ちゃ"
"tyi"  "ちぃ"
"tyu"  "ちゅ"
"tye"  "ちぇ"
"tyo"  "ちょ"

"da"   "だ"
"di"   "ぢ"
"du"   "づ"
"de"   "で"
"do"   "ど"

"dha"  "でゃ"
"dhi"  "でぃ"
"dhu"  "でゅ"
"dhe"  "でぇ"
"dho"  "でょ"

"dya"  "ぢゃ"
"dyi"  "ぢぃ"
"dyu"  "ぢゅ"
"dye"  "ぢぇ"
"dyo"  "ぢょ"

"na"   "な"
"ni"   "に"
"nu"   "ぬ"
"ne"   "ね"
"no"   "の"

"nya"  "にゃ"
"nyi"  "にぃ"
"nyu"  "にゅ"
"nye"  "にぇ"
"nyo"  "にょ"

"ha"   "は"
"hi"   "ひ"
"hu"   "ふ"
"he"   "へ"
"ho"   "ほ"

"fa"   "ふぁ"
"fi"   "ふぃ"
"fu"   "ふ"
"fe"   "ふぇ"
"fo"   "ふぉ"

"hya"  "ひゃ"
"hyi"  "ひぃ"
"hyu"  "ひゅ"
"hye"  "ひぇ"
"hyo"  "ひょ"

"ba"   "ば"
"bi"   "び"
"bu"   "ぶ"
"be"   "べ"
"bo"   "ぼ"

"bya"  "びゃ"
"byi"  "びぃ"
"byu"  "びゅ"
"by