Translations: How to efficiently handle language variants?
-
Apologies for reviving an thread, but I am hoping somebody will reply. I am trying to figure out whether it is possible to implement option 2 described here - using "sparsely populated" region-specific translation files (fr_CA for instance), and falling back to the "main" translation file (fr) for any strings not found in the region-specific file.
I am installing 2 translators just as this post suggests, with full translations in the fr file, and only a few strings in the fr_CA file. The fallback does not work, however, I only ever get strings from the translation file that I load last. That is, if I load the fr_CA file last, I get the fr_CA-specific strings displayed translated, but the rest fall back directly to the source file strings (English in my case). And if I load the fr file last, I get all the strings from the fr file, but none of the fr_CA strings.
Has anybody made this work?
-
Please check this thread
"
http://qt-project.org/forums/viewthread/4207/":http://qt-project.org/forums/viewthread/4207/ -
I'm sorry, but how does dynamic language switching have anything to do with this problem? I am not switching languages, I am using French all the time.
What I want is to get the strings that are located in the fr_CA file to be displayed, and for the strings that are NOT in the fr_CA file, I want the strings from the fr file to be displayed (not fall back to the source strings).
So I need language fallback to work. I would have hoped that this would just work by default, as in Java, but it obviously does not. So I am trying to work around that issue, by loading 2 QTranslators (as suggested by the original poster), but that also does not work.
-
The "QTranslator docs":http://qt-project.org/doc/qt-5.0/qtcore/qtranslator.html report that using multiple translations is possible. They're checked in reverse order so you can load a first translation which would be your main translation, and a second translation that would be your language variant.
Basically, you load your fr_FR main translation, then load the fr_CA translation. The QTranslator will first look for a translation in fr_CA; if none is found then it'll look back into the previous (main) translation fr_FR.I hope that helps ;)
-
Apologies if this is a duplicate response, not sure if my first attempt disappeared in thin air.
I know that the QTranslator docs state that this is possible, but has anybody made it work? It certainly does not work for me. I only get translations from the last loaded file.
-
That's right, you would normally get translations from the last loaded translation file. But, in case the last translation file is missing a translation, all previously loaded translations files are checked in reverse-loading order until any translation is found.
I haven't used it, but seems to be pretty easy... -
It SEEMS pretty easy, except it does not work the way you describe it.
The translation file loading I see corresponds to what my understanding has always been: QTranslator looks for translation files in a fallback order (if I ask for an fr_CA translation, and QTranslator does not find an _fr_CA file, then it will look for an _fr version, etc.). BUT, if QTranslator finds an _fr_CA file, then it will ONLY look for translations in that file. If a certain string does not have a translation in the fr_CA file, then QTranslator just loads the source string. So we have translation file fallback on a per-file basis, but not on a per-string basis.
I would love to see a Hello World app with 2 strings that demonstrates that this actually works as advertised...
-
I guess you're doing something wrong because the docs clearly state:
@Using Multiple Translations
Multiple translation files can be installed in an application. Translations are searched for in the reverse order in which they were installed, so the most recently installed translation file is searched for translations first and the earliest translation file is searched last. The search stops as soon as a translation containing a matching string is found.@
The last phrase means that the app will keep searching a translation in the installed translation files until a matching translation is found.Probably there's some particular approach needed to install multiple translations. Probably, the way you're using is overwriting the previous translation instead of adding it in the translation files list.
-
OK, I did find a way to make this work. It turns out that with context-based translation strings you can just install the 2 translators in the order stated, and the translations will be loaded from the fallback file if not found in the more specific file. So the documentation is indeed correct for that case.
I was using ID-based translation strings, and for some reason it does not work there (at least I have not been able to make it work - yet). Will update if I do.
