Re: Warning to fontList resource setters: append a colon [was: Japanese menus in netscape-ja-resource-476 won't display correctly]

[Steven Mueller <diffusor@ugcs.caltech.edu>]

Well, I found out what my troubles were:  I had set the fontList
resource improperly:
*.fontList: -ricoh-ms\ mincho-medium-r-normal---140-*-*-*-*-*-*
When I set the following resources as follows, it works fine:

Netscape*fontList: \
    -adobe-helvetica-medium-r-*--12-*-*-*-*-*-iso8859-*;\
    -ricoh-ms\ mincho-medium-r-normal--12-*-*-*-*-*-*-*:
! Avoid Motif Weakness in Japanese locale.
Netscape*.urlBarItem*XmTextField.fontList: \
    -adobe-helvetica-medium-r-*--12-*-*-*-*-*-iso8859-*
Netscape*XmFileSelectionBox*XmTextField.fontList: \
    -adobe-helvetica-medium-r-*--12-*-*-*-*-*-iso8859-*

So I needed to include a colon after the font.  How come this colon is
necessary in this one isolated case? 
! this works:
Netscape*fontList: \
    -ricoh-ms\ mincho-medium-r-normal--12-*-*-*-*-*-*-*:
! this fails:
Netscape*fontList: \
    -ricoh-ms\ mincho-medium-r-normal--12-*-*-*-*-*-*-*


Anyway, sorry about the false alarm; since I couldn't find any other mention
of such a problem on the mailing lists, deja, or google, I thought it
was likely that the problem was my own.  Anyway, now off to create a
Netscape.normal app-defaults file that has English.

Why would I do such a thing after spending all that time on trying to
get the Japanese interface to work?  Well, apart from the principle of
the thing, I really wanted to be able to display and input Japanese in
forms, and I also wanted my Japanese bookmarks to show properly in the
menu.  I wonder if there is an easy way to get Netscape to recognize
the LANGUAGE environment variable like gtk apps do, so I can just set
it to "en" when I don't feel like translating menu options whenever I
want to configure some options... :)

What would be a good way to do such a thing, anyway?  As a kludge, one
could write a small script that depending on the setting of LANGUAGE,
load Netscape with the proper app-defaults, and then run that instead
of netscape directly.  I wonder if Motif supports a cleaner method?

Steve

On Sun, Dec 03, 2000 at 05:30:25PM -0800, Steven Mueller wrote:
> Hello there,
> 
> I recently upgraded to the latest navigator in Woody and tried
> installing netscape-ja-resource-476 to get input Japanese form buttons
> to display properly and to enable Japanese input.  This works fine,
> but no matter what I try, the menu options are all gibberish.  Mozilla
> displays Japanese fine in menus and bookmarks, so I wonder if it's a
> Motif problem I'm having?  Anyway, I've tried variations of the
> following environment variable settings and Xresources:
> 
> (from my .xsession:)
> 
> # Set the interface language to english, allow Japanese input
> export LANGUAGE=en
> 
> <snip...>
>
> Netscape*fontList: -ricoh-ms\ mincho-medium-r-normal--14-*-*-*-*-*-*-*
> 
> Setting the fontList resource does indeed change the appearance of the
> Motif menu options as promised, but still no Japanese is rendered.
> Instead I get a bunch of Yen symbols.

Of course, the answer is to put a colon at the end.

> Any ideas on what I could do to fix this up properly?  Do you suppose
> this is a bug in the netscape-ja-resource-476 package?  I never did
> try the preceeding netscape-ja-resource-475 package since it had that
> dependancy issue with locale-ja or whatever, so I don't know if that
> would have worked with my setup or not.
> 
> Thanks for your time and any input!  My head is beginning to spin from
> sifting through all those Japanese help sites on older and possibly
> not quite relevant issues with communicator 4.04 and Japanization...
> :)
> 
> Steve
> 
> -- 
> Steven Mueller
> diffusor@ugcs.caltech.edu
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-japanese-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-- 
Steven Mueller
diffusor@ugcs.caltech.edu