Re: Please Help with FVWM

[Shigeru Abe <sabe@example.com>]

> 
> I don't know what "ujis.fvwmrc" is supposed to do.  You should say at
> least that much unless you know it's a topic of common interest.
>

"Ujis.fvwmrc" is apparently the Japanese version of system.fvwmrc.
All the menus are in Japanese (its readable using KON).

>     (0) I assume that Japanese works everywhere but fvwm ....

So far. XKlock will display Japanese but XCalendar will not. Mosaic
and Netscape 2.0 b2 work, but nothing else will.  There is a locale
directory and I wonder if I need to do anything with that.
(usr/lib/X11/locale)

>     (1) Even if it does, it is not necessarily true that ujis.fvwmrc
>         uses your preferred fonts.  Try changing the fonts specified 
>         there.

I'm using the fvwm that comes with JE.  It allows multiple fonts so
you can select both a Japanese and Latin alphabet.

ie. Font	k14,a14

Normal fvwm will give an error after the comma.

>     (2) check the console (probably Ctrl-Alt-F1) for error messages.
>         if that's not where your console lives, try looking in
>         /var/log/messages and /var/log/syslog (these may live in
>         /var/adm if you're not FSSTND-compliant).  They may be quite
>         big, I suggest using "tail -100 /var/log/messages | less",
>         then truncating the log files :-)
>     (3) try removing fvwm from .xinitrc, and put an xterm or kterm as
>         the last thing.  (This is essential, or you'll never be able
>         to open a window!)  Now run fvwm from that xterm (don't kill
>         that xterm or you'll kill your X server too).  This allows you 
>         to play with your fvwm settings without killing the X server
>         (you can do that with the Restart fvwm menu item) and see the
>         fvwm error messages (if any) in the xterm (you can't do that
>         without switching virtual consoles with Restart).
>
Ok, I'll try this.

> The next possibility is that ujis.fvwmrc requires patches to fvwm.
> This seems unlikely, but I know that X11R4 and maybe X11R5 permitted
> implementations to handle 8 and 16 bit fonts with different calls.
> Maybe fvwm simply doesn't understand 16 bit fonts without patches.
> Have you read that configuration file through?  Often such information
> doesn't make it into readmes (disgustingly enough).
>

I'm using the fvwm with JE, I assume the patches are included since
the file size is always larger than the "normal" fvwm.

> Where do I get ujis.fvwmrc?  Maybe I'll play with it....  Good luck.
>

JE always includes ujis.fvwmrc in fvwm.tgz. So, if you don't want
the entire je, you can just get fvwm.tgz in the xclt directory.

Shige Abe