Re: [Printing-architecture] PAPPL 1.2.0

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)?

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

> I've been working on a new StringsUtil library and utility project that can be used to manipulate .strings files more easily - it's what I've used to localize PAPPL and will be using for libcups3 as well:
> 
>      https://github.com/michaelrsweet/stringsutil
> 
> I'm in the process of moving the .strings file save functionality out of the utility and into the library, at which point it should do everything you need it to do to dynamically maintain a set of .strings files.
> 

Will have a look into it.

    Till