Dvips and BaKoMa type 1 fonts
Our department's current tex installation was obtained from the texlive5 CD. Recently, one of my colleagues discovered some characters missing from the printed version of one of his documents, and on further investigation we discovered that dvips was not finding characters 0 to 31 in the BaKoMa type 1 fonts. (It works OK if one turns off fonts subsetting by changing the <'s to <<'s in bakomaextra.map). It looks like dvips is not correctly extracting the encoding vector from the pfb file. This surprised me, since it works just fine with the fptex distribution I'm using on my PC, and I thought that dvips would be essentially the same in the two places. I suggested to our system manager that he get a newer version of dvips from tetex-beta, and he did so, but it still didn't work. I'm no programmer, but I can see in writet1.c some code which is clearly meant to deal with "getinterval" "putinterval" stuff that the BaKoMa fonts use in setting up their encoding vectors; so it really ought to work. Can anyone suggest what might have gone wrong? Has something been compiled incorrectly here, or is it true that tetex-beta dvips doesn't handle font subsetting for the BaKoMa type 1 fonts? Bob Howlett
RE: PS viewers.
Hello, The problem is solved now as pointed out in my previous email. The puzzle is "How did gv work with gs 5.50?". George -Original Message- From: Mats Bengtsson [SMTP:[EMAIL PROTECTED]] Sent: Monday, 28 May 2001 14:36 To: George J. Wakileh Cc: [EMAIL PROTECTED] Subject:Re: PS viewers. That's weird. I just tried the same gv 3.5.8 with both gs5.50 and gs6.50 and it works without any problems. Are you sure that you didn't compile in any full paths to gs in the gv binary? In State->Ghostscript options ..., it should just say Interpreter: gs /Mats
RE: PS viewers.
Hello Thomas, Thanks very much for pointing this out. For some reason, my gs 6.50 was compiled without x11 x11alpha x11... When I combined all devices under DEVICE_DEVS and left DEVICE_DEVS1, ..., things worked out fine. Now, gv 3.5.8 works fine again. Kind regards, George -Original Message- From: Thomas Anders [SMTP:[EMAIL PROTECTED]] Sent: Monday, 28 May 2001 09:28 To: George J. Wakileh Subject:Re: PS viewers. Hi, Your gs 6.50 is "broken", i.e. built without the x11 devices. Here is what my gs 6.50 has: Available devices: x11 x11alpha x11cmyk x11cmyk2 x11cmyk4 x11cmyk8 x11gray2 x11gray4 x11mono appledmp iwhi iwlo iwlq t4693d2 t4693d4 t4693d8 tek4696 ap3250 epson eps9mid eps9high epsonc lp8000 lq850 st800 stcolor hl7x0 uniprint cdeskjet cdjcolor cdjmono cdj500 cdj550 cdj670 cdj850 cdj880 cdj890 cdj970 cdj1600 djet820c deskjet djet500 djet500c dnj650c paintjet pj pjetxl pjxl pjxl300 hpdj stp laserjet ljet2p ljet3 ljet3d ljet4 lj4dith ljetplus lj5mono lj5gray cljet5 lp2563 bj10e bj200 bjc600 bjc800 lbp8 lips3 lxm5700m lex7000 lex5700 lex3200 lex2050 declj250 dl2100 la50 la70 la75 la75plus ln03 lj250 ccr cp50 ibmpro imagen jetp3852 m8510 necp6 oce9050 oki182 oki4w okiibm r4081 sj48 xes pbm pbmraw pgm pgmraw pgnm pgnmraw pnm pnmraw ppm ppmraw pkm pkmraw plan9bm inferno dfaxhigh dfaxlow faxg3 faxg32d faxg4 tiffcrle tiffg3 tiffg32d tiffg4 tiff12nc tiff24nc tifflzw tiffpack psmono psgray psrgb bit bitrgb bitcmyk mgrmono mgrgray2 mgrgray4 mgrgray8 mgr4 mgr8 pcxmono pcxgray pcx16 pcx256 pcx24b pcxcmyk pngmono pnggray png16 png256 png16m sgirgb bmpmono bmp16 bmp256 bmp16m cgmmono cgm8 cgm24 cif jpeg jpeggray miff24 pdfwrite bbox pswrite epswrite pxlmono pxlcolor nullpage Rebuilt gs 6.50 and both gs and gv will display your document fine. HTH, Thomas -- Thomas Anders <[EMAIL PROTECTED]> Hahn-Meitner-Institut Berlin, Germany
Re: PS viewers.
> Hello, > > Thanks very much for all the feedback I got on PS viewers. > > In fact, only a week ago, I downloaded gv 3..5.8, managed to compile it and > it worked fine. I then had to upgrade my gs5.50 to gs6.50 to handle > computer modern type 1 fonts. Now, gv no longer works. It gives > "Postscript interpreter failed on main page". That's weird. I just tried the same gv 3.5.8 with both gs5.50 and gs6.50 and it works without any problems. Are you sure that you didn't compile in any full paths to gs in the gv binary? In State->Ghostscript options ..., it should just say Interpreter: gs /Mats
Re: I can't find "tex.fmt"
> I must generate the format file.. > Sorry I don't know this. > > I tried "fmtutil --byfmt=tex" as you wrote. > > I made it! Thank you for your helping!! Normally, the format files are generated by calling texconfig init This usually happens when running "make install" (installation from sources) or automatically by install.sh (when installing binaries). So, something must have gone wrong with your installation. But, if texconfig init does not generate any error now, you do have a working system. Thomas
Re: I can't find "tex.fmt"
Hi Thomas At 10:10 午前 01/05/28 +0200, Thomas Esser wrote: > > Where is the "tex.fmt"? > > What happens if you run > fmtutil --byfmt=tex > Ah-.. I must generate the format file.. Sorry I don't know this. I tried "fmtutil --byfmt=tex" as you wrote. I made it! Thank you for your helping!! [EMAIL PROTECTED]
Re: teTeX releases
> Is there a new teTeX release underway anytime soon? No. My target for a new release is somewhere at the end of this year when - hopefully - the next web2c release is out. teTeX is based on web2c-7.3.1 and I want to skip over 7.3.2 and 7.3.3 which are already out (with only very few improvements over 7.3.1). I would have updated pdftex in teTeX-beta, but since it depends on web2c-7.3.3 now, this is not as easy as it used to be... Thomas
Re: I can't find "tex.fmt"
> Where is the "tex.fmt"? What happens if you run fmtutil --byfmt=tex Thomas
