Bug 42656 - a2ps doesn't print plain text files
Summary: a2ps doesn't print plain text files
Status: CLOSED DUPLICATE of bug 40532
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: a2ps
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-29 07:09 UTC by Tomasz Kepczynski
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2002-01-09 15:17:16 UTC

Attachments (Terms of Use)
Analysis and proposed patch (1.30 KB, patch)
2001-05-29 09:47 UTC, Jean-Luc Richier
no flags Details | Diff
Corrected patch for this bug and bug #40532 (1.52 KB, patch)
2001-05-29 11:01 UTC, Jean-Luc Richier
no flags Details | Diff

Description Tomasz Kepczynski 2001-05-29 07:09:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
a2ps used to convert text files to postscript before sending them to
printer. At the moment it seems that the conversion fails as the postscript
printer (HPLJ 4050N) doesn't print. In addition if printing to postscript
file and viewing it with gv - ghostscript fails with errors or gv displays
empty page only with frame around it.
I don't know what magic a2ps uses to convert text to postscript so it
may be possible that actual fault is in some other place.
This used to work in RH 7.0 & 6.2.

How reproducible:

Steps to Reproduce:
1. print any text file with a2ps

Additional info:

I use Polish ("pl_PL") locale and latin2 encoding but the latter doesn't
seem to matter. The fault disappers when locale is set to "en_GB" or "C".
If locale is set to "en" a2ps dumps core.

Comment 1 Jean-Luc Richier 2001-05-29 09:47:18 UTC
Created attachment 19855 [details]
Analysis and proposed patch

Comment 2 Jean-Luc Richier 2001-05-29 11:01:06 UTC
Created attachment 19863 [details]
Corrected patch for this bug and bug #40532

Comment 3 Tim Waugh 2002-01-10 09:37:11 UTC

*** This bug has been marked as a duplicate of 40532 ***

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