-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localized strings are not present for many options #1020
Comments
Aren't those options+values from PPD file? CUPS localizes only PPD options which generates for IPP Everywhere, and IPP attributes and its values. Other PPD options/values localization have to present in the PPD file to get the localized. But that's about CUPS - whether the application uses the CUPS locale API to get them localized, that's a different thing. |
@zdohnal No, those are CUPS IPP attributes. @metabiswadeep WRT those IPP attributes, "page-border" is the only one that is not deprecated in CUPS 2.4.x, and it will be deprecated in CUPS 2.5 (haven't gotten around to doing so) since CUPS 3.0 and later won't support it. I'm not sure how much effort we want to put into this but I can see whether adding the strings to be base localization file is enough to propagate things to the other languages, but that is what will be required... |
Describe the bug
While CUPS provides localized strings for most options, there are still many such ipp options and choices for which CUPS still does not provide localized strings. For example, as in the screenshots below, CUPS does not provide translations for ipp options such as position, page-border, page-set, etc and for their corresponding choices.
Expected behavior
CUPS should provide localized strings for these options.
Screenshots
System Information:
The text was updated successfully, but these errors were encountered: