Bug 143642 - problems with dot matrix printer
problems with dot matrix printer
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-12-23 02:41 EST by Shinu R
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-23 04:50:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Shinu R 2004-12-23 02:41:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:

1.i am using fedora verasion 1 core .i have dot matrix printer tvse 
msp 155.i need to take pdf output on a paper with width of 14 inch 
and heigh of 12 inch.But there is problem,that it take driver options 
only. iadd printtool,driver options as eps9high.but i cannot specify 
custom paper size during printing.Therefore i loss data or not get 
correct format as required.How i solve this problem.Can any one help 
me please give step by step procedures . iwait for reply

2.i need to take print out on a paper of132 columns.But my report 
have 190 columns.How i print this in linux?// .I am using Fedora 1 
core and tvse dot matrix155 printer with cups.any body know how to 
done compressed printing without loss of my data.Help me please by 
giving all informations 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
 with this

Additional info:
Comment 1 Tim Waugh 2004-12-23 04:50:59 EST
Custom paper sizes are not possible with redhat-config-printer (but can be done
with PPDs).  Please note that this is not a support forum but a means of
reporting bugs.  Please try one of the mailing lists or IRC channels for asking
questions like this:


Note You need to log in before you can comment on or make changes to this bug.