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: ikko-@example.com (Kazuyuki Okamoto)
- Date: Sun, 7 Jun 1998 17:20:33 +0900
- Cc: ikko-@example.com (Kazuyuki Okamoto)
- Content-Type: text/plain; charset=iso-2022-jp
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Hi, At 15:50 06/07/98 +0900, Jonathan Byrne wrote: >-----Original Message----- >From: Matthew J. Francis <asbel@example.com> >To: tlug@example.com <tlug@example.com> > >> Anyway, If you've used Windows at all, perhaps you've >come across a >>little free Japanese word processor called (strangely >enough) JWP; it has > >I've heard of it, but I've never used it or seen it myself. > >>builtin EDICT searching and several useful sorts of >character-lookup >>method, but perhaps what I liked about it most is that the >input works >>sensibly, as you describe. Kanji could be input without >losing >>editability, and without focus gratuitously jumping around >the place. > >Japanese input works this way in all proprietary OSes too, >and I confess that they spoil you. The main reason that I >spend as much time under Windows as I do is simply because >Japanese input works so well, and even works in a lot of >English applications. For example, my computer at home has >the English version of Outlook Express, but it has >absolutely no trouble with reading Japanese or accepting >Japanese input, with the exception that it doesn't take >Japanese input correctly in subject lines. The localized >version has no problem with that. Overall, it's very nicely >internationalized. If I were working only in English, I >would have no reason to use Windows except for those times >when I need to produce an English version of a document that >was created in MS Office, which is what's used in my >company. At home, I would just need it for Internet Phone. > >Because I'm spoiled by the quality of the Japanese input >front-ends and conversion engines on <insert proprietary OS >here>, I do find myself often hoping that something just as >good will one day emerge on Linux/Unix. > >> With that thought, one of the first items on my list of >things to >>attempt to add into Yudit was JWP-like >"never-leave-the-spot" Kanji >>entry. Yudit does already support Canna and KInput2, but I >can't see >>a really obvious way of making KInput2 behave right >either - so >>essentially I was looking at adding a direct interface to >Canna without >>going through KInput2. > >Here's a "think big" suggestion/idea: one of the problems >that I see in the general world of Unix Japanese input is >that there are too many different ways of doing it: Kinput2, >Canna, Wnn, SKK, Egg, etc., (I must be leaving out >something), whereas the proprietary OSes essentially have >just one for each platform. Atok is available as an >aftermarket item, but it is apparently fully compatible with >the ones from MS/Apple/IBM, since you can just install it >and use it. I'm confused as to why anyone buys it when the >ones that are included standard seem perfectly satisfactory, >but people do. Anyway, I think that Unix needs what the >other guys have got: just one way to do it. The Japanese Input Method is a Server-Client type system. Server --------- Client ---------------------------------- Application cannaserver ---- kinput2 (with canna support) ------------ netscape ---- onew (included jvim with canna support) - jvim ---- canuum ---------------------------------- mule Wnn(jserver) --- kinput2 (with wnn support) -------------- dp/note --- uum ------------------------------------- --- onew (included jvim with wnn support) --- --- xwnmo - X ------------------------------- BTW, cannaserver, kinput2 and netscape has executiion order. 1st, at boot time, cannaserver was run by root user. setenv LANG ja_JP.ulis ( set from .cshrc ) setenv XMODIFIERR @example.com=kinput2 ( set from .cshrc ) 2nd, kinput2 was run by user for Japanese Input with & (back ground). 3rd, netscape was run by same user for Japanese Input. -- | Kazuyuki Okamoto <ikko-@example.com> | http://www.st.rim.or.jp/~ikko-/XF332/DocIndex.html | http://www.st.rim.or.jp/~ikko-/XF331/DocIndex.html | XFree86 Docs in Japanese | PGP Key fingerprint = 56 D2 1E 57 22 12 3B 3C AB 36 55 37 23 27 F0 61 -------------------------------------------------------------- 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
Home | Main Index | Thread Index
- Prev by Date: Re: Japanese input (was RE: tlug: Japanese)
- Next by Date: tlug: open source survey
- 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