Bug 690185 - spacing is larger in the output file compared with the pcl input file
Summary: spacing is larger in the output file compared with the pcl input file
Status: NOTIFIED FIXED
Alias: None
Product: GhostPCL
Classification: Unclassified
Component: PCL fonts (show other bugs)
Version: 1.52
Hardware: PC Windows XP
: P4 normal
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-28 06:20 UTC by Horiana Costea
Modified: 2011-09-18 21:47 UTC (History)
0 users

See Also:
Customer: 460
Word Size: ---


Attachments
sample.pcl (4.35 KB, application/octet-stream)
2008-11-28 06:25 UTC, Horiana Costea
Details
sample.pcl.tiff (25.50 KB, image/tiff)
2008-11-28 06:25 UTC, Horiana Costea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Horiana Costea 2008-11-28 06:20:55 UTC
Using GhostPCL 1.53 we observed that for the pcl file attached to 
this defect, the spacing in the output file (tiff backend was used) is larger.
Comment 1 Horiana Costea 2008-11-28 06:25:07 UTC
Created attachment 4627 [details]
sample.pcl
Comment 2 Horiana Costea 2008-11-28 06:25:38 UTC
Created attachment 4628 [details]
sample.pcl.tiff
Comment 3 Henry Stiles 2008-12-03 10:11:01 UTC
I am afraid this problem is not likely to be solved without considerable effort.
 The vertical spacing is reset after receiving the request for a paper size
change to "legal".  The spacing should be reset if the previous paper size is
not legal and should not otherwise.  In our interpreter other difficult to
emulate problems were alleviated by resetting vertical motion irrespective of
paper state change.  The usual protocol in the pcl language is to set the paper
size first, then change the spacing, in this case our interpreter will match the
HP, a case can be made that the pcl (sample.pcl) is ill-formed or we can
research what other problems will be created by changing the behavior to fix
this bug.  A project of probably 2 weeks duration.  Please discuss this with
Miles or Marcos, I was informed there are business issues to be resolved before
starting projects with customer 460.
Comment 4 Horiana Costea 2009-08-07 00:31:48 UTC
I reopened this defect since I need a resolution for it.

Thank you
Comment 5 Horiana Costea 2009-08-12 08:20:09 UTC
Hello. I would need the signature problem to be fixed by 8/21, since the 
product being integrated in is going to exit from test.

Is this achievable?
Thanks
Comment 6 Henry Stiles 2009-08-12 09:25:19 UTC
No I don't think that date is possible, even if we started today.  I haven't
been given the go ahead to start working on this issue at customer priority so I
am reassigning to support until that is resolved.
Comment 7 Henry Stiles 2009-11-03 09:48:59 UTC
Fixed in rev 10274.
Comment 8 Horiana Costea 2009-11-04 06:25:45 UTC
Could you please tell me how can I get code modified in rev 10274? 

Thank you.
Comment 9 Ken Sharp 2009-11-04 06:52:53 UTC
Patch is here:

http://ghostscript.com/pipermail/gs-cvs/2009-November/010000.html
Comment 10 Marcos H. Woehrmann 2011-09-18 21:47:35 UTC
Changing customer bugs that have been resolved more than a year ago to closed.