Official talk:Translation Howto: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
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 receives translation from the Qt. Ideally Qt framework has complete translation on the relevant language. But if we see that some basic dialog boxes appear in English – and all string are translated in Scribus .ts files – this should be a Qt translation lack. You can check Qt translation state [http://l10n-files.qt.io/l10n-files/ here]. The Qt framework is translated [http://code.qt.io/cgit/qt/qttranslations.git/ here], and this is the [https://wiki.qt.io/Qt_Localization official guide] for translators.
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.


We can add some screenshot from the bug: https://bugs.scribus.net/file_download.php?file_id=8347&type=bug Please, fix my text. I'm not a native English speaker.
We can add some screenshot from the bug: https://bugs.scribus.net/file_download.php?file_id=8347&type=bug Please, fix my text. I'm not a native English speaker.

Revision as of 20:27, 2 November 2016

Announcement: Updated Translation Page in Progress
See Official:Translation_Update

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:

  1. some basic dialog boxes appear English
  2. 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.

We can add some screenshot from the bug: https://bugs.scribus.net/file_download.php?file_id=8347&type=bug Please, fix my text. I'm not a native English speaker.