Closed
Bug 72028
Opened 23 years ago
Closed 23 years ago
Xprint does not render tables correctly which spans over multiple pages...
Categories
(Core Graveyard :: Printing: Xprint, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: roland.mainz, Assigned: roland.mainz)
References
()
Details
Attachments
(1 file)
306.08 KB,
application/postscript
|
Details |
Xprint in 2001-03-12-08-Mtrunk does not render tables correctly which spans over multiple pages. Table cells printed on one page are not continued correctly on the following page. Tinderbox status (http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey-Ports) is an good example for this... I'll attach a PostScript file (generated using Solaris 7 Xprt/108376-21, % export XPCONFIGDIR=/home/gisburn/cwork/Xprint/Xprt_config/XpConfig; Xprt -fp /home/gisburn/cwork/Xprint/Xprt_config/XpConfig/C/print/models/SPSPARC2-TEST001/fonts,/home/gisburn/Xp_miscfonts -audit 4 :1 # see bug 68779 2001-03-14 16:08 for details of this issue) CC:'ing dcone@netscape.com because this may be a problem with printing in general
Assignee | ||
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
Assign to Roland
Assignee: katakai → Roland.Mainz
QA Contact: Roland.Mainz → katakai
Assignee | ||
Comment 3•23 years ago
|
||
Accepting. Can someone compare if this issue also appears on Windows and native PS module ? If yes --> "Component: Printing" because that isn't a Xprint-specific issue in that case...
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•23 years ago
|
||
Should be partially fixed by bug 83242 - other issues related to table stuff are not Xprint module specific... I am going to test this...
Depends on: 83242
Assignee | ||
Comment 5•23 years ago
|
||
Tested. Output on Win32 and Solaris/Xprint looks nearly the same. Tables are rendered OK except bugs in platform-independent table print code...
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•