Bug 316461
Summary: | paps text conversion has problem with calculation of the printable area | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Norm Murray <nmurray> |
Component: | paps | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED NOTABUG | QA Contact: | QE Internationalization Bugs <qe-i18n-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | iav, jeffery_stone, tnunemaker, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-01 19:12:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Norm Murray
2007-10-03 06:26:27 UTC
Could you please provide a testcase and the expect result how it looks like? As far as a reproducer goes, Dell tells us that the Customer says any program that generates output of 132 characters per line will trigger the bug in the paps filter. The program they're using is apparently huge, and they can't send it to us as a reproducer. This event sent from IssueTracker by gcase issue 129164 This sort of thing can be quite hard to reproduce without the exact conditions. I think it would help if we had a small test case consisting of: 1. a PPD file this happens with, to have the same page boundaries as the customer 2. the output of 'lpoptions -p queuename' for that queue so we can see the exact lpi, cpi, page-left and page-right options in use 3. a few lines of text that the problem occurs with (word-wrapping bugs can be quite content-dependent) It should be possible to see the problem from this: PPD=theppd.ppd /usr/lib/cups/filter/texttopaps \ 1 me '' 1 'cpi=17 lpi=7 page-left=36 page-right=36' \ input.txt > output.ps with the right PPD, options, and input text file. This really sounds like bug #237202. Here's another instance of a RHEL-5 user seeing the same problem: http://cups.org/newsgroups.php?s14787+gcups.general+v15785+T0 This URL may not be stable. It should point to: ==> Subject: [cups.general] cannot exceed 132 columns with lpd Date: Tue, 08 Apr 2008 18:26:35 -0700 I'm using cups 1.2.4 on RHEL 5. I'm trying to print a 135 column report from Linux to a Brother HL-1440 on a Windows XP SP2 system, using LPD. Per the RFC, the Windows LPD is defaulting to 132 columns in raw mode, but according the lpr man page, the w control character I would use to override the default is disabled. I have tried both the standard laserjet.ppd, and the recommended foomatic:Brother-HL-1440-hl1250.ppd Interestingly, I could get laserjet.ppd to print up to 132 columns at cpi=17, but the foomatic one seemed capped at 80 regardless of cpi setting. Additionally, if I set cpi any higher than 17, or failed to specify a page-right option, laserjet.ppd would also start wrapping at 80 columns. I would like to be able to print 135 columns at 18 cpi. Any suggestions are greatly appreciated. <== Was there any resolution to this case? I have come across the same issue with RHEL 5.4 using cups 1.3.7-11.el5_4.4 |