Hi Markus, On Thu, Sep 27, 2018 at 10:33:06PM +0200, Markus Koschany wrote: > Hi, > > I believe I have found the solution to this problem. Apparently they > changed the underlying device for ps2ascii to txtwrite last year. > > http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=2fa6beaa40144c592661a611bf35ff6f06d3354f > > If I apply this commit in Jessie, ps2ascii appears to work again. I > tested it with two example ps files from > > https://www.ghostscript.com/doc/current/Psfiles.htm#Art > > alphabet.ps and waterfal.ps > > The text is correctly displayed now in Jessie but the Stretch version > shows Chinese characters instead. Hence I would appreciate it if you > could double-check and verify the output on your terminals.
The commit might be part indeed of the solution, that is to switch to the txtwrite device. In the bisect I did, I already used as well a variant with using the txtwrite device. This is what lead to previously posted git bisect log (with commits between a broken one in the 9.20 series, up to the a less broken one[*], and in each iteration always applying as strategy the mentioned commit for fixing the CVE and which caused the regression, and calling gs directly with the needed parameter using the txtwrite device). I know already that e.g. using the commit http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=cc746214644deacd5233a1453ce660573af09443 (*and* using the txtwrite device) seems to improve the situation. But there are still dispalying discrepancies and regressions with test files. So this is not enough for the stretch built at least :-/. In the jessie patched version, you did exact the same documents with old version and with patched one for e.g. alpahet.ps and waterfall.ps? Regards, Salvatore [*] I'm saying it explicitly this way, because the rendered output, will have in those situations as well already regressions, but not anymore just "completely broken output".
