don simons wrote: > Robin Fairbairns wrote > > i'm assuming you've got a recent enough ghostscript (>=6.01, but > > preferably not 7.00 which mucks up gsftopk), but that would merely > > mean that the dvipdf script would make grotty output, not dvips too. > > To solve a printing problem with Win98, I recently installed gsview 4.0. > (see http://sunsite.dk/pipermail/tex-music/2001-October/000641.html ). It > wouldn't work with whichever ghostscript I had, so not knowing any better, I > installed AFPL ghostscript 7.03 (gswin32.exe).
gs7.03 is (i'm told) ok even on linux, which was what stefan is using. gs7.00 had problems on linux with gsftopk, but i've installed it with no apparent problem on w2k for users at my lab (though i'm using 7.03 for them as of the last install i did). > The printer problem was > solved and I didn't notice any other new problems. I've exercised the setup > with bith bitmapped and postscript fonts. Could you elaborate on your > comment? What is gsftopk? What are the symptoms of the problem? Is it > possible that gsview/gswin32 somehow bypasses it? gsftopk generates pk fonts from type1 ones, for use with old versions of xdvi (the unix previewer). the latest xdvi uses type 1 fonts direct. what i suspect is happening for stefan is that dvips is interpreting whatever map file it finds as saying the fonts are "present in the printer" (so they don't need downloading). or that his dvips is subsetting the fonts incorrectly. aha! there's a thought, stefan -- try -j0 to dvips... _______________________________________________ TeX-music mailing list [EMAIL PROTECTED] http://sunsite.dk/mailman/listinfo/tex-music
