On Sun, Nov 12, 2006 at 09:45:23AM +0100, Alberto Hernando wrote:
> 
> Hi.
> 
> Thanks for your explanations. I'll check if things go as you say should go. 
> Only one question: how do you set utf-8 for X and, say, iso-8859-15 for 
> console? 

 I was going to say that you don't wnat to do that, but on looking a
bit more deeply I can see that for many common West European
languages that will work nicely.  The big thing you need to watch
out for is probably the euro symbol (€) - the iso-8859-15 glyph for
that is now the funny-looking 'currency symbol' in UTF-8.

 So, for a desktop system try 8859-15 in your .bash_profile so that
a login at the console will use it, and UTF-8 everywhere else
including the LFS sysconfig and /etc/profile.

 I use startx while I'm building a system, that would inherit the
login locale, so I'd need to try exporting UTF-8 in .xinitrc.  Once
the system is mostly built, I use gdm in mode 5 with .xsession and
that doesn't reference ~/.bash_profile so the default UTF-8 would be
in effect (and in my case .xsession is a symlink to .xinitrc which
would anyway set UTF-8).

> To me, the most important thing here is handling text files with non-ascci  
> characters in the file and possibly in the name. This means good X 
> configuration, I think.
> 
 Yes - extra TTF fonts as in blfs, fontconfig (local.conf), and
decent applications that can use fontconfig (e.g. by telling
browsers to use 'serif' 'sans' 'monospace' - the names in local.conf
which give a list of fonts to try - instead of specifying e.g.
'DejaVu Sans').  That isn't a criticism of DejaVu, it's very good
for most of Western Europe, but as you stray further afield it
starts to show its limits.

 In your original post, you said you could type and see japanese
characters - out of interest, how do you type them, and into which
application(s) ?

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to