Re: dvips(k) state and maintainer

2000-01-24 Thread Tom Kacvinsky
Han The Thanh (of pdftex fame) did the work on this module. Tom On Sun, 23 Jan 2000, Tomas G. Rokicki wrote: > Just so you know: > > the dvips in the pretest works *great* on the files that Karsten sent out. > That new writet1 looks good! Who did the work? > > -tom >

Re: dvips(k) state and maintainer

2000-01-24 Thread Tomas G. Rokicki
Just so you know: the dvips in the pretest works *great* on the files that Karsten sent out. That new writet1 looks good! Who did the work? -tom

Re: dvips(k) state and maintainer

2000-01-20 Thread Tomas G. Rokicki
Howdy! Yep, I do dvips. Can you send me the font? (And any other files.) I'll take a look. Tom, does the latest snapshot of tetex actually use the writet1 module to handle font subsetting in dvips? I wasn't aware that had happened yet . . . -tom

Re: dvips(k) state and maintainer

2000-01-20 Thread Tom Kacvinsky
That should be /Encoding 256 array Sorry about the mix up... Tom > > /Encoding 255 array > 0 1 255 {1 index exch /.notdef put} >

Re: dvips(k) state and maintainer

2000-01-20 Thread Tom Kacvinsky
Hi Karsten, I am CC'ing this to the tex-k mailing list. To answer your question, Tom Rokicki is the official maintainer of dvips(k). To answer your question about the encoding problem: Does the original Type 1 font you are subsetting (you wrote partially encoded but I think you really meant su

dvips(k) state and maintainer

2000-01-20 Thread Karsten Tinnefeld
Who is the one who currently maintains dvips? I have some trouble with partially encoded fonts with non-standard encoding and late postscript interpreters in recent hp printers. unfortunately, I have no idea who is the current maintainer. ctan has dvips versions up to 5.67, dvipsk to 5.78a, an