Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Japanese input (was RE: tlug: Japanese)
- To: <tlug@example.com>
- Subject: Re: Japanese input (was RE: tlug: Japanese)
- From: "Jonathan Byrne" <jpmag@example.com>
- Date: Mon, 8 Jun 1998 20:47:37 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="us-ascii"
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
-----Original Message----- From: Stephen J. Turnbull <turnbull@example.com> > jb> For example, my computer at home has the English version of > jb> Outlook Express, but it has absolutely no trouble with reading > jb> Japanese or accepting Japanese input, with the exception that > jb> it doesn't take Japanese input correctly in subject lines. > jb> The localized version has no problem with that. Overall, it's > jb> very nicely internationalized. > >For the user. From the point of view of (some of) the people who >receive your mail, and the people who are forced to write software to >hide your broken mail from those who don't see it, Outlook >Expectorates. You've known I hold that opinion for a while now. And I'm sure you're right, too. But I keep on using it because the features it provides are so good that it's pretty darn hard to give it up. However, as inferior as Netscape Mail is to OE, if Netscape would get their shit together and make it Japanese-capable like it is on other platforms, I'd use it. I do often use the Japanese-hacked version of Pine, and I will say that as a text-based mail package, it's very impressive. My only complaints in terms of features are that it lacks nested folders, clickable URLs (coming in Pine 4, though) and a nice, convenient rule wizard to make up message sorting parameters. But I haven't dug into the docs yet to find out if it supports that one at all; it may be expecting you to handle all of that with procmail before the mail gets to Pine. BTW, does the Sparc Solaris version of IE include Outlook Express, and if it does, is the mail broken in the same way that it is in the Windows version? >God save us from Han Unification! However, Stallman and Handa are I don't want Han unification, just Japanese input unification under Linux :-) >trying to arrange for exactly (the One True Input Method, not Han >Unification) that by ignoring all non-Quail input methods in Mule. I >hope they fail. Me too. Maybe it's about time RMS just kind of, like, retired, or something :-) >The obvious name is "Japanese Input on Linux Terminals," because JILT >is exactly what I would do to it, with quite high probablility. Why don't you join the campaign to world domination of Japanese input instead? :-) That way you could do loads to make sure it worked exactly the way you wanted it to while you dominated the world :-) Cheers, Jonathan -------------------------------------------------------------- Next TLUG Meeting: 13 June Sat, Tokyo Station Yaesu gate 12:30 Featuring Stone and Turnbull on .rpm and .deb packages Next Nomikai: 17 July, 19:30 Tengu TokyoEkiMae 03-3275-3691 After June 13, the next meeting is 8 August at Tokyo Station -------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- Re: Japanese input (was RE: tlug: Japanese)
- From: Scott Stone <sstone@example.com>
- Re: Japanese input (was RE: tlug: Japanese)
- From: "Matthew J. Francis" <asbel@example.com>
Home | Main Index | Thread Index
- Prev by Date: RE: tlug: printer problems
- Next by Date: RE: tlug: printer problems
- Prev by thread: Re: Japanese input (was RE: tlug: Japanese)
- Next by thread: Re: Japanese input (was RE: tlug: Japanese)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links