neubauer@bsu-ucs.uucp (Paul Neubauer) (10/04/90)
Keywords: metafont ymir thai rmit style file
Hi there, folks,
I'm having a wierd problem (aren't they all?) with trying to build and
test a Thai font that I got from ymir. (And, BTW, I also can't seem to
find a .sty file that is referred to in the sample files that come with
the fonts. If anyone knows where to find, or has, the file RMIT-STD.STY
that is used in the rmit thai .tex files, I would be very grateful.
From what I can see, this file contains all of the macros that should
make it reasonable to use the fonts.)
I ftp'ed the .mf files from [anonymous.tex.babel.thai.rmit] and, after
fixing a bunch of corruptions that seem to have appeared in the
transmission, I have built one of the fonts in the family. The listing
shows:
< This is METAFONT, Vax/VMS Version 1.7 (preloaded base=bsu 90.5.18)
< 3 OCT 1990 18:18
< **&plain
<
< *mag:=\magstep1;
<
< *input thair20
< (PAUL$FILES:[MF.THAI.RMIT]THAIR20.MF;1
< (PAUL$FILES:[MF.THAI.RMIT]THAIBASE.MF;1)
< (PAUL$FILES:[MF.THAI.RMIT]R.MF;1)
< (PAUL$FILES:[MF.THAI.RMIT]ALL.MF;1
< (PAUL$FILES:[MF.THAI.RMIT]CHAR87.MF;2 [135])
< (PAUL$FILES:[MF.THAI.RMIT]CHAR88.MF;1 [136])
< (PAUL$FILES:[MF.THAI.RMIT]CHAR89.MF;3 [137])
< ...
As you can see, the characters start at 135. I copied the .tfm and .pk
files to the relevant directories so they could be found and then I
tried to run the THAI-TEST.TEX file that also came from the same source.
(It was the only .tex file that I could use, since the others required
RMIT-STD.STY.) The LaTeX'ing went fine until I tried to look at the
results. I got the following error:
< $ xdvi thai-test
< Character code 135 outside range, file thair20.360pk
(needless to say, there is no file THAIR20.360PK, it is called
THAIR20.PK and when I tried renaming it to .360PK, an even worse error
occurred:
< $ ren tex_fonts:[360]thair20.pk .360pk
< %RENAME-I-RENAMED, TEX_FONTS:[360]THAIR20.PK;1 renamed to
< TEX_FONTS:[360]THAIR20.360PK;1
< $ xdvi thai-test
< Font file:TEX_DISK:[DECUS.TEX.FONTS.][360]thair20.pk
< Font file:TEX_DISK:[DECUS.TEX.FONTS.][1800]thair20.pxl
< thair20.1800pxl [not found]
< xdvi: Not all PXL files were found
This is obviously not the (only) problem, so I restored the name to .PK.)
I considered the possibility that the problem was with xdvi (though that
seemed unlikely) and next tried to convert the file to a printable file
using dvi2ln3, with the following result:
< $ dvi2ln3 thai-test
<
< Ln03DVI V1.2-015
<
< Font load to contain 50 glyphs.
< Font thair20: magnified 120%, loading PK file [360]thair20.pk,
< %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=000BB9BE,
< PC
< =0002D734, PSL=03C00001
< %TRACE-F-TRACEBACK, symbolic stack dump follows
< module name routine name line rel PC abs PC
<
< PK PKScanForGlyph 1050 0000003D 0002D734
< PK PKGetGlyph 893 00000050 0002D589
< LN03FONTS copy_pk_char 1715 0000002F 0002CC21
< LN03FONTS add_txf_to_lnf 650 000002DA 0002B1AE
< LN03DVI make_font_load 1343 00000384 0002868F
< LN03DVI main 471 000001AB 000273AB
which means that DVI2LN3 (evidently originally named LN03DVI) crashed
during the PKScanForGlyph routine, presumably while trying to find glyph
135. Still, we know that metafont did create a glyph 135, since it
shows up in the listing. What could be going on here?
====
Paul Neubauer 00prneubauer@bsu-ucs.uucp or 00PRNEUBAUER@BSUVAX1.BITNET
neubauer@bsu-cs.uucp
{backbones}!iuvax!bsu-cs!neubauerdhosek@sif.claremont.edu (Hosek, Donald A.) (10/05/90)
In article <42847@bsu-ucs.uucp>, neubauer@bsu-ucs.uucp (Paul Neubauer) writes... >I have built one of the fonts in the family. The listing >shows: >< (PAUL$FILES:[MF.THAI.RMIT]CHAR87.MF;2 [135]) >< ... >As you can see, the characters start at 135. >The LaTeX'ing went fine until I tried to look at the >results. I got the following error: >< $ xdvi thai-test >< Character code 135 outside range, file thair20.360pk >and next tried to convert the file to a printable file >using dvi2ln3, with the following result: >< $ dvi2ln3 thai-test >< Ln03DVI V1.2-015 >< Font load to contain 50 glyphs. >< Font thair20: magnified 120%, loading PK file [360]thair20.pk, >< %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=000BB9BE, >< PC >< =0002D734, PSL=03C00001 >< %TRACE-F-TRACEBACK, symbolic stack dump follows > Still, we know that metafont did create a glyph 135, since it >shows up in the listing. What could be going on here? It looks like you have two drivers that don't support fonts with more than 128 characters (or to be more precise, fonts with character codes greater than 127). One of the many reasons that I go on tirades against PXL support (support of which encourages this sort of limitation). Your LN03 driver should be replaced anyway; there is a newer driver by Brian Hamilton Kelly, dvitoln03 (available from ymir.claremont.edu in [anonymous.tex.drivers.ukln03] which supports 256 character fonts. As for xdvi, a more recent version _may_ have fixed the high-character support problem, but if not, I'll tell Scott Allendorfer to put this in his pipeline. -dh --- Don Hosek TeX, LaTeX, and Metafont support, consulting dhosek@ymir.claremont.edu installation and production work. dhosek@ymir.bitnet Free Estimates. uunet!jarthur!ymir Phone: 714-625-0147 finger dhosek@ymir.claremont.edu for more info