Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: kinput and kterm SOLVED!!!!!
- To: Tobias Diedrich <ranma@example.com>, tlug@example.com
- Subject: Re: kinput and kterm SOLVED!!!!!
- From: Martin Baehr <mbaehr@example.com>
- Date: Wed, 24 Oct 2001 03:29:34 +0200
- Content-disposition: inline
- Content-type: text/plain; charset=us-ascii
- Delivered-to: tlug@example.com
- In-reply-to: <20011023130427.B24570@example.com>; from ranma@example.com on Tue, Oct 23, 2001 at 01:04:27PM +0200
- List-help: <mailto:tlug-request@example.comsubject=help>
- List-post: <mailto:tlug@example.com>
- List-subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-return-path: <mbaehr@example.com>
- References: <20011022064213.C19323@example.com> <s3telnw6in2.fsf@example.com> <20011022134657.B20628@example.com> <20011022141239.A1121@example.com> <20011022144407.N19322@example.com> <s3tsncb6dci.fsf@example.com> <20011023073330.O19322@example.com> <s3titd64uli.fsf@example.com> <20011023110501.N20628@example.com> <20011023130427.B24570@example.com>
- Reply-to: tlug@example.com
- Resent-from: tlug@example.com
- Resent-message-id: <O9BNEB.A.bdC.Kgh17@example.com>
- Resent-sender: tlug-request@example.com
- User-agent: Mutt/1.2i
On Tue, Oct 23, 2001 at 01:04:27PM +0200, Tobias Diedrich wrote: > AFAIK the C locale supports only 7bit ascii. > en_US supports iso-8859-1, so you can input german. yeah, that was only a rethorical example. > LANG=ja_JP gives me japanese error messages an the like, which I usually > don't want, so I just set LC_MESSAGES=en_US too. i think i need to kill LANG alltogether, it seems to override LC_*; > However, as utf-8 encoding is not really support sufficiently, you can't > input german when using the japanese locale, or rather the japanese > character encoding... > (I know it is theoretically possible with iso-2022, but I have never > seen that actually working...) hmm, of all things unicode should have less problems with german than iso-2022. in any case i am making continuous progress with japanese input, this is really cool. interresting observation: jvim by default writes files in iso-2022-jp. vi 6 does not handle files in iso-2022-jp and writes euc-jp. jvim handles files in euc-jp though. what programs do you use for converting? i found tcs in the debian archive. greetings, martin. -- by the end of 2001 i'd like to find a new job anywhere in the world, doing pike development and/or training and/or unix and roxen system administration. -- pike programmer Traveling in Japan (www|db).hb2.tuwien.ac.at unix (iaeste|bahai).or.at (www.archlab|iaeste).tuwien.ac.at systemadministrator (stuts|black.linux-m68k).org mud.at is.(schon.org|root.at) Martin B"ahr http://www.iaeste.or.at/~mbaehr/
- Follow-Ups:
- Re: kinput and kterm SOLVED!!!!!
- From: Tobias Diedrich <ranma@example.com>
- Re: kinput and kterm SOLVED!!!!!
- From: David Santinoli <u235@example.com>
- References:
- kinput and kterm
- From: Martin Baehr <mbaehr@example.com>
- Re: kinput and kterm
- From: Mike Fabian <mfabian@example.com>
- Re: kinput and kterm
- From: Martin Baehr <mbaehr@example.com>
- Re: kinput and kterm
- From: Tobias Diedrich <ranma@example.com>
- Re: kinput and kterm
- From: Martin Baehr <mbaehr@example.com>
- Re: kinput and kterm
- From: Mike Fabian <mfabian@example.com>
- Re: kinput and kterm SOLVED!!!!!
- From: Martin Baehr <mbaehr@example.com>
- Re: kinput and kterm SOLVED!!!!!
- From: Mike Fabian <mfabian@example.com>
- Re: kinput and kterm SOLVED!!!!!
- From: Martin Baehr <mbaehr@example.com>
- Re: kinput and kterm SOLVED!!!!!
- From: Tobias Diedrich <ranma@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: jvim vs. vim 6
- Next by Date: Re: How to use samba mangled japanese filenames as CLI args?
- Previous by thread: Re: kinput and kterm SOLVED!!!!!
- Next by thread: Re: kinput and kterm SOLVED!!!!!
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links