tlug: Dad-blamed Netscrape again

[Matt Gushee <matt@example.com>]

Hi, folks--

Once again I'm trying to install a muriyari-nihongo Netscape. This time 
the one from the Vine Linux distribution (CD from Linux Japan). Once
again I'm getting nothing but

Bus Error

&*Q#%$#@&*$!@!@#!

There seems to be a problem with the fonts. The README contains the
following instructions:

$BJ#?t%5%$%:$N%U%)%s%H$KBP1~$9$k$?$a$N%j%=!<%972(B
($B4D6-JQ?t(B XFONTSIZE={small,normal,large} $B$K$h$C$F@example.com(B)

$BA0Ds$H$9$k(B font $B%j%=!<%9$N=q$-49$((B
$B%7%9%F%`%U%)%s%H!'(B
-alias-fixed-*--<$B%5%$%:(B>-*-{iso8859-1,jisx0201.1976-0,jisx0208.1983-0}
[for those w/ nihongo-challenged systems, that thing in the angle
brackets is "size"]

Now, I'm not quite sure how to interpret this. Clearly this is not the 
literal string to put in fonts.alias (I *guess* that's where it's
supposed to go). My best guess is that this means you make separate
entries for each encoding, all at a size of your choice -- e.g.:

-alias-fixed-*--12-*-iso8859-1

... and so on. Does that look right?

:: UPDATE: strace results suggest Netscoop is indeed choking on the
:: fixed font aliases. But just in case, there's more:

Or maybe the problem is with the proportional fonts. The README also
calls for 

-adobe-helvetica-*-iso8859-1
-aliastt-mincho-*-jisx0208.1983-0 (X-TT $B$K$h$k(B TrueType $B%U%)%s%H(B)

I have X-TrueType. My Mincho font works (at least it works for TeX,
GV, non-muriyari Netscape, etc.). I'm using Dynalab Heisei Mincho
W3. Its fonts.dir entries (generated by mkttfdir) look like this:

DFHsm3.ttc -DynaLab-DFHSMincho-W3-r-normal--0-0-0-0-c-0-jisx0208.1983-0
bw=0.5:DFHsm3.ttc -DynaLab-DFHSMincho-W3-r-normal--0-0-0-0-c-0-iso8859-1
bw=0.5:DFHsm3.ttc -DynaLab-DFHSMincho-W3-r-normal--0-0-0-0-c-0-jisx0201.1976-0

Hmm. There's some question in my mind of how to properly alias this. I 
guess the left side of the fonts.alias entry should be the above
string (-aliastt-mincho- ...). But what goes on the right side? Do I
use the exact string that's in fonts.dir, or ....?

I've noticed one other thing that may be part of the problem. If I
reinstall a working 'Scrape after a bum installation, the new one
continues to die with Bus Errors. Evidently the messed-up one remains
in memory and prevents the new one from working. Is there a way (at
user level) to flush a program (or its residue) out of memory, so that 
I don't have to reboot when this happens?

Hoping for your sage advice,

Matt Gushee
Oshamanbe, Hokkaido
-------------------------------------------------------------------
Next Nomikai: March 19 (Fri), 19:30  Tengu TokyoEkiMae 03-3275-3691
Next Technical Meeting: April 10 (Sat), 12:30   place: Temple Univ.
-------------------------------------------------------------------
more info: http://tlug.linux.or.jp                     Sponsor: PHT