Qt Creator Translation Page: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:Tools::QtCreator]] | |||
= | = Qt Creator Translation Page = | ||
== Contributed Translations == | |||
Thank you! | The authoritative resource about contributing translations is [[Qt_Localization|the Qt Localization page]].<br />This page is meant as a place to collect information on existing translation efforts. Please feel free to add information on the languages you want to work on and announce your intent at the "Qt localization list&quot;:http://lists.trolltech.com/pipermail/qt-l10n/. Some contact information would be great, too:<s>) | ||
<br />Thank you! | |||
<br />h3. en | |||
<br />There is no English translation</s> it is the native language of Qt Creator. Regional variants and proper plurals are thinkable, but nobody cared enough to do a translation for just that so far. | |||
=== de === | |||
The German translation is maintained as part of Qt Creator itself. Please check the "Qt Creator Page&quot;:http://developer.qt.nokia.com/wiki/Category:Tools::QtCreator for contact information | |||
=== fr === | |||
== | The French translation is maintained by the Qt team of "Developpez.com&quot;:http://www.developpez.net/forums/f376/c-cpp/bibliotheques/qt/. Work in progress can be downloaded on "bugreports.qt.io&quot;:https://bugreports.qt.io. If you want to help or contact the team, you can leave a message on "IDE forum&quot;:http://www.developpez.net/forums/f1450/c-cpp/bibliotheques/qt/outils/edi/ or contact "Thibaut Cuvelier on Developpez.com&quot;:http://www.developpez.net/forums/private.php?do=newpm&amp;u=254882. | ||
=== jp === | |||
Japanese translation seems to be hosted "here&quot;:http://sourceforge.jp/projects/qt-creator-jp/ | |||
See the "blog post&quot;:http://qt-labs.jp/2010/06/24/qt-creator-2-0-in-japanese.html. | |||
=== other languages === | |||
Active Russian, Chinese and Slovenian translation teams exist as well. TODO: elaborate on this. | |||
== User Interface Text Conventions == | |||
==User Interface Text Conventions== | |||
The below guidelines explain what is required to make it easy for interpreters to create good translations for Qt-based applications using Qt Linguist or other tools. Basically, as a developer, always be aware that an interpreter commissioned to create a translation of your code might have no knowledge of software development at all. | The below guidelines explain what is required to make it easy for interpreters to create good translations for Qt-based applications using Qt Linguist or other tools. Basically, as a developer, always be aware that an interpreter commissioned to create a translation of your code might have no knowledge of software development at all. | ||
===Coding=== | === Coding === | ||
* Add linguist comments ( //:) to clarify where appropriate<br /> <pre> //: Contact book | * Add linguist comments ( //:) to clarify where appropriate<br /><pre&gt;<br /> //: Contact book "Add person&quot; button label<br /> return tr("Add&quot;);<br /></pre&gt; | ||
* If the class is not a | * If the class is not a <code&gt;Q_OBJECT&lt;/code&gt;, use<br /><pre&gt;<br /> QCoreApplication::translate("class context&quot;, "text&quot;).<br /></pre&gt; | ||
* Do ''' | * Do '''NOT''' use <code&gt;QObject::tr()</code&gt; as this is confusing since the messages appear grouped by class context in linguist. | ||
* Avoid contractions, do not shout at users using exclamation marks: | * Avoid contractions, do not shout at users using exclamation marks: <code&gt;tr("Can't open the file!")</code&gt; should be <code&gt;tr("Cannot open the file.")</code&gt;. | ||
* Use plurals correctly: | * Use plurals correctly: <code&gt;tr("%1 files found&quot;).arg(number)</code&gt; should be <code&gt;tr("%n files found&quot;, 0, number)</code&gt;. | ||
* Be aware that articles have a grammatical gender in some languages and sentences cannot be as easily constructed as in English, so avoid things like<br /> <pre> tr( | * Be aware that articles have a grammatical gender in some languages and sentences cannot be as easily constructed as in English, so avoid things like<br /><pre&gt;<br /> tr("%1 failed&quot;).arg(someCondition ? "the operation&quot; : "opening a file&quot;).<br /></pre&gt; | ||
* Try to avoid concatenating messages (use | * Try to avoid concatenating messages (use "%1&quot; formatting instead), as some constructions may not work for grammar reasons. Also, '''NEVER''' use leading/trailing/multiple blanks to achieve formatting in a message, as they will invariably be clobbered by translators (think Excel, other tools). So,<br /><pre&gt;<br /> tr("Foo failed: ") + message<br /></pre&gt;<br />should be<br /><pre&gt;<br /> tr("Foo failed: %1&quot;).arg(message)<br /></pre&gt; | ||
* When using Qt Designer, mark text that is not supposed to be translated (for example, dummy data or initial values for label texts that will be set programatically) as such (check off | * When using Qt Designer, mark text that is not supposed to be translated (for example, dummy data or initial values for label texts that will be set programatically) as such (check off 'translate' in the property editor). | ||
* In Qt Designer, preferably use plain text for Tooltips. Should you want some extra formatting, write short, canonical | * In Qt Designer, preferably use plain text for Tooltips. Should you want some extra formatting, write short, canonical HTML in the source tab of the rich text editor:<br /><pre&gt;<br />[html&gt;[head/&gt;[body&gt;[b&gt;Note:[/b&gt;bla….<br /></pre&gt;. | ||
In Qt 4.7, | In Qt 4.7, ALWAYS use the source tab of the Designer rich text editor and verify that you do not get unneeded HTML annotation created by the automatic conversion from the rich text editor tab. Reason being that it contains a lot of stylesheet information and hard-coded fonts that look bad on other platforms and are almost impossible to translate in Linguist (which does not have an HTML editor). | ||
Qt Designer 4.8 has a feature simplifying the rich text (on by default), still, you should verify by looking at the source tab. | Qt Designer 4.8 has a feature simplifying the rich text (on by default), still, you should verify by looking at the source tab. | ||
* Observe the | * Observe the "KDE UI Capitalization guidelines&quot;:http://developer.kde.org/documentation/standards/kde/style/basics/labels.html#items on Capitalization of User Interface Texts should be observed. Here is a short summary: Two major styles are used, book title and sentence style: | ||
** Example of Book Title Capitalization | ** Example of Book Title Capitalization | ||
** Example of sentence style capitalization<br /> Use book style for: | ** Example of sentence style capitalization<br />Use book style for: | ||
** Titles (window, dialog, group box, tab, list view columns, and so on) | ** Titles (window, dialog, group box, tab, list view columns, and so on) | ||
** Functions (menu items, buttons) | ** Functions (menu items, buttons) | ||
** Selectable items (combobox items, listbox items, tree list items, and so on)<br /> Use sentence style for: | ** Selectable items (combobox items, listbox items, tree list items, and so on)<br />Use sentence style for: | ||
** Labels | ** Labels | ||
** Tool tips | ** Tool tips | ||
** Descriptive text | ** Descriptive text | ||
Revision as of 10:06, 24 February 2015
Qt Creator Translation Page
Contributed Translations
The authoritative resource about contributing translations is the Qt Localization page.
This page is meant as a place to collect information on existing translation efforts. Please feel free to add information on the languages you want to work on and announce your intent at the "Qt localization list":http://lists.trolltech.com/pipermail/qt-l10n/. Some contact information would be great, too:)
Thank you!
h3. en
There is no English translation
de
The German translation is maintained as part of Qt Creator itself. Please check the "Qt Creator Page":http://developer.qt.nokia.com/wiki/Category:Tools::QtCreator for contact information
fr
The French translation is maintained by the Qt team of "Developpez.com":http://www.developpez.net/forums/f376/c-cpp/bibliotheques/qt/. Work in progress can be downloaded on "bugreports.qt.io":https://bugreports.qt.io. If you want to help or contact the team, you can leave a message on "IDE forum":http://www.developpez.net/forums/f1450/c-cpp/bibliotheques/qt/outils/edi/ or contact "Thibaut Cuvelier on Developpez.com":http://www.developpez.net/forums/private.php?do=newpm&u=254882.
jp
Japanese translation seems to be hosted "here":http://sourceforge.jp/projects/qt-creator-jp/
See the "blog post":http://qt-labs.jp/2010/06/24/qt-creator-2-0-in-japanese.html.
other languages
Active Russian, Chinese and Slovenian translation teams exist as well. TODO: elaborate on this.
User Interface Text Conventions
The below guidelines explain what is required to make it easy for interpreters to create good translations for Qt-based applications using Qt Linguist or other tools. Basically, as a developer, always be aware that an interpreter commissioned to create a translation of your code might have no knowledge of software development at all.
Coding
- Add linguist comments ( //:) to clarify where appropriate
<pre>
//: Contact book "Add person" button label
return tr("Add");
</pre> - If the class is not a <code>Q_OBJECT</code>, use
<pre>
QCoreApplication::translate("class context", "text").
</pre> - Do NOT use <code>QObject::tr()</code> as this is confusing since the messages appear grouped by class context in linguist.
- Avoid contractions, do not shout at users using exclamation marks: <code>tr("Can't open the file!")</code> should be <code>tr("Cannot open the file.")</code>.
- Use plurals correctly: <code>tr("%1 files found").arg(number)</code> should be <code>tr("%n files found", 0, number)</code>.
- Be aware that articles have a grammatical gender in some languages and sentences cannot be as easily constructed as in English, so avoid things like
<pre>
tr("%1 failed").arg(someCondition ? "the operation" : "opening a file").
</pre> - Try to avoid concatenating messages (use "%1" formatting instead), as some constructions may not work for grammar reasons. Also, NEVER use leading/trailing/multiple blanks to achieve formatting in a message, as they will invariably be clobbered by translators (think Excel, other tools). So,
<pre>
tr("Foo failed: ") + message
</pre>
should be
<pre>
tr("Foo failed: %1").arg(message)
</pre> - When using Qt Designer, mark text that is not supposed to be translated (for example, dummy data or initial values for label texts that will be set programatically) as such (check off 'translate' in the property editor).
- In Qt Designer, preferably use plain text for Tooltips. Should you want some extra formatting, write short, canonical HTML in the source tab of the rich text editor:
<pre>
[html>[head/>[body>[b>Note:[/b>bla….
</pre>.
In Qt 4.7, ALWAYS use the source tab of the Designer rich text editor and verify that you do not get unneeded HTML annotation created by the automatic conversion from the rich text editor tab. Reason being that it contains a lot of stylesheet information and hard-coded fonts that look bad on other platforms and are almost impossible to translate in Linguist (which does not have an HTML editor).
Qt Designer 4.8 has a feature simplifying the rich text (on by default), still, you should verify by looking at the source tab.
- Observe the "KDE UI Capitalization guidelines":http://developer.kde.org/documentation/standards/kde/style/basics/labels.html#items on Capitalization of User Interface Texts should be observed. Here is a short summary: Two major styles are used, book title and sentence style:
- Example of Book Title Capitalization
- Example of sentence style capitalization
Use book style for: - Titles (window, dialog, group box, tab, list view columns, and so on)
- Functions (menu items, buttons)
- Selectable items (combobox items, listbox items, tree list items, and so on)
Use sentence style for: - Labels
- Tool tips
- Descriptive text