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
Inconsistent translations #2642
Comments
CUPS.org User: ronaly Will this request be granted? However, the DDKs string translator is still valuable whenever there are strings not defined in the user's message catalog. |
CUPS.org User: mike Reassigning as CUPS 1.4 bug. |
CUPS.org User: mike Fixed in Subversion repository. |
"str2642.patch": Index: ppdc/ppdc-catalog.cxx--- ppdc/ppdc-catalog.cxx (revision 8049) // void
// Range check input...
// Verify that we don't already have the message ID...
// Add the message...
messages->add(new ppdcMessage(id, text)); @@ -166,7 +174,6 @@
- temp = new ppdcMessage(id, str);
while (cupsFileGets(fp, line, sizeof(line)))
- }
strlcpy(str, ptr, sizeof(str));
- temp = new ppdcMessage(id, str);
|
Version: 1.4-current
CUPS.org User: ronaly
I am using cups 1.3.3 and ddk 1.2.3. I also have my own message catalog (PO). Most of the strings are translated on different locales based on my message catalogs. But there are few strings that have their own translations and never get from my message catalog.
For example, "Tray 1", "Tray 2", "Statement".
First problem:
(ex. in French)
Expected Translations: From generated PPD:
Tray 1 - Tiroir 1 Tray 1 - Bac 1
Tray 2 - Tiroir 2 Tray 2 - Bac 2
Statement - Statement US Statement - Relevé
I understand now that the base translation in the ddk has higher
precedence than the user - supplied translations.
Second problem:
The string "On" has base translations from all locales except Italian.
It does not also get translation from my message catalog now that
translation from ddk is not provided.
Is this a bug in cups ddk?
Could it be possible to set user-supplied translation as higher precedence? I think for more flexibility it is better.
The text was updated successfully, but these errors were encountered: