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

Reproduction du message de Berthold K.P. Horn

This message went out of the list, i thought it could be of interest
to its readers anyway,

-- BEGIN included message

At 06:34 PM 98/10/15 +0200, Thierry Bouche wrote:

>But, wait a minute, i've been using dvips for years, doing partial
>downloading as soon as possible, and we're printing tons of papers
>using my  Utopia/Lucida fonts, without never hitting that problem!

>I'm puzzled! 

Normally you will not see such problems, because you will not be accessing
characters that are not in the font, and you are not using a broken PS interpreter.
The problem occurs in two cases I know of:  

(i) you try to access one of the
characters that is not in the partial font --- this puts a blank in the glyph cache
for that font - which is all that is seen later even when using a font that has that 
character.  This will not normally occur with DVIPS, since it includes all the
characters it plans to access.

(ii) You are using Acrobat Reader (I have seen this bug mostly with the Mac Reader).
In this case Acrobat and/or ATM retains some information about the font that
includes which glyphs are actually present.  When you then look at a second
PDF file that has the same font (and using the same PS FontName) but with
different glyph complement, you get blanks.

These problems can be avoided by using a different name.  Changing the
UniqueID may nt be needed and may not help, since ATM ignores it.

Regards, Berthold.

Berthold K.P. Horn
Cambridge, MA		mailto:bkph@ai.mit.edu

-- END included message