Not yet had the time to check, sorry (you know, it's all about this crazy little thing called work). But I'll do it ASAP.
@ Till: just to be sure to have understood correctly. When you write in the diff:
- pdftops: Start determining the printing resolution with cupsRasterInterpretPPD(), this is the most reliable as often
the choice names of the "Resolution" option are marketing names
with higher numerical values than the actual resolution. Also
ignore error exit values of cupsRasterInterpretPPD() as the
function can error out after having found the resolution.
- pdftops: If printing resolution is determined by cupsRasterInterpretPPD() do not stick on 100 dpi if the
resolution cannot be determined (LP: #984082).
Does it means that it will understand that BRResolution means Resolution (see posts #11 and #13) and interpret the setting correctly, or that it won't understand this setting at all and always set a fixed resolution of something like 600 dpi ?
Not yet had the time to check, sorry (you know, it's all about this crazy little thing called work). But I'll do it ASAP.
@ Till: just to be sure to have understood correctly. When you write in the diff:
- pdftops: Start determining the printing resolution with
cupsRasterInte rpretPPD( ), this is the most reliable as often pretPPD( ) as the
cupsRasterInte rpretPPD( ) do not stick on 100 dpi if the
the choice names of the "Resolution" option are marketing names
with higher numerical values than the actual resolution. Also
ignore error exit values of cupsRasterInter
function can error out after having found the resolution.
- pdftops: If printing resolution is determined by
resolution cannot be determined (LP: #984082).
Does it means that it will understand that BRResolution means Resolution (see posts #11 and #13) and interpret the setting correctly, or that it won't understand this setting at all and always set a fixed resolution of something like 600 dpi ?
Thanks for the work.
Best regards
Olivier Subilia