From:
[email protected]
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Hi,
The first attachment to this email, psset.sed, is a sed script is created on-the-fly by psset (in the a2ps package). As you see, lines 5 and 17 of
the script begin with the characters "\countdictstack" (without quotes). However, versions 4.1-1 and higher of sed treat the "\co" as an escape
sequence representing Ctrl+O (ASCII 15), which breaks the output of psset,
and in turn causes Bug# 258042 that is currently filed against gs.
Versions 4.0.9-5 and earlier of sed do not do anything special with the
"\co".
Now, the Info sed manual describes the "\cX" escape sequence, but I am not intimately familiar with sed so I don't know under what circumstances the escape is substituted in. If the escape should NOT be substituted in,
this is a bug in sed that should be fixed. On the other hand, if current versions of sed are behaving correctly, I will reassign it to a2ps.
The second attachment to this email, a2ps.patch, is a trivial patch to fix psset to work with the current behavior of sed. (The patch is harmless if
the sed behavior is reverted.) I think it should be applied in any case,
since sed is in Base and therefore already frozen, while a2ps is not yet.
Please look after this quickly, because this problem makes apsfilter essentially unusable as a print filter in sarge.
thanks and regards,
--
Kevin B. McCarty <
[email protected]> Physics Department
WWW:
http://www.princeton.edu/~kmccarty/ Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544
[SoupGate killed MIME-encoded file psset.sed (560 bytes)]
[SoupGate killed MIME-encoded file a2ps.patch (617 bytes)]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)