Re: [Printing-architecture] PAPPL 1.2.0

Michael Sweet <[email protected]> Sun, 15 May 2022 11:42:22 -0400

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

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", ...);

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.

> On May 15, 2022, at 10:40 AM, Till Kamppeter <[email protected]> wrote:
> 
> On 15/05/2022 15:57, Michael Sweet wrote:
>> Till,
>> You need to create a .strings file of the form:
>>     "optionname" = "localized text";
>>     "optionname.choicename" = "localized text";
>> Add these resources in your system callback with papplSystemAddStringsData/File.
> 
> Can I set this dynamically while the Printer Application is running? This way I can create it when I set up a printer and read the PPD file I have assigned to it. I do not want to have to pre-build this for ~4000 PPD files and this way blow up the size of the Snap. And there is also the function for users to load their own PostScript PPD files.
> 
>   Till
> 

________________________
Michael Sweet

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