TEKSI Translation Guide
It is possible to contribute to TEKSI modules translations :
- Documentation
- QGIS .qgs projects (Forms)
- Plugin (Interface)
https://explore.transifex.com/teksi/
Here you will be able to join any "project" you want to help to translate (just after your account is created and your joining request is accepted) :
Old organisations are still available for QWAT and QGEP
To ease translation and improve quality, glossaries have been set to provide translation terms from official repositories (at least for switzerland)
https://docs.google.com/spreadsheets/d/1qeoCVwdOLyhdLHqVKsOzZ5zyle3iiQd1pVTFKU_rbGU/edit?usp=sharing
In Transifex, it can be seen like that :
Use official terms when possible as first rule. And take care about specific details of attention listed here under.
When translating it's important to know, where the word is coming from. In "more info" you find for every text the context. "value_en" has two contexts:
- it can be a value_relation value: then it has to be translated to value_de or value_fr:
green: table or view, field. blue: valuerelation value
effect: in the translated project, there will stand value_de / value_fr instead of value_en - you have your language.
- it can by a field alias (name of the attribute of a table or of a view). All other fieldaliases should be translated, but not field-aliases of value lists (Wertetabellen). Becaue if you do this, there will be two fields with value_de after the translation. The value relation goes to the field with name value_de. QGIS will take the first field with value_de. This is the field with the english values, but has alias value_de. Your valuelists in the attributes form will be in english!
these blue value_en should keep his name.
Do not translate field aliases of value list!.
Value lists are tables with name "classname"_"fieldname". In the example: class reach_point, field elevation_accuracy
Database type items/attributes (like ws_type) can only be translated manually (translate Description and not Value!)
See https://github.com/teksi/wastewater/issues/60 for more information about that.
Translations assets (documentation, project, plugin) are provided and updated by the CI using Transifex API and GitHub actions.
In a general way :
- Documentation translation is updated every day
- Project translation is done every release or triggered manually
- Plugin translation is done every release
- Go to the corresponding workflow https://github.com/teksi/wastewater/actions/workflows/project-translation.yml
- Click run workflow (you have to be member of TEKSI GitHub organisation to do it)
- Refresh the page
- Once the workflow is done (about 2m30s) click on it and click on summary
- Here you will find the translated project file available to download
