🚀 go-pugleaf

With the PostScript driver on Windows 95 and 98SE (other 9x versions not
tested), some text strings simply dissapear or are clipped if the resolution
is set to 1200dpi or higner. Happened with ADOBEPS.DRV 4.3.1, and still
happens with the driver installed by the Universal Installer 1.0.5 (I think
it's 4.5.2). All ok on Windows 2000.

The application makes exactly the same GDI calls for each string it prints,
variables being only point size and (x,y) coordinates (note: it does not
generate PostScript code by itself). I checked coordinates, and these are
ok. The functions used (tried TextOut() and TabbedTextOut()) do not involve
any clipping; I tested DrawText() too, with and without clipping, but the
result is identical. The problem is not related to a particular font, rather
to the total string's width and number of characters (wider strings and
strings with more characters - like 90 - are more likely to be affected).
The problem does not appear randomly, that is if printing again with the
same printer settings, the same strings dissapear.

By examinig the PostScript produced, I noticed that for some strings
(apparently the longer ones), the driver generates a call to "rectclip"
followed by an "ashow" (the app does nothing special that would require
"ashow"). For others (even if the GDI function used by the program is the
same), it uses "show" and no "rectclip". My impression is that somehow the
driver thinks it needs clipping and computes the clipping rectangle
incorectly, resulting an empty rectangle (or too small); then it outputs
only the characters that would fit into that rectangle (yes, in some cases
the last visible character if partially clipped).

Does anybody know what's happening? Is this an OS failure? A fix? A
workaround? (other than setting the resolution to 600dpi or less)