[Desktop_printing] Multi-Language PPD files and PPD file specs
george.liu at ussj.ricoh.com
Tue Jan 17 10:37:59 PST 2006
> PPDs should be multi-language, so that every user sees the printer
options in his desktop language. Best would be to not re-invent the
wheel for it and use the implementation of CUPS 1.2:
The multi-language PPD file is indeed a really good idea. I was thinking
about that too. Thanks Michael and Easysoft to make it a reality.
> We also need to convert the sets of single-language manufacturer PPDs
into multi-language ones, preferrably with the help of a script.
For manufacture supplied PPD files, I prefer the change be made by the
manufacture. We'll have a better tracking of the version and the
translation will be consistent with Windows/Mac driver.
I don't have any objections for the changes you planned to make for xml
based foomatic drivers,
From: desktop_printing-bounces at lists.osdl.org
[mailto:desktop_printing-bounces at lists.osdl.org] On Behalf Of Till
Sent: Tuesday, January 17, 2006 9:19 AM
To: desktop_printing at osdl.org
Subject: [Desktop_printing] Multi-Language PPD files and PPD file specs
another point for the agenda would be to talk about the PPD file specs
and possibilities to improve them to fit the current situation better.
There are the following points:
1. Multi-Language PPD files
As in a network users can have different desktop languages, but use
print queues on print servers together, PPDs should be multi-language,
so that every user sees the printer options in his desktop language.
Best would be to not re-invent the wheel for it and use the
implementation of CUPS 1.2:
2. New option types
I think we discussed this already earlier here or on the
desktop_architects list. PPDs should also have string/password options
for secure usercode/password-protected (locked) printing, and numerical
options for color and other adjustments.
Desktop_printing mailing list
Desktop_printing at lists.osdl.org
More information about the Printing-summit