Does the value saved in /var/cache/cups/[printer_name].strings meet the expectations?

[xiaowen581]

The strings returned from the printer's printer-strings-uri is
"media-type.com.epson-thickpaper1" = "Thick paper1";
However, after installing the printer with everywhere, the strings saved in /var/cache/cups/[printer_name].strings is
"media-type.com.epson-thickpaper-1" = "Com.epsonThickpaper1";

Therefore, when using cupsLocalizeDestValue(xxx, xxx, xxx, "media-type", "com.epson-thickpaper-1"), it returns "Com.epsonThickpaper1". However, I think that "Thick paper1" should be the correct answer, right?

System Information:

• OS and its version: Ubuntu 22.04(WSL)
• CUPS version: 2.4.10

the ppd created by everywhere :
epson.ppd.txt
the strings cache :
epson.strings.txt

[xiaowen581]

I tried to change the line in _ppdCreateFromIPP2
from
cupsFilePrintf(fp, "*MediaType %s: \"<</MediaType(%s)>>setpagedevice\"\n", ppdname, ppdname);
to
cupsFilePrintf(fp, "*MediaType %s/%s: \"<</MediaType(%s)>>setpagedevice\"\n", ppdname, msgstr, ppdname);
then I get my expected outcome from cupsLocalizeDestValue.

For 2.4.10, It seems that the choice->text in the _ppdCacheCreateWithPPD doesn't obtain the message in C.MediaType cause the issue?

[xiaowen581]

I think this issue could be a duplicate of #546

[michaelrsweet]

Actually, #86 which is resolved for CUPS 2.5 (not a whole lot we can do for 2.4.x unfortunately...)

[michaelrsweet]

There are known localization issues in CUPS 2.4 that are resolved in CUPS 2.5. Unfortunately, the scope of the changes is more than we'd want to include in a patch update so it will have to wait for 2.5.0 later this year.