all devices regression report - 2018-02-28-07:34:49 - d57bd7ce641d8134d559f5e8190e2578137e1d39

[email protected] Wed, 28 Feb 2018 07:34:49 -0800 (PST)

Newsgroups	gmane.comp.printing.ghostscript.regression
Message-ID	<20180228153450.017FD2041D93@i7>

Differences in all devices errors using gs/examples files

Previous Revision: d0d4e282f98487ca2979edbaf6834d9341bcee53
 Current Revision: d57bd7ce641d8134d559f5e8190e2578137e1d39

commit d57bd7ce641d8134d559f5e8190e2578137e1d39
Author:     Ken Sharp <[email protected]>
AuthorDate: Wed Feb 28 14:04:32 2018 +0000
CommitDate: Wed Feb 28 14:04:32 2018 +0000

    txtwrite - better dynamic resizing
    
    A better fix for bug #699078, this implemnets the thought I had while
    writing up the description of the problem. In this case we check whether
    the current 'effective size' of the monospaced font would lead to
    the end of the current run of text lying to the right of the 'next' run
    of text on this line. If it would, then use the newly calculated
    effective size, no matter how small it is, to avoid collisions.

devices/vector/gdevtxtw.c

new errors:
=== ghostpdl/examples/grayalph.ps === txtwrite ===
timeout



=== ghostpdl/examples/waterfal.ps === txtwrite ===
timeout




errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/grayalph.ps === txtwrite ===
=== ghostpdl/examples/waterfal.ps === txtwrite ===