Changes between Version 31 and Version 32 of Translating

Timestamp:

May 11, 2010 9:18:23 AM (14 years ago)

Author:

Christian Pötzsch

Comment:

Sun -> Oracle

Translating

@@ -84 +84 @@
  4. Language country name, in English (the original value is {{{--}}}). The same as 2, but a common English spelling of the territory (country).
 
- 5. Comma-separated list of translators (the original value is {{{Sun Microsystems, Inc.}}}). 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.
+ 5. Comma-separated list of translators (the original value is {{{Oracle Corporation}}}). 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.
 
 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.
@@ -90 +90 @@
 === Picking up recent changes to the translation files ===
 
-Existing {{{.ts}}} files are periodically synchronized with the source code by the GUI maintainer at Sun, 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. See ticket:2018 for more information about the synchronization process.
+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. See ticket:2018 for more information about the synchronization process.
 
-In order to get the latest changes to the existing {{{.ts}}} that appear as a result of the described synchronization, as well as all other modifications made by Sun developers or other contributors, you will need to do the following steps. These steps imply that you already performed step 5 of the section [#Preparingatranslationtoanewlanguage Preparing a translation to a new language] above and have a copy of the NLS subdirectory in the {{{VirtualBox_nls/}}} directory of your local hard drive.
+In order to get the latest changes to the existing {{{.ts}}} that appear as a result of the described synchronization, as well as all other modifications made by Oracle developers or other contributors, you will need to do the following steps. These steps imply that you already performed step 5 of the section [#Preparingatranslationtoanewlanguage Preparing a translation to a new language] above and have a copy of the NLS subdirectory in the {{{VirtualBox_nls/}}} directory of your local hard drive.
 
  1. Go to the {{{VirtualBox_nls/}}} directory and type the following command in the command line window (terminal) of your host OS:
@@ -154 +154 @@
 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. 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.
 
-'''Please note''' that you should always run the {{{svn update}}} command as described in [#Pickinguprecentchangestothetranslationfiles Picking up recent changes to the translation files] before packing and attaching your {{{.ts}}} files! This way, you will make sure that your version corresponds to the latest version from the !VirtualBox SVN repository. Note that if the translation file you attach to ticket:2018 doesn't merge cleanly to the SVN head, it will be rejected because the GUI maintainer at Sun doesn't know all possible languages and therefore cannot resolve possible merge conflicts for you. 
+'''Please note''' that you should always run the {{{svn update}}} command as described in [#Pickinguprecentchangestothetranslationfiles Picking up recent changes to the translation files] before packing and attaching your {{{.ts}}} files! This way, you will make sure that your version corresponds to the latest version from the !VirtualBox SVN repository. Note that if the translation file you attach to ticket:2018 doesn't merge cleanly to the SVN head, it will be rejected because the GUI maintainer at Oracle doesn't know all possible languages and therefore cannot resolve possible merge conflicts for you. 
 
-'''PLEASE REMEMBER''' that before your translation can be included into the !VirtualBox code base and distribution archives, '''you must allow Sun Microsystems 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 Sun Contributor's Agreement] (ICA) and send it to Sun Microsystems or to make the following statement directly in the ticket:2018 comment where you attach your translation source file:
+'''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 Sun Contributor's Agreement] (ICA) and send it to Oracle Corporation or to make the following statement directly in the ticket:2018 comment where you attach your translation source file:
 
 {{{
@@ -165 +165 @@
 assuming that {{{<MyLanguage>}}} is the language name, {{{<my_MY>}}} is the language identifier and {{{<my_full_name>}}} is your '''full name''' that has exactly the same spelling you used in the .ts file itself (in the list of translators in the special context {{{@@@}}}). 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.
 
-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 addresses internally within Sun Microsystems in order to be able to contact each of them individually.
+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 addresses internally within Oracle Corporation in order to be able to contact each of them individually.