From owner-freebsd-hackers Thu Jan 19 04:00:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA17891 for hackers-outgoing; Thu, 19 Jan 1995 04:00:29 -0800 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA17883 for ; Thu, 19 Jan 1995 04:00:27 -0800 Received: from fedora.x.org by expo.x.org id AA18754; Thu, 19 Jan 95 06:59:41 -0500 Received: by fedora.x.org id AA20024; Thu, 19 Jan 1995 06:59:40 -0500 Message-Id: <9501191159.AA20024@fedora.x.org> To: Peter da Silva Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Internationalization (was Re: CVS stuff) In-Reply-To: Your message of "Thu, 19 Jan 1995 04:09:33 CST." <199501191009.EAA13451@bonkers.taronga.com> Date: Thu, 19 Jan 1995 06:59:40 EST From: Kaleb Keithley Sender: hackers-owner@FreeBSD.org Precedence: bulk >Has "vi" been updated to the point where it will display > > y with dieresis > >instead of > > 0xff > >When you enter "y in Xterm? > >It doesn't in 1.1.5.1. I don't know how you get vi to even display 0xff when you enter compose"y, If I have a ydiaeresis key on my keyboard, which I can get by using xmodmap, e.g. 'xmodmap -e "keysym F6 = ydiaeresis"', then I have no trouble at all with vi. Ironically I don't even seem to need cs8 on the tty, which I would've thought I'd have needed, but you definitely need -istrip. But adding keys with xmodmap is far from ideal, in fact it's pretty ugly. It might be tolerable for writing exclusively in German, Spanish, or Italian, which only have a few extra characters, but it's out of the question for French and maybe the Scandinavian languages. What's even uglier is that xterm hasn't been internationalized yet, so it will pass compose sequences straight through, although I think it silently swallows the compose key. If xterm were internationalized then I'm confident that compose sequences would work fine, because xterm would intercept the compose sequence and send the composed character through to the application. It's not that hard to add i18n to xterm, several people have done it, and there are a couple of variants like hterm and kterm that might suffice, if nothing else as models for adding i18n to xterm. Note that for you'll also need ISO8859-1 locale support for X i18n to work, which neither 1.1.5.1 nor 2.0 have, unless you used the LC_CTYPE file I posted here a while ago, or got it from -current. -- Kaleb KEITHLEY