GDI tracing refinements: The LP TRACE information has been expanded somewhat to help interpret/debug the behavior of the driver when requesting paper sizes. For example, when listing the available paper sizes, it now shows the actual dimensions of the available paper sizes and their full names (according to the driver) rather than just the standard code names and numbers. It also shows the initial and updated paper size (after attempting to set it), making it easier to identify whether the paper size setting is functioning as expected. For example, you may see the following messages (among others) in the trace:
Initial page size: 1800 x 3000 pixels
Requesting papersize #256
Updated page size: 2550 x 3300 pixels
Final page size: 2550 x 3300 pixels (300 x 300 dpi)
The above sequence indicates that the initial default paper size was 1800 x 3000 pixels. (See the "Final page size" message to get the pixels per inch or "dpi".) You requested paper size #256 (PAPERSIZE=256 or //PAPERSIZE,256), and this had the immediate and final effect of setting the paper size to 2550 x 3330 pixels.
It will also show details about the attempts to set custom paper sizes, including the two-step process of pre-setting the paper size to a supported value and then overriding the length and width.
