Re: [PyX-devel] Missing glyphs when including PyX files

[Michael S. <m-s...@us...>]

Salut André,

On 18/02/12, André Wobst wrote:
> However, it is interesting to note, that this is a rather new issue.
> To my understanding it is related to recent changes in the type1
> computer modern fonts I observed elsewhere (see
> http://sourceforge.net/mailarchive/forum.php?thread_name=4E95F322.70505%40users.sourceforge.net&forum_name=pyx-devel).

Yes, I remember that comment, but did not follow closely.

> When you use latex and dvips on this later file and you have the new
> versions of the computer modern type1 fonts installed, the glyph a
> is not displayed in the output even though it is contained in the
> postscript file. There is something wrong in the postscript file,
> and it has nothing to do with the DSCs. (You can remove all DSCs and
> the problem remains.) Your DSC commands will result in the embedding
> of full font (without stripping) by dvips. This is not needed and
> not correct.

Have many thanks for the thorough analysis. You convinced me that it
is not a DSC issue.

> 2. Consider the case that you use a font in the figure, which you do
> not use in the document. Inserting the DSCs you suggested will
> result in the full embedding of the font in the "outside" document
> for no valid reason at all. This is due to the fact that dvips
> "thinks" that those font informations you mark in the DSCs are
> "DocumentNeededFonts"-entries. This is wrong, we properly embed all
> the fonts.

OK, you are right. I will undo the changes in pswriter.

> We basically do have two options to address this bug directly.
> 
> 1. We could clear all font information in the beginning of the PyX
> Postscript files by the following small code: "(*) {undefinefont}
> 128 string /Font resourceforall" – as I suggested in July last year
> already. But that time I suggested it as a patch to dvips (in
> special.pro). However, we could move it on top of your PyX
> Postscript output too. This is rather trivial to do. Just insert
> this line prior to the font resources in the eps files of the
> figures (for example immediately after the %%BeginProlog DSC) and
> the whole issue goes away.
> 
> 2. We could remove the fancy search for a font with the same
> UniqueID from the fonts we embed in our Postscript output. Not
> difficult either. I suggest to go for the second option. See
> changeset 3242 for the implementation.

So, it was the "{restore} if" (and a bit more) which I suspected in
the beginning, whithout really knowing what it was. You seem to speak
postscript quite fluently!
I also opt for the second solution, although it is worth keeping the
other in mind for the case one has to fix a given eps file by hand --
one never knows ...

Michael