Changes between Version 17 and Version 18 of Translating

Timestamp:

May 2, 2007 12:33:58 PM (17 years ago)

Author:

Dmitry A. Kuminov

Comment:

Added Translation hint #5

Translating

@@ -88 +88 @@
  3. Translate only human-readable words and sentences. Leave HTML markup and other sorts of special characters untouched -- otherwise you may completely break the text appearance in the UI.
  4. Don't translate items starting with the {{{#}}} (hash) sign in contexts {{{VBoxGlobalSettingsDlg}}} and {{{VBoxVMSettingsDlg}}}, such as {{{#general}}}, {{{#input}}} and so on. They are responsible for the settings category hyper-link feature on the VM Details page and translating them will break this feature.
+ 5. When Qt Linguist shows the source text of the translatable item, it uses special text fragments inside it to mark unprintable characters, for example: {{{(new-line)}}} for new-line marks or {{{(sp)}}} for ambiguous space characters. However, if you copy the source text to the translation field (to use it as a template for translation), Qt Linguist will not replace these special fragments back with real control/formatting characters -- they will remain {{{(new line}}}} and {{{(sp)}}} in the translation and will appear like that in the GUI as well. Therefore, you should be careful and always replace them with the corresponding formatting characters (new-line or space) manually.
 
 == Testing the translation ==