Changes between Version 18 and Version 19 of Translating
- Timestamp:
- Jun 7, 2007 6:31:59 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Translating
v18 v19 3 3 This document describes how users without a strong technical background in software engineering can contribute translations to other languages. The process is very straightforward and based on the easy to use [http://doc.trolltech.com/3.3/linguist-manual-3.html Qt Linguist] tool which is a part of the Qt Toolkit version 3. 4 4 5 Translation is possible for all languages, including languages with non-latin alphabets. The process requires you to perform an initial translation which you then have to keep up to date as !VirtualBox evolves. The original language is English which -- together with German -- is handled by !InnoTek. The Qt Linguist tool will also assist you in finding where your translation has to be updated for a new release of !VirtualBox.5 Translation is possible for all languages, including languages with non-latin alphabets. The process requires you to perform an initial translation which you then have to keep up to date as !VirtualBox evolves. The original language is English which -- together with German -- is handled by innotek. The Qt Linguist tool will also assist you in finding where your translation has to be updated for a new release of !VirtualBox. 6 6 7 7 == Language file naming and location == … … 60 60 3. Language name, in English (the original value is {{{English}}}). The same as 1, but a common English spelling of the language name. 61 61 4. Language country name, in English (the original value is {{{--}}}). The same as 2, but a common English spelling of the territory (country). 62 5. Comma-separated list of translators (the original value is {{{ InnoTek}}}). This item used is to specify a list of authors who worked on this translation. Please use the Latin alphabet here, to make it readable by everyone.62 5. Comma-separated list of translators (the original value is {{{innotek}}}). This item used is to specify a list of authors who worked on this translation. Please use the Latin alphabet here, to make it readable by everyone. 63 63 64 64 Every item in this special context has a self-descriptive comment field, so it will not be difficult to locate them in your translation file even if the order there differs from the order they are listed here. … … 78 78 Please read carefully the '''Translation hints''' section below to learn more about the translation process. 79 79 80 Existing translation source files are periodically synchronized with the source code by the GUI maintainer at !InnoTek, either a few weeks before a new product release, or after a big number of language-related changes in the UI. This synchronization is performed to add new (untranslated) strings used in the UI to translation files, which then need to be translated by contributors. See ticket:234 for more information about the synchronization process.80 Existing translation source files are periodically synchronized with the source code by the GUI maintainer at innotek, either a few weeks before a new product release, or after a big number of language-related changes in the UI. This synchronization is performed to add new (untranslated) strings used in the UI to translation files, which then need to be translated by contributors. See ticket:234 for more information about the synchronization process. 81 81 82 82 == Translation hints == 83 83 84 This section contains important notes about translating the VirtualBox product.84 This section contains important notes about translating the !VirtualBox product. 85 85 86 86 1. Read the [http://doc.trolltech.com/3.3/linguist-manual-3.html Qt Linguist manual] to get general information about translating Qt applications. Pay special attention to understanding the status of translatable items (unfinished, obsolete). … … 100 100 4. Navigate through '''all''' parts of the user interface and check the quality and meaningfulness of the translation. 101 101 102 '''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.102 '''Please note''' that you cannot test translations with !VirtualBox before 1.4.0 because the translation suppport was not enabled in those releases. So either use the last release or compile the current code from SVN. 103 103 104 104 == Submitting the translation == … … 108 108 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). 109 109 110 '''PLEASE REMEMBER''' that before your translation can be included into the !VirtualBox code base and distribution archives, '''you must allow !InnoTek to make usage of your contributions'''. The [wiki:Contributor_information] section describes how to do it. Basically, you have two options: either to fill out the [wiki:ICA InnoTek Contributor's Agreement] (ICA) and send it to !InnoTek or to make the following statement directly in the ticket:234 comment where you attach your translation source file:110 '''PLEASE REMEMBER''' that before your translation can be included into the !VirtualBox code base and distribution archives, '''you must allow innotek to make usage of your contributions'''. The [wiki:Contributor_information] section describes how to do it. Basically, you have two options: either to fill out the [wiki:ICA innotek Contributor's Agreement] (ICA) and send it to innotek or to make the following statement directly in the ticket:234 comment where you attach your translation source file: 111 111 {{{ 112 112 The MyLanguage (my_MY) translation attached here by Foo Bar is published under the terms of the [wiki:"MIT license"]. … … 114 114 assuming that {{{MyLanguage}}} is the language name, {{{my_MY}}} is the language identifier and {{{Foo Bar}}} is your full name. It's enough to do it only once for a given language. If you translate !VirtualBox to more than one language than a separate statement for every language is necessary. 115 115 116 The '''second requirement''' for including your translation to the product is to send an e-mail to {{{info {at} innotek.de}}} where you mention your full name and the language you are translating to. This is necessary to keep track of all active translators and their e-mail addressees internally within !InnoTek in order to be able to contact each of them individually.116 The '''second requirement''' for including your translation to the product is to send an e-mail to {{{info {at} virtualbox.org}}} where you mention your full name and the language you are translating to. This is necessary to keep track of all active translators and their e-mail addressees internally within innotek in order to be able to contact each of them individually.
