Bug 609

Summary: print job gets flushed from buffer on SPARCprinterE
Product: xprint Reporter: Jonathan Walther <krooger>
Component: Fonts: OtherAssignee: Roland Mainz <roland.mainz>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: high CC: MostAwesomedude
Version: unspecifiedKeywords: patch
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: http://reactor-core.org/religion/ezekiel.html
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
clears use of FT internals, switches on FT support in Xprint none

Description Jonathan Walther 2004-05-07 17:30:57 UTC
The HTML generated from Mozilla to my Lexmark Optra R+ is way too big, and of an
unsuitable version level; my Postscript engine only supports 2014.500, not 2015.
 However, even when ghostscript converts this PS to level 1, the printer still
flushes the buffer without indicating that it has reached it's memory or
complexity limit.

The SPARCprinters do not contain all level 2 fonts in their roms; some of the
level 2 fonts may need to be downloaded for things to work correctly.
Comment 1 Drew Parsons 2006-01-25 16:20:12 UTC
Created attachment 4459 [details] [review]
clears use of FT internals, switches on FT support in Xprint

This patch 
a) switches on Freetype support in Xprint (PS driver).
b) fixes usage of Freetype internals psout_ftpstype3.c

Note that it not a complete fix for full freetype support. Remaining issues are

1) use of ttf2pt1 by the type1 handler
2) use of lib/XFont/src/FreeType/ftfuncs.h, not exported by the Xfont module

To build Xprt without freetype support, use --disable-freetype in the autogen
step.
Comment 2 Drew Parsons 2006-01-25 16:21:18 UTC
damn sorry about that, wrong bug. bugzilla is crazy, throws you on to some other
random bug for no reason
Comment 3 Corbin Simpson 2011-09-13 13:27:50 UTC
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

Also adding "patch" to expedite triage in the future.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.