Official talk:Translation Howto: Difference between revisions
Jump to navigation
Jump to search
(announcement) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
=== Translating the Render Frame Editor… === | === Translating the Render Frame Editor… === | ||
=== Translating Qt framework === | === Translating Qt framework === | ||
Scribus is based on the [http://www.qt.io/ Qt Framework] and therefore some basic dialog box | Scribus is based on the [http://www.qt.io/ 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. | ||
[[File:CloseWindow.png|framed|right|Example of a Qt translation dependence. This is Scribus using the Hungarian localization with 100% completed translation file. As you can see the strings for the dialog box buttons are still in English.]] | |||
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 [http://l10n-files.qt.io/l10n-files/ here]. | |||
The Qt framework is translated [http://code.qt.io/cgit/qt/qttranslations.git/ code.qt.io/cgit/qt/qttranslations], and this is the [https://wiki.qt.io/Qt_Localization 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 [https://bugs.scribus.net/view.php?id=13860#c39466 explanation]. | |||
== Add Transifex section -- [[User:Kunda|Kunda]] ([[User talk:Kunda|talk]]) 22:07, 2 November 2016 (CET) == | |||
== Transifex == | |||
# Filling the rest of the info for how to use Transifex | |||
# State the intention of Transifex and the option to use (some don't) | |||
# Screenshots of the process | |||
# Guidelines for Language Coordinators | |||
# Guidelines for Language Translators | |||
Latest revision as of 21:24, 2 November 2016
Proposal to update Translation page -- Kunda (talk) 15:21, 2 April 2016 (CEST)
bubu, lets write the proposal here Kunda (talk) 15:21, 2 April 2016 (CEST)
Part Two: Translating other parts of Scribus…
Translating Templates…
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.
Example of a Qt translation dependence. This is Scribus using the Hungarian localization with 100% completed translation file. As you can see the strings for the dialog box buttons are still in English.
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.
Add Transifex section -- Kunda (talk) 22:07, 2 November 2016 (CET)
Transifex
- Filling the rest of the info for how to use Transifex
- State the intention of Transifex and the option to use (some don't)
- Screenshots of the process
- Guidelines for Language Coordinators
- Guidelines for Language Translators