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: Tue, 20 Oct 1998 12:55:07 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.3.96LJ1.1b7.981019185606.10189B-100000@example.com>
- References: <Pine.LNX.3.96LJ1.1b7.981019184321.20295D-100000@example.com><Pine.LNX.3.96LJ1.1b7.981019185606.10189B-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "jb" == Jonathan Byrne <jq@example.com> writes: jb> On Mon, 19 Oct 1998, Scott Stone wrote: >> xemacs-mule does this now, without 4-byte. explain that, if >> you dare. jb> The one I have only has support for 22 different language jb> encodings on it's "Set Language Environment" menu, including jb> several different variations on Latin. So my preliminary jb> explanation at this point is "No it doesn't. jb> Nyaanyaanyaanyaanyaa!" :-) To do so would require it to jb> understand every encoding method extent today. Does it? XEmacs does not, because Thai, Ethiopic, and Vietnamese are known to lock up at least one X server hard (the one on the head XEmacs maintainer's development system). GNU Emacs does support all of the national language character sets registered with the ISO that are supported by any generally available system, AFAIK. There are a number of such character sets that are supported by academic research facilities but are not available in free or proprietary format. Neither flavor of Mule supports, nor will they support, Micro$oft's attempt to Balkanize language (and sell multiple copies of WinKludge to the same user) by registering several dozen "Winkludge-<codepage>" encodings, either. I assume that you support them in this decision. I'm sure SS does ;-) jb> Assuming it does, then you could conceivably display all of jb> the national character sets and encoding methods on a page at jb> once. But you could hardly claim that this was simpler than a jb> single encoding that contained all characters that have ever jb> existed in any language that we have records of, plus leaving jb> lots of room for new ones yet to be devised. This will not happen. All of the practical proposals I know of for using more than the first two of the 32767 planes of UCS-4 involve importing national character sets wholesale in variant encodings. You would still have the problem of translating massive amounts of archived data, too. -- 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
- 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: kanji or romaji for Japanese? (was: parallel-port IDE)
- 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