VirtualBox

Changes between Version 43 and Version 44 of Translating


Ignore:
Timestamp:
08/14/2019 08:20:58 AM (3 years ago)
Author:
gombara
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Translating

    v43 v44  
    4949 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. 
    5050 
    51  2. Check that your language is not yet in the list on ticket:14091 (the translation ticket). 
     51 2. Check that your language is not yet in the list on ticket:17708 (the translation ticket). 
    5252 
    53  3. Add a comment to ticket:14091 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. 
     53 3. Add a comment to ticket:17708 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. 
    5454 
    5555 4. Download the files {{{VirtualBox_xx_YY.ts}}} and {{{qt_xx_YY.ts}}} from the web page [https://www.virtualbox.org/download/testcase/nls/] to your computer (please be aware that the address of that page may change occasionally and check back to this instruction page if you are in doubt) and rename the files for your language using the language identifiers described above.  For example, the name {{{VirtualBox_yi.ts}}} would be correct for Yiddish, and {{{qt_sw_TZ.ts}}} for Tanzanian Swahili. 
     
    8383=== Picking up recent changes to the translation files === 
    8484 
    85 Existing {{{.ts}}} files are periodically synchronized with the source code by the GUI maintainer at Oracle, either a few weeks before a new product release, or after a big number of language-related changes in the user interface (UI). This synchronization is performed to add new (untranslated) strings used in the UI to {{{.ts}}} files which then need to be translated by contributors. Updates will be announced on ticket:14091.  To translate the newly added text, you should replace the copies of the translation files on your computer with the new ones on the web page, which will contain any work which you have submitted previously. 
     85Existing {{{.ts}}} files are periodically synchronized with the source code by the GUI maintainer at Oracle, either a few weeks before a new product release, or after a big number of language-related changes in the user interface (UI). This synchronization is performed to add new (untranslated) strings used in the UI to {{{.ts}}} files which then need to be translated by contributors. Updates will be announced on ticket:17708.  To translate the newly added text, you should replace the copies of the translation files on your computer with the new ones on the web page, which will contain any work which you have submitted previously. 
    8686 
    8787== Updating a translation done by someone else == 
     
    9191 1. Determine the language identifier for your language as described above. If translations to your language vary depending on the country or region, 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. 
    9292 
    93  2. Look through comments to ticket:14091 to find out who is currently maintaining the translation to your language. Contact these people in order to coordinate your work and avoid conflicts by adding a comment to ticket:14091 (this is less important if you will be working on a new regional variant of the language, but consider that you may still gain a lot from working together). 
     93 2. Look through comments to ticket:17708 to find out who is currently maintaining the translation to your language. Contact these people in order to coordinate your work and avoid conflicts by adding a comment to ticket:17708 (this is less important if you will be working on a new regional variant of the language, but consider that you may still gain a lot from working together). 
    9494 
    9595 3. Copy the existing translation files from the web page mentioned in the [#Preparingatranslationtoanewlanguage Preparing a translation to a new language] section.  If you are working on a new regional variant of the language rename the files appropriately. 
     
    131131== Submitting the translation == 
    132132 
    133 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:14091. 
     133When 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:17708. 
    134134 
    135135The 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. Note though that you may and normally should replace a previous attachment of the same name if it was also attached by you and if it contains an outdated version of the same translation file you are attaching now. 
    136136 
    137 '''PLEASE REMEMBER''' that before your translation can be included into the !VirtualBox code base and distribution archives, '''you must allow Oracle Corporation to make use 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 Oracle Contributor's Agreement] (ICA) and send it to Oracle Corporation or to make the following statement directly in the ticket:14091 comment where you attach your translation source file: 
     137'''PLEASE REMEMBER''' that before your translation can be included into the !VirtualBox code base and distribution archives, '''you must allow Oracle Corporation to make use 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 Oracle Contributor's Agreement] (ICA) and send it to Oracle Corporation or to make the following statement directly in the ticket:17708 comment where you attach your translation source file: 
    138138 
    139139{{{ 

www.oracle.com
ContactPrivacy policyTerms of Use