From: Andre W. <wo...@us...> - 2007-07-20 16:43:53
|
Hi Michael, On 25.04.07, Michael SCHINDLER wrote: > The PDF generation with unincluded standard fonts is currently broken: > The minimal example > > from pyx import * > text.set(mode="latex") > text.set(fontmaps="builtin35.map") > #text.set(fontmaps="download35.map") > text.preamble(r"\usepackage{mathptmx}") > c = canvas.canvas() > c.text(0,0, r"$\psi$") > c.writeEPSfile("bloch") > c.writePDFfile("bloch") > > leads to a working eps file, but the pdf file does not show anything. It's not a bug. builtin35.map just isn't the proper map file here. When you specify a map file yourself, you simply need to know what you are doing (I don't see any way out of that using *existing* TeX/LaTeX infrastructure). In case you don't specify any map file -- well -- we still have a problem (depending on your TeX-configuration of course -- I remember some problems with palatino). Point here is, that psfonts.map is correct for postscript only, for pdf, which have less/different fonts included, we should consider using pdftex.map instead (as pdftex does by default). Too bad, that the mapping files are that broken. It seems to me that the pdfTeX guys first started with the psfonts.map (from dvips) (including all its strange syntax) and later realized that they need a slighly modified version and just created their pdf-adjusted version ... pdftex.map. Still using the same strange and limited format. The only thing we should consider for the future (and that's how I read the comment in the CHANGES file) is to use psfonts.map and pdftex.map for postscript or pdf by default respectively. Jörg? Should we go that line? André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript and PDF figures (_/ \_)_/\_/ with Python & TeX: visit http://pyx.sourceforge.net/ |