GNOME Bugzilla – Bug 113932
Noun and adjective in the same messages in epiphany
Last modified: 2004-12-25 16:43:18 UTC
#: data/glade/prefs-dialog.glade.h:45 src/prefs-dialog.c:127 msgid "Russian" This message represents both the noun "Russian" (as in the language) and the adjective "Russian" (as in "Russian character encoding"). This is most unfortunate for many languages other than English, where the noun and adjective might not be the same word. See also bug 97482.
Reset target, will have to wait at least glib 2.4
Sorry for the spam. Reassigning bugs with a target to our next milestone.
The required i18n support macro Q_() is now in glib/gi18n.h.
Wow time to get rid of bonobo-i18n inclusions ;)
-> i18n
Chpe, any idea on how to do this ? Would it break string freeze ?
Yes, it would break the string freeze. Fixing this is marking those strings with context, i.e. instead of one string "Chinese" you'd then have two strings "the language|Chinese" and "encoding|Chinese", and use Q_() macro instead of _() which strips away the context. I'm not even sure that the intl toolchain supports extracting strings marked with Q_() yet. Definitely 1.4 material.
Any news? This seems to be easily fixable, but somebody has to take care of it. Christian? regs, Chris
Yep, PATCH_NEEDED :) However, depending on resolution of bug 130446, the language names would be removed from ephy altogether, so maybe this should be deferred until after feature freeze (but before string freeze) ?
Mass-moving Targe Milestone 1.4 -> 1.6 due to feature, UI and string freeze.
Those strings are used 1) in Edit->Prefs->Languages->Add dialogue, and 2) in Edit->Prefs->Fonts in the "For Language" combo box. What should we take as context, "language|Russian" or "the language|Russian" or ...; and "the fonts for|Russian" etc.?
If these strings are only used in the "language" context nowadays, and not in the "character encoding" context, then the problem mentioned in this bug report no longer applies. The problem was due to there formerly being several such contexts in which these strings were used, and no single translation fit both of them, at least in Swedish. But if there's only one context now, "language", then that problem is solved. I'll add cc: to Danilo, though, who should be able to tell if there's still a problem somehow.
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
Hmm seems I erred, we still have to distinguish between - "Fonts:\nFor Language: Chinese" and "Chinese" language in the language editor - "Autodetect: Chinese" meaning autodetect chinese character encodings Suggestions for the context string to use: "the language|Chinese" and ?
I've added context for the encoding autodetector strings, and the font languages strings. I've NOT added context for the language code strings, since 1) there's no overlap anymore, and 2) I didn't want to change that many strings which are going away anyway, as soon as we'll depend on iso-codes domain. If you find any more strings which need context, please file new bugs.