Acknowledgement sent to [email protected]: Extra info received and forwarded to list. This might explain why the bug cannot be reproduced by Jonas. This fixes especially LP: #780935. -- Till Kamppeter
A colorbar on > the right with negative labels produces postscript-eps output which > displays ok with gv or evince. Acknowledgement sent to JP Bruns
Description Matt 2009-11-02 12:03:21 PST I'm trying to convert eps figures created with the python package matplotlib into pdf figures; however, when I do this the figure fonts are sometimes mangled Copy sent to Debian Printing Team
Reported by: Geoffroy Desvernay
Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Could be a broken program, orpossibly a bad font. Comment 2 Ralph Giles 2009-11-02 12:24:25 PST Confirmed with HEAD (r10257). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721137 Copy sent to Debian Printing Team
Tags: amd64 apport-bug natty Edit Tag help Related branches lp:ubuntu/oneiric/cups AZ (m-dev) wrote on 2011-05-11: #1 BootDmesg.txt Edit (51.4 KiB, text/plain; charset="utf-8") CupsErrorLog.txt Edit (2.4 KiB, text/plain; charset="utf-8") CurrentDmesg.txt Edit (870 If you continue to a /FontBBox of [0 0 1 -58], the text is displayed correctly (I've tried 58 since it seem to be the largest height of the four bitmap When viewing the PDF with xpdf the errors Error: Bad bounding box in Type 3 glyph Error: Missing or bad Type3 CharProc entry are reported (duplicated many times) and some characters Do you have any customizations in your matplotlibrc file?
It does take a few seconds. > I haven't actually investigated it properly, but I do see a few of these: > Error: Bad bounding box in Type 3 glyph > see here It can be made much faster by using bounding box specified by d1 command instead of \FontBBox. cupsfilter -m application/vnd.cups-pdf -p /etc/cups/ppd/
Sign up for the SourceForge newsletter: I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. Evince on the other hand does not complain. I really don't know much of PostScript, but that looks like a [0 0 0 0] FontBBox, meaning "autodetect" ? this page Please don't fill out this field.
Why don't > > poppler prints Type3 fonts directly? > Any chance of a patch? > > > Another suspicious thing is number of calls of SplashClip::test. Can you send me (off-list) the ps/eps and pdf files in question? The arXiv appears to be using an SVN version of gs tagged as 8.71.
Only > > partialy clipped characters should call SplashClip::test, but it seem > > that they're incorrectly detected. Not sure if relevant, but skimming through your Postscript it seems to contain bitmapped fonts (i.e. Comment 3 Matt 2009-11-02 15:34:17 PST This problem was first noticed in connection with this paper: http://arxiv.org/abs/0910.2773 The PS version is fine but figure 2 on page 11 of the PDF Should I try to go back?
Could this perhaos be an issue of broken fonts? I have this problem specifically with statements from Chase bank. The TTF-to-Postscript font conversion library in matplotlib (ttconv) was hard-coded to use the "Standard" Postscript encoding (which defines the set of glyphs available for use), and "Standard" doesn't include the "/minus" Get More Info Mike SourceForge About Site Status @sfnet_ops Powered by Apache Allura™ Find and Develop Software Create a Project Software Directory Top Downloaded Projects Community Blog @sourceforge Resources Help Site Documentation Support Request
Re: [matplotlib-devel] Bug in eps output of matplotlib From: Michael Droettboom