You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a printer has a Resolution option, foomatic will usually generate code for a user interface element in the PPD file, including a *DefaultResolution statement. When there is only a single choice for the Resolution, something like this will end up in the PPD file instead, however:
*FoomaticRIPOption Resolution: enum CmdLine A 100
*FoomaticRIPOptionSetting Resolution=300dpi: " -r300"
In this case, the *DefaultResolution statement is missing entirely. The problem with that is that the *DefaultResolution statement is meaningful even when there is no choice of resolutions. Without it, users of the PPD file will have no idea what the resolution of the printer should be.
A workaround for this is to add a <ppdentry> to the printer definition, but since foomatic does know the resolution, it should really be smart enough to add the *DefaultResolution entry automatically.
The text was updated successfully, but these errors were encountered:
When a printer has a
Resolution
option, foomatic will usually generate code for a user interface element in the PPD file, including a*DefaultResolution
statement. When there is only a single choice for the Resolution, something like this will end up in the PPD file instead, however:In this case, the
*DefaultResolution
statement is missing entirely. The problem with that is that the*DefaultResolution
statement is meaningful even when there is no choice of resolutions. Without it, users of the PPD file will have no idea what the resolution of the printer should be.A workaround for this is to add a
<ppdentry>
to the printer definition, but since foomatic does know the resolution, it should really be smart enough to add the*DefaultResolution
entry automatically.The text was updated successfully, but these errors were encountered: