tomkralidis
commented
10 years ago @rduivenvoorde thanks.
1./ The .pro file is generated automagically as a build step in build_qt_files (https://github.com/geopython/MetaSearch/blob/master/pavement.py#L104). Then in compile_messages this runs lrelease MetaSearch.pro. What should the output look like so all locales have a release?
2./ The loading of the translated docs can be setup on to work off something like a select box on the webpages to change languages. Is this what you mean? Is this how QGIS does it?
plz check this
I've updated .tx/config so a 'tx pull -a' retrieves all languages from transifex (note: paver clean also removes them all. Maybe leave them in the dirs, either put them in .gitignore or just check them in periodically?)
after paver extract_messages and paver compile_messages the po stuff is compiled but the tx files are not... seems something to do with missing info in .pro file?? When I make a 'release' file with linguist (just load the ts file, and do File/Release, a ui.qm file will be generated next to ts file). The dialog will be translated (small fix in plugin .py to make 'qgis --lang it' work) Q1: how is the pro file generated (and can it be fixed so all locales will have a release)? Q2: how will the loading of the translated docs work?