User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b13pre) Gecko/20110305 Firefox/4.0b13pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b13pre) Gecko/20110305 Firefox/4.0b13pre When printing the same page (http://lucire.com) to PDF, the spacing goes haywire. The fonts that Firefox is accessing are PostScript Type 1s. When printing a page using OpenType fonts (e.g. http://autocade.net), I continue to have missing glyphs—again the ligatures and, in this case, a special Th ligature that is in the OpenType tables to replace the T–h combination. Reproducible: Always When printing to my Epson Stylus Photo 830U, I notice that the ligatures (e.g. ﬁ) are missing and replaced with a dot. So there seems to be some issue with the print engine.
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: unspecified → Trunk
Reporter, can you attach the pdf of the file you printed Thanks
For the issue with PS Type 1 fonts, I filed bug 640528 (sorry, I missed this one at that time), so let's focus here on the missing-glyphs-for-OpenType-ligatures case. To investigate that, it would be helpful to have a testcase that demonstrates the problem without being dependent on specific, proprietary fonts; Jack, can you reproduce it with a freely-available font such as Linux Libertine O, DejaVu, etc?
Hi Jonathan: I'm off to download and install them now. Interestingly, the stylesheet for autocade.net specifies PT Serif (a freely available family) but prints in my default. What I will do is set my default to something that is publicly available and see how it goes.
I wasn't able to generate any new PDFs: Firefox (build of March 14) crashed both times, once in the middle of generating (while the font table was being built) and once at the beginning (soon after pressing the 'Print' button). bp-f7feab5a-6f0d-499a-bf52-da2752110315 bp-7cc5034a-fd2c-47b6-8946-ec4842110315
I have filed Bug 642017 on the crashing issue. I'll attach the one relevant PDF here. It appears the ligatures are appearing (fi), which suggests the tables are working—just that something else has happened between the two builds that have stopped my PDF generation.
You need to log in before you can comment on or make changes to this bug.