[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Printing problem (Conflicting font name?)

Berthold wrote:
>At 03:34 PM 10/19/98 +0100, Lars Hellström wrote:
>>I just wanted to mension that it seems like partial font downloading is not
>>the cause of the problems I mensioned, since the dvips in OzTeX does not
>>seem to do this by default (and knowing my colleagues, none of them are
>>very likely to have told it to do so either).
>and Textures doesn't do partial font downloading (this would be important
>since in your example - as far as I remember - the Textures job went first).
There would not necessarily come a Textures job first, it appears the
problem does arise anyway. I also doubt Textures does partial font
downloading, since I have the impression that BSR does not give priority to
printing trickeries. (BTW, I have still not been able to pinpoint _any_
font downloading in the things Textures send to the printer. But shouldn't
the printer report some sort of error if a document tries to use a font it
does not have? I haven't seen that either, despite my requesting the
printer to give a full report of all errors.)

>>The idea about some kind of font management going on seems more likely.
>>OzTeX and Textures use different PS versions of the Computer Modern fonts
>>(that is,when you tell OzTeX to use PS fonts, since it uses PK fonts by
>I believe they would be essentially the same, since the fonts that come with
>Textures are the ones that BSR/Y&Y/AMS etc. put on CTAN.  The actual
>file format is different, but by the time QuickDraw unpacks the Mac fonts
>into the PS file for Textures it is in `PFA' format, the same as what DVIPS
>produces from PFB files.  Maybe compare the PS produced by the two?
Well, you're defintely wrong about this one. The CM cut that comes with
Textures is by BSR (at least they claim the copyright). The CM cut that
comes with OzTeX is called BaKoMa. I've checked the cmr10 fonts of both
sets, and the UniqueIDs are not the same, so I very much doubt any printer
driver should be able to "unpack" them as the same thing.

Concerning the formats: The dvips in OzTeX can read LWFNs as well as pfas
and pfbs. The fonts in both families are actually stored in LWFN format.

Lars Hellström