Tell me more ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.
up vote 0 down vote favorite

when running dvips on a dvi (containing just a graph included via an .eps file) the generated ps file "drops" certain characters in the graph (decimal points in the labels on the axes and capital letters in the axis title). Note that the dvi correctly shows the graph in all its details.

However, and this is what puzzling me the output of the dvips command DOES NOT give any error at all. It calls all the correct fonts without any problem.

The fonts called are all CM, and dvips locates them correctly

Any ideas ? Is it possible that certain pfb files are broken without dvips noticing that ?

[Adding that the graph was generated using PyX 0.11 This turned out to be the problem as I note in the comment. a switch to PyX 0.12 solves the issue. I therefore add a PyX tag to this question.]

Here is the dvips output

This is dvips(k) 5.98 Copyright 2009 Radical Eye Software (www.radicaleye.com) ' TeX output 2012.11.07:0003' -> draft2.ps . [1 <./pic/Fig1ext.eps>]

share|improve this question
1  
This could be a viewer issue; try zooming in on the postscript, or using an alternative program to look at the file. Failing that, please make the eps file available for download, and add an example code that reproduces the problem. – Ian Thompson Nov 7 '12 at 19:32
1  
Hi thx for your suggestion. It turned out not to be a viewer problem, but something more subtle. The graph included in the tex document, was generated using PyX (great tool!!). Apparently the version I was using had UniqueID lookup issues for the CM fonts embedded in the PostScript output of the figure, causing certain glyphs to be dropped after a dvips. A recent PyX update solved this. So everything works just fine now. – Mathias Vanwolleghem Nov 8 '12 at 12:21
4  
@MathiasVanwolleghem Unlike a traditional forum, we keep questions and answers separate. Please consider posting a self-answer, and moving the appropriate material from the question. – Joseph Wright♦ Nov 8 '12 at 12:26

1 Answer

up vote 2 down vote

It turned out not to be a viewer problem, but something more subtle. The graph included in the tex document, was generated using PyX 0.11 (great tool!!). Apparently the version I was using had UniqueID lookup issues for the CM fonts embedded in the PostScript output of the figure, causing certain glyphs to be dropped after a dvips. A recent PyX update (0.12) solved this. So everything works just fine now.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.