88554 - Xprint module should avoid using GFX fonts unless there is no other option...

Status: VERIFIED FIXED

(Core Graveyard :: Printing: Xprint, enhancement)

Description

[Roland Mainz]

Xprint module still uses tons of GFX fonts in some cases (see example URL).

Workaround:
Set
-- snip --
user_pref("browser.display.use_document_fonts", 0);
-- snip --
in prefs.js

Resulting PS job sizes using S7 or X11R6.5.1 Xprt:
Example URL without workaround: 11139666 bytes of PS code
Example URL with    workaround:   520675 bytes of PS code

Maybe it's usefull to crawl into source and enable this behaviour by default...
:-)

Comment 1

[Roland Mainz]

Fix in bug 92918.

Comment 2

[Roland Mainz]

Filed bug 93771 to get a final solution for this.
I'll file a workaround for now...

Comment 3

[Roland Mainz]

Attachment: Patch for 2001-07-31-08-trunk

Comment 4

[Roland Mainz]

Filed patch (workaround, real fix will be implemented in bug 93771).

Requesting r=/sr= ...

Comment 5

[Brendan Eich [:brendan]]

r=[e-mail]

Comment 6

[Brendan Eich [:brendan]]

Cc'ing cls to check the use of _IMPL_NS_XPRINT.

/be

Comment 7

[kinmoz]

sr=[e-mail]

Comment 8

[Roland Mainz]

Fix checked in
(http://bonsai.mozilla.org/cvsquery.cgi?module=MozillaTinderboxAll&branch=HEAD&cvsroot=/cvsroot&date=explicit&mindate=997275720&maxdate=997276260&who=brade%25netscape.com).

Marking bug as FIXED.

Comment 9

[Masaki Katakai]

I'm now verifying the Xprt bugs, however, I'm not sure how to
verify this bug.

Roland,

could you give the exact instruction how to reproduce
this problem?

Comment 10

[Roland Mainz]

If Xprt uses "GFX fonts" (font glyhs generated from X bitmap fonts) you should
see three things:
- Xprt in X11R6.5.1(and Solaris 2.7/2.8 Xprt) generates "Im1" bitmap per glyph
in the PostScript output
(in X11R6.6 jay hobson added the "bitmap glphy cache")
- the issue above causes large, very large print jobs (you can get easily get 
beyond 50MB for some pages without the "bitmap glyphs cache")
- font quality isn't good

Normally Xprt should either use printer buildin fonts or upload the neccesary
fonts to the printer, GFX fonts should only be used as a fallback solution if
_every_ other option fails...

The issue with this bug was that some CSS stylesheets used explicitly font
families which were only available as X bitmap fonts (the 75DPI
-b&h-lucidatypewriter-* comes in mind while printing http://www.cnn.com/ ...
=:-)

Therefore I set the CSS spec always to "serif" (and filed bug 93771 for getting
a permanent solution for this). In bug 116158 I relaxed this restriction and
allowed some common PostScript font family names beside "serif" (like "times",
"courier" etc.) ...

Comment 11

[Roland Mainz]

Attachment: http://www.cnn.com/ printed with 2002-01-14-08-trunk Xprint module and Solaris 7 Xprt

Comment 12

[Roland Mainz]

Marking VERIFIED per attachment 65423 [details] (which uses only printer builtin fonts)
...