Is there interest into improving the support for translation in ParaView ?
I’m currently adding a support for translation in a ParaView based app and there is a lot of non
tr() visible QString in ParaView.
Some doc for these that do not know this :
If we consider that ParaView is “translatable” with some effort, we may need to take a few steps :
- Do a general pass to add a many tr() as possible in ParaView
- During the review process, check that visible string are tr()ed
- Qt provide a tool to generate a translation file from .cxx and .ui files (lupdate). We may want to provide a tool to do the same from a servermanager xml file.
- Something more advanced not yet designed ?
As a side note, I have a question for those that have already experience with this mechanism.
the translation file .ts provide translation by context. eg: in pqMyClass, “foo” is translated “bar” by calling
pqMyClass::tr("foo"). Is there a way to specify a generic context to fallback on ? that would avoid duplicating translation. Unless we try to use QObject::tr() instead of pqMyClass::tr() in general.