Changes between Version 15 and Version 16 of Translating

Timestamp:

Apr 18, 2007 4:57:49 PM (17 years ago)

Author:

Dmitry A. Kuminov

Comment:

Added info about qt_xx_YY.ts.

Translating

@@ -11 +11 @@
 <component>_<lang>
 }}}
-where {{{<component>}}} is the name of the component (currently, {{{VirtualBox}}} is the only possible value which stands for the ''!VirtualBox GUI'' front-end) and {{{<lang>}}} is the language identifier.
+where {{{<component>}}} is the name of the component and {{{<lang>}}} is the language identifier. Possible values for the {{{<component>}}} part are:
+||{{{VirtualBox}}} ||''!VirtualBox GUI'' front-end||
+||{{{qt}}}         ||Qt library itself (built-in dialogs and other resources like key names)||
 
 The language identifier has the form of {{{<language>[_<TERRITORY>]}}}, where {{{<language>}}} is a two-letter language code as defined by [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639], and optional {{{<TERRITORY>}}} is a two-letter territory (country) code as defined by [http://en.wikipedia.org/wiki/ISO_3166-1 ISO 3166]. See the examples of language file names at the end of this section.
@@ -27 +29 @@
 Here are some examples of language file names:
 
- - {{{VirtualBox_de.qm}}} (Deutsch language, all territories)
- - {{{VirtualBox_ru.qm}}} (Russian language, all territories)
- - {{{VirtualBox_zh_TW.qm}}} (Chinese language, Taiwan)
+ - {{{qt_de.qm}}} (Qt translation, Deutsch language, all territories)
+ - {{{VirtualBox_ru.qm}}} (!VirtualBox GUI translation, Russian language, all territories)
+ - {{{VirtualBox_zh_TW.qm}}} (!VirtualBox GUI translation, Chinese language, Taiwan)
 
 == Prerequisites ==
@@ -44 +46 @@
  2. Check that your language is not yet supported by visiting this [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls directory] in the source tree.
  3. Add a comment to ticket:234 that you are going to maintain the translation to your language to inform other people that may also want to participate. Before adding such a comment, check that nobody else has already started the translation to the same language.
- 4. Download the translation template [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls/VirtualBox_xx_YY.ts VirtualBox_xx_YY.ts].
- 5. Rename the template to {{{VirtualBox_my_MY.ts}}}.
- 6. Start Qt Linguist, open the {{{VirtualBox_my_MY.ts}}} file and translate it.
- 7. Make sure all the fields in a special context named {{{@@@}}} are properly translated (see below).
+ 4. Download translation templates for each component: [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls/VirtualBox_xx_YY.ts VirtualBox_xx_YY.ts] and [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls/qt_xx_YY.ts qt_xx_YY.ts].
+ 5. Rename the templates to {{{VirtualBox_my_MY.ts}}} and {{{qt_my_MY.ts}}}, respectively.
+ 6. Start Qt Linguist, open and translate renamed files you got in step 5.
+ 7. Make sure all the fields in a special context named {{{@@@}}} in the file {{{VirtualBox_my_MY.ts}}} are properly translated (see below).
  8. Check your translation at runtime by referring to the '''Testing the translation''' section below.
 
 === Special context @@@ ===
 
-A special context named {{{@@@}}} contains translatable items necessary to identify the given translation file, so you must ensure they are properly translated. There are five items in this context:
+A special context named {{{@@@}}} contains translatable items necessary to identify the given translation file, so you must ensure they are properly translated. This context is currently present only in the {{{VirtualBox_my_MY.ts}}} file. There are five items in this context:
 
  1. Native language name (the original value is {{{English}}}). Translate it to a common, human-readable name of the language of your translation, as written in the language itself. For example, for Russian, it will be {{{Русский}}}. Please note that the {{{<language>}}} part in the name of the {{{.ts}}} file must match the language specified here.
@@ -70 +72 @@
  1. Define a language identifier for your language according to the rule described above. If translations to your language vary depending on the country, use the {{{_<TERRITORY>}}} suffix, otherwise omit it (i.e. no need to apply the suffix if it represents the only possible country). Let's say that your language code is {{{my_MY}}} for the purpose of this description.
  2. Look through comments to ticket:234 to find out who is currently maintaining the translation to your language. Contact these people in order to coordinate your work and avoid conflicts
- 3. Goto this [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls directory] and download the {{{VirtualBox_my_MY.ts}}} file.
- 4. Start Qt Linguist, open the {{{VirtualBox_my_MY.ts}}} file and translate it.
+ 3. Goto this [http://virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls directory] and download translation files for all components ({{{VirtualBox_my_MY.ts}}} and {{{qt_my_MY.ts}}}).
+ 4. Start Qt Linguist, open the downloaded files and update translations.
  5. Check your translation at runtime by referring to the '''Testing the translation''' section below.
 
@@ -91 +93 @@
 
  1. Select '''File -> Release...''' from the main menu of Qt Linguist.
- 2. Specify {{{<path_to_VirtualBox_exe>/nls/VirtualBox_my_MY.qm}}} as the target path and file name and press Ok. This will generate a binary language file and save it to the proper directory.
- 3. Setup the locale corresponding to the {{{my_MY}}} language identifier and start {{{VirtualBox.exe}}}. The language file should be loaded automatically if you did everything right.
+ 1. Specify {{{<path_to_VirtualBox_exe>/nls/VirtualBox_my_MY.qm}}} as the target path and file name and press Ok. This will generate a binary language file and save it to the proper directory.
+ 1. Repeat the previous step for all other components ({{{qt_my_MY.qm}}}).
+ 3. Setup the locale corresponding to the {{{my_MY}}} language identifier and start {{{VirtualBox.exe}}}. The language files should be loaded automatically if you did everything right.
  4. Navigate through '''all''' parts of the user interface and check the quality and meaningfulness of the translation.
 
-Please note that you cannot test translations with !VirtualBox version 1.3.8 and earlier because the translation suppport was not enabled in those releases. Presently, the only option to test is to use the SVN build. All future releases of !VirtualBox will have the translation support enabled.
+'''Please note''' that you cannot test translations with !VirtualBox version 1.3.8 and earlier because the translation suppport was not enabled in those releases. Presently, the only option to test is to use the SVN build. All future releases of !VirtualBox will have the translation support enabled.
 
 == Submitting the translation ==
 
-When you think your translation looks good and ready to be shared with others, you may submit the translation source file you created ({{{VirtualBox_my_MY.ts}}}, according to the examples above) by packing it to a .zip archive and attaching to ticket:234.
+When you think your translation looks good and ready to be shared with others, you may submit the translation source files you created ({{{VirtualBox_my_MY.ts}}} and {{{qt_my_MY.ts}}}, according to the examples above) by packing it to a .zip archive named {{{VirtualBox_my_MY.zip}}} and attaching to ticket:234.
 
 The same thing should be done after you have updated an existing translation, but please be careful with the name of the file you are attaching and make sure you will not replace somebody's else attachment with the same name (you may and should replace a previous attachment of the same name only if it was also attached by you and only if it contains an outdated version of the same translation file you are attaching now).