[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
psset bug?
From: |
Robert M. Marmorstein |
Subject: |
psset bug? |
Date: |
Tue, 26 Jul 2005 12:07:31 -0400 (EDT) |
We are running version 4.13 of a2ps on a SuSE 9.3 system (both 32 and 64
bit architecture).
When we try to use psset -m on a postscript file, the output is bad
postscript. It seems that what is happening is the first character on the
line is being replaced by a control character.
I believe this may be caused by an error on lines 253 and 254 of
/usr/bin/psset. Instead of:
# Prepare the sed command we want to run.
# End of lines must be protected by `\' but the last one, and leading
# spaces with a `\' too...
pspagedevice=`echo "$pspagedevice" | \
sed -e "$pspagedevicelen!s/\$/\\\\\\/;s/^/\\\\\\/"`
I used:
pspagedevice=`echo "$pspagedevice" | \
sed -e "$pspagedevicelen!s/\$/\\\\\\/;s/^ /\\\\\\ /"`
(Two spaces are missing from the sed expression).
This seemed to fix the problem.
Let me know if I can help any further.
Robert Marmorstein
Ph. D. Program, Computer Science
College of William and Mary
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- psset bug?,
Robert M. Marmorstein <=