Re: [Printing-architecture] PAPPL 1.2.0

Michael Sweet <[email protected]> Sun, 15 May 2022 15:34:08 -0400

Newsgroups	dev.linux.lists.printing-architecture
Message-ID	<[email protected]>

Till,

> On May 15, 2022, at 3:01 PM, Till Kamppeter <[email protected]> wrote:
> 
> On 15/05/2022 17:42, Michael Sweet wrote:
>> Till,
>> You will need to maintain a single strings file for each language that is localized, among all of the added printers.  Then make sure to remove any existing resource file before re-adding it, otherwise the resource will not be added:
>>     // Update LOCALE.strings file
>>     papplSystemRemoveResource(system, "/LOCALE.strings");
>>     papplSystemAddStringsData/File(system, "/LOCALE.strings", "LOCALE", ...);
> 
> So it needs to be a single file for all printers set up? Or can it be one per printer and per language (4 printers, each printer's PPD has 3 languages -> 12 files)?

A single file for all printers.

Normally a printer application has a closed set of drivers, options, and choices, but in your case the PPD files work against that assumption.  I don't know that I want to change PAPPL just to accommodate ps-printer-app when there is an easy enough workaround.

> And the localization for PAPPL's UI has to be in the same file as the localization for the vendor options?

Yes, though most of that (if not all) is options/attributes and values anyways.

Anything provided by PAPPL is localized for you, you just provide strings for anything specific/unique to your application.  Right now PAPPL has built-in localizations for English, French, German, Italian, Japanese, and Spanish.  I want to add more, obviously, but that will depend on contributions...

________________________
Michael Sweet

signature.asc (application/pgp-signature, 833 B)