Difference between revisions of "Official talk:Translation Howto"
(→Add Transifex section -- ~~~~: new section)
|Line 23:||Line 23:|
== Transifex ==
== Transifex ==
Revision as of 21:24, 2 November 2016
- 1 Proposal to update Translation page -- Kunda (talk) 15:21, 2 April 2016 (CEST)
- 2 Part Two: Translating other parts of Scribus…
- 3 Add Transifex section -- Kunda (talk) 22:07, 2 November 2016 (CET)
- 4 Transifex
Part Two: Translating other parts of Scribus…
Translating the Render Frame Editor…
Translating Qt framework
Scribus is based on the Qt Framework and therefore some basic dialog box receive translations from the Qt directly. Ideally Qt framework would have complete translations on that specific relevant language.
But sometimes if we encounter using Scribus in another language besides english that:
- some basic dialog boxes appear English
- the specific language you are using in Scribus has been translated totally or that you've looked in the .ts file and can't find those non-translated strings
This indicates that the issue is an upstream Qt translation problem. To check this you can check the Qt translation state for your specific language here. The Qt framework is translated code.qt.io/cgit/qt/qttranslations, and this is the official guide for translators.
FYI, for those of you who are wondering why we don't just translate these Qt translated dependant strings directly in Scribus, see jghali's explanation.
1) Filling the rest of the info for how to use Transifex 2) State the intention of Transifex and the option to use (some don't) 3) Screenshots of the process 4) Guidelines for Language Coordinators 5) Guidelines for Language Translators