Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- To: tlug@example.com
- Subject: Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Mon, 19 Oct 1998 15:29:05 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.3.96LJ1.1b7.981019133330.9015D-100000@example.com>
- References: <Pine.LNX.3.96LJ1.1b7.981019103806.20295g-100000@example.com><Pine.LNX.3.96LJ1.1b7.981019133330.9015D-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "jb" == Jonathan Byrne <jq@example.com> writes: jb> They would most likely have been kanji-enabled from the jb> outset. Uh-uh. Look at history. jb> If not, they would have been kana-enabled from the outset, jb> with kanji following as soon after that as technically jb> possible. This is what happened. But had the initiative come from the East, possibly the whole thing would have been postponed for much longer, as the Japanese and Chinese might very well have fixated on Han characters, making the initial hurdle much higher (remember, you need four to ten times the display resolution for kanji that you do for the uppercase Roman alphabet). jb> As a result, we would have far fewer problems with jb> m17n today. I think the real hope for M17N is the fact that compared to working with Asian languages, doing M17N with European languages only is relatively easy, and we have standards (Unicode and POSIX locales) to shoot down and replace with something better. Compare the approaches of Mule and POSIX or X. True, Mule is much more multilingual, but it does nothing to encourage translation to new languages; it provides no framework for that. Rather, it encourages each project to do it differently. I also don't see the Japanese, Koreans, and Chinese cooperating on M17N if it isn't imposed from the outside (if they hadn't participated in Unicode/UCS, Xerox, MS, and ANSI would have done it to them, making it much worse). At least for the Europeans, the languages of the dominant nations all fit into ISO-8859-1 and _one_ byte. I can't see the Japanese, Chinese, and Koreans (not to mention the Vietnamese and Taiwanese) quietly getting together and creating Unified Han in two bytes (look at the sound and fury created when that was enforced from the outside), nor do I see them being willing to jump to 3 or 4 bytes. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +1 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "XEmacs rules." --------------------------------------------------------------- Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Meeting: 12 December, 12:30 Tokyo Station Yaesu central gate --------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- From: Jonathan Byrne <jq@example.com>
- References:
- Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- From: Scott Stone <sstone@example.com>
- Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- From: Jonathan Byrne <jq@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: GCC compiler question
- Next by Date: Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- Prev by thread: Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- Next by thread: Re: tlug: kanji or romaji for Japanese? (was: parallel-port IDE)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links