Closed
Bug 726244
Opened 14 years ago
Closed 9 years ago
OS/2 version only - Native Postscript subsystem is broken in 2.5/2.6/2.7
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: verydiscreet, Unassigned)
References
Details
Attachments
(1 file)
215.73 KB,
application/pdf
|
Details |
User Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.1.19) Gecko/20110421 SeaMonkey/2.0.14
Build ID: 20110421220512
Steps to reproduce:
Print a webpage to file in Seamonkey 2.7 for OS/2 using a Postscript printer definition.
Actual results:
(1) Major issue: second and all subsequent pages printed within a single session in all versions later than 2.0.14 are damaged and cannot be viewed and read in Acrobat or Lucide. Illustrative file is attached.
(2) Minor issue: the .ps or .pdf files that version 2.7 generates (including the readable first file per session) are bloated -- typically 35 percent larger for .pdf, typically 400 to 800 percent larger for .ps -- compared to the same-format files that are generated by Seamonkey (for OS/2) versions 2.0.14 and earlier.
This bug reports form allows one to attach only one file; I can supply additional illustrations of(identical page rendered by version 2.0.14; identical page when it is the first page rendered within a session of version 2.7) behavior in Seamonkey (for OS/2) version 2.0.14 and Seamonkey (for OS/2) version 2.7. The behavior is repeatable and consistent; independent third parties should be able to replicate it.
Expected results:
(1) As to major issue, the second page (and all subsequent pages) printed to file within a session of Seamonkey should be rendered as viewable files, just as the first page printed to file is rendered as a viewable file.
(2) A generated .pdf or .ps file for a specific page generated by Seamonkey (for OS/2) version 2.7 should be the same size as a generated .pdf file (or .ps file) of the identical page generated from Seamonkey (for OS/2) version 2.0.14.
There is a partial workaround. Shut down Seamonkey (for OS/2) completely, and reopen it. After re-opening, one can print one (only one, no more) uncorrupted webpage to file. To print a second webpage to file, one must shut down Seamonkey completely a second time and reopen it.
Updated•13 years ago
|
Hardware: Other → x86
![]() |
||
Comment 1•13 years ago
|
||
Is this broken in Firefox 8/9/10 as well?
(In reply to Philip Chee from comment #1)
> Is this broken in Firefox 8/9/10 as well?
Yes it is.
On my spouse's MacBookPro, running OS X Snow Leopard, we run Seamonkey 2.7.2, and formerly ran 2.7; and, on that platform, corrupted print-to-file is NOT an issue. This is specifically an issue in the OS/2-eComStation port. In my bug report, I imprecisely stated that only one uncorrupted _page_ could be printed per session; more precisely, only one uncorrupted print _job_ can be run per session. However, on further examination of the output from the first print job of multi-frame pages in 2.7, I notice that the second _frame_ is corrupted.
Component: OS Integration → Printing: Output
Product: SeaMonkey → Core
QA Contact: os-integration → printing
Version: SeaMonkey 2.0 Branch → unspecified
Comment 4•9 years ago
|
||
OS/2 is no longer a supported platform.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•