Changes between Version 17 and Version 18 of Internationalization

Timestamp:

Apr 19, 2014, 7:25:42 PM (10 years ago)

Author:

Adrián Chaves

Comment:

--

Internationalization

@@ -48 +48 @@
 Simply put: '''you cannot'''.
 
-You can call any of the global internationalization functions described below, however, strings passed to these functions are not parsed by the message extraction system, which means that translators won’t be able to actually translate the string.
-
-Move any !JavaScript code that requires internationalization of “hard-coded” strings into a function of a separate !JavaScript file. The message extraction system will successfully extract !JavaScript strings from !JavaScript files. You can then call that function from your GUI file. For example:
+You can call any of the global internationalization functions described below, however, strings passed to these functions are not parsed by the [wiki:Message_Extraction message extraction tool], which means that translators won’t be able to actually translate the string.
+
+Move any !JavaScript code that requires internationalization of “hard-coded” strings into a function of a separate !JavaScript file. The message extraction tool will successfully extract !JavaScript strings from !JavaScript files. You can then call that function from your GUI file. For example:
 
 '''Original:'''
@@ -151 +151 @@
 = Internationalizing !JavaScript Simulation Files =
 
-Internationalizing js simulation files isn't easy, as the simulation is supposed to be deterministic, and completely equal between different players in a game (which may use different locales). That's why the simulation may only mark strings for translation (those strings will can found by the message extracting tool), and the actual translation has to happen in the unsynced GUI files.
+Internationalizing js simulation files isn't easy, as the simulation is supposed to be deterministic, and completely equal between different players in a game (which may use different locales). That's why the simulation may only mark strings for translation (those strings will can found by the [wiki:Message_Extraction message extracting tool]), and the actual translation has to happen in the unsynced GUI files.
 
 Marking a string for translation is done with the {{{markForTranslation(message)}}} and {{{markForTranslationWithContext(context, message)}}} functions.
@@ -172 +172 @@
 Internationalizing strings from data files that are loaded by !JavaScript files is a two-step process. You must:
 
- 1. Configure the [wiki:Implementation_of_Internationalization_and_Localization#MessageExtraction message extraction system] to extract the translatable strings from the data file.
+ 1. Configure the [wiki:Message_Extraction message extraction] to extract the translatable strings from the data file.
  1. Use an internationalization function on the !JavaScript side after you load the data file.
 
 == Configuring the Message Extraction System for Data Files ==
-Our message extraction system currently supports extracting data strings from:
+Our [wiki:Message_Extraction message extraction tool] currently supports extracting data strings from:
 
  * '''Plain text files (.txt)'''. The content of plain text files can be extracted  line by line. Paragraphs in these plain text files should not contain  line breaks, otherwise each line is extracted as a separate message,  which is not translator-friendly.
@@ -184 +184 @@
    * Strings from JSON data defined within an XML element.
 
-To configure the message extraction system to extract strings from a new data file, you must edit the `l10n/messages.json` file of the mod folder. In the `messages.json` file of the main mod, `public`, you can find examples of all the supported types of data extraction. For more information, see the [wiki:Implementation_of_Internationalization_and_Localization#MessageExtraction message extraction system documentation.]
+To configure the message extraction system to extract strings from a new data file, you must edit the `l10n/messages.json` file of the mod folder. In the `messages.json` file of the main mod, `public`, you can find examples of all the supported types of data extraction. For more information, see [wiki:Message_Extraction Message Extraction].
 
 == Internationalizing Content that !JavaScript Files Load from Data Files ==
-Once the message extraction system is properly configured to extract the translatable strings from a data file, translators will be able to translate those strings. But for those translations to be actually used, you must internationalize the !JavaScript that loads or uses the data to translate the loaded data at run time.
+Once the message extraction is properly configured to extract the translatable strings from a data file, translators will be able to translate those strings. But for those translations to be actually used, you must internationalize the !JavaScript that loads or uses the data to translate the loaded data at run time.
 
 If the !JavaScript file obtains the data as string that contains the complete message to translate, you can simply pass a variable that contains the translatable string to a global internationalization function such as `translate()` or `translateWithContext()`.
@@ -223 +223 @@
 }}}
 
-It will translate "translatedObject1" using a certain context, and every string in the list of "translatedObject2" also with the same context, after which the list will also be joined with a localised connector (", " in English). So the result could be
+It will translate "translatedObject1" using a certain context, and every string in the list of "translatedObject2" also with the same context, after which the list will also be joined with a localized connector (", " in English). So the result could be
 
 {{{