*BSD News Article 54219


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!news.mtu.edu!newsxfer.itd.umich.edu!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!mercury.near.net!noc.near.net!public.x.org!kaleb
From: kaleb@x.org (Kaleb KEITHLEY)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Composing International Characters
Date: 9 Nov 95 15:18:25 GMT
Organization: X Consortium
Lines: 36
Message-ID: <kaleb.815930305@exalt>
References: <47fjfg$a7s@news.puug.pt> <47jcjb$nbq@uriah.heep.sax.de>
NNTP-Posting-Host: exalt.x.org
X-Newsreader: NN version 6.5.0 #5

j@uriah.heep.sax.de (J Wunsch) writes:

>Joao Neves Cabral <jcnc@eppet.eppet.pt> wrote:

>>My problem now is how to write composed characters. I haven't found  
>>anything related to it in the OS. For example, when I type "'" followed 
>>by "a", I would like to get an "a" with an accent.
>>

>However, if you're running XFree86, it has rudimentary compose
>character support.  

What's the difference between "rudimentary compose ... support" and any
other kind of compose support?

The real answer is that X11 has had extensive support for international-
ization (i18n) and localization (l10n) since R5 -- XFree86 has it because
X has it. 

Unfortunately not very many applications in the freely redistributable 
domain have been modified to take advantage of it. XFree86's xterm is 
one program that has been modified. GNU Emacs 19.30 (not available yet) 
will use X i18n code to do compose processing. All you have to do for 
xterm is make sure it runs in the right locale, i.e. set your LANG 
environment variable to something appropriate for you; see /usr/share/locale 
for a list of locale names to use.

(Note that the XFree86 xterm is only internationalized for one-byte
character sets and won't work for multi-byte locales like Japan, China,
or Korea. For those you still need to use cxterm or hterm.)

--

Kaleb KEITHLEY
X Consortium