Re: [tlug] Re: Japanese in Xandros/Debian (lost the headers, sorry)

[CL <az.4tlug@example.com>]

Scott Robbins wrote:

> Sigh, once again I deleted too quickly--this is mutt, so there's no
> recovery. 

Mutt is a program name?  I've seen you mention it as a reason for losing 
things a couple of times.  I only ask because I had a lead guide / scout 
in one of my earliest squad commands who called himself "mutt" but I 
didn't think you were the kind of person to channel the souls of people 
who died thirty plus years ago in Cambodia.

Do I politely mention the "A" word (archive) here?

> So, we've gotten to the point where you get the input module but nothing
> happens when you hit shift+space. 

Yes and no ... my message was that we got there and having gotten there 
could not get back there the next time we tried.  I'd installed a bunch 
of fonts from the DVD of installed .ttf and .ttc fonts off of my WIN 
installation into my System Fonts folder.  What I did not mention before 
was that the font installer kept hanging so I manually installed the 
fonts using Konqueror.

> I've seen this and it's often because either the terminal or environment
> doesn't support the locale, or perhaps the fonts can't be found. 

Except, the locale was set for ja_JP -- I changed that before I tried to 
start SCIM.

> One thing that sometimes works is to put the XMODIFIERS and LC_CTYPE
> variables in .bash_profile.  In your .bash_profile try adding
>
> export XMODIFIERS='@im=SCIM'
> export LC_CTYPE=ja_JP.utf8

Okay ... but shouldn't we be looking at why starting SCIM is not 
automatic and repeatable first?  I am trying to figure out why I could 
follow your instructions successfully, install fonts, then find that 
SCIM will not install when called by scim -d any time after that.

> This is for testing only, if we get somewhere with this, we can worry
> about only calling it when needed.  I've also forgotten which terminal
> was being used.  

uxterm

I'm using a KDE desktop, too.  Debian 4.0.

--
CL