Oracle® Database Express Edition Application Express User's Guide Release 2.1 Part Number B25309-01 |
|
|
View PDF |
This section describes how to translate an application built-in Application Builder.
This section contains the following topics:
See Also:
"Working in a Global Environment" in Oracle Database Express Edition 2 Day Developer GuideYou can develop applications in Application Builder that can run concurrently in different languages. A single Oracle database instance and Oracle Application Express can support multiple database sessions customized to support different languages.
In general, translating an application built-in Application Builder involves the following steps:
Map primary and target application IDs
Seed and export text to a file for translation
Translate the text in the file
Apply and publish the translated file
See Also:
"Understanding the Translation Process"Topics in this section include:
After you create an application, you specify a language preference on the Edit Application Attributes page. Under Globalization, you select a primary application language and select how the Application Express engine determines the application language. You can specify to have the application language based on the user's browser language preference, an application preference, or an item preference.
Use the following rules to determine which translated version to use:
Look for an exact match between the user language preference and the language code of the translated application.
Look for a truncated match. That is, see if the language and locale exist. For example, if the user language preference is en-us
and the translated version of en-us
does not exist, look for a translated application that has the language code en
.
Use the primary application language.
For example, suppose you create an application with the primary language of German, de
, and you create a translated version of the application with a language code of en-us
. Users accessing this application with a browser language of en-us
execute the English en-us
version of the application. Users accessing the application with a browser language of en-gb
view the application in the application's primary language. In this example, these users see the application in German, which is the application's primary language. For this example, you should create the translated English version using language code en
to encompass all variations of en
.
After Oracle Application Express determines the language for an application, the Application Express engine alters the database language for a specific page request. It then looks for a translated application in the appropriate language. If the Application Express engine finds that language, it render the application using that definition. Otherwise, it renders the application in the base (or primary) application language.
Note that the text that displays within an application is not translated on the fly. Oracle Application Express dynamically collects page attributes from either a base language application definition or an alternative application definition.
When you build an application in Application Builder, you define a large number of declarative attributes such as field labels, region headings, page header text, and so on. Using the steps described in this section, you can make all the application definition attributes within your application translatable.
Application Builder includes two shortcut types that enable you to reference translatable messages:
Message. Use this shortcut to reference a translatable message at run time. Note that the name of the shortcut must match the corresponding message name. At run time, the name of the shortcut expands to the text of the translatable message for the current language.
Message with JavaScript Escaped Single Quotes. Use this shortcut to reference a shortcut inside of a JavaScript literal string and reference a translatable message at run time. This shortcut defines a text string. When the shortcut is referenced, it escapes the single quotation marks required for JavaScript.
See Also:
"Using Shortcuts"If your application includes PL/SQL regions or PL/SQL processes, you may need to translate any generated HTML or text. Within Application Builder, these types of generated HTML and text are called messages. You can define all messages and translate them on the Translatable Messages page. You can use the HTMLDB_LANG
.MESSAGE
API to translate text strings from PL/SQL stored procedures, functions, triggers, packaged procedures, and functions.
Dynamic translations are used for database data that needs to be translated at run time. For example, you might use a dynamic translation to translate a list of values based on a database query. A dynamic translation consists of a translate-from language string, a language code, and a translate-to string. You can also use the HTMLDB_LANG.LANG
API to retrieve dynamic translations programmatically.
By default, page region titles are included in the generated translation file. However, you can mark a region title as not translatable.
To mark a region title as not translatable:
Navigate to the Page Definition:
Navigate to the Database Home Page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
On the Page Definition, select the region title.
The Edit Region page appears.
Select the exclude title from translation check box.
By default, templates are not translatable, and therefore are not included in the generated translation file. Generally, templates do not and should not contain translatable text. However, if you need to mark a template as translatable, select the Translatable check box on the Edit Page Template page.
To identify a template as translatable:
On the Database Home Page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
Under User Interface, select Templates.
The Templates page appears.
Locate the template you want to edit and select the template name.
Under Template Identification, select Translatable.
You can include translatable text at the application-level by defining the translatable text using static substitution strings. Because application-level attributes are translated, any text defined as a static substitution string will be included in the generated translation file.
See Also:
Globalization attributes specify how the Application Express engine determines the primary language of an application.
To edit globalization attributes:
On the Database Home Page, click the Application Builder icon.
Select an application.
Click Edit Attributes.
Click Edit Globalization Attributes.
From Application Primary Language, select the language in which the application is being developed.
From Application Language Derived From, specify how the Application Express engine determines (or derives) the application language. Available options are described in Table 14-1.
Table 14-1 Application Language Derived From Options
Option | Description |
---|---|
No NLS (Application not translated) |
Select this option if the application will not be translated. |
Use Application Primary Language |
Determines the application's primary language based on the Application Primary Language attribute. (See step 5.) |
Browser (use browser language preference) |
Determines the application's primary language based on the user's browser language preference. |
Application Preference (use FSP_LANGUAGE_PREFERENCE) |
Determines the application's primary language based a value defined using the See Also: "SET_PREFERENCE Procedure" |
Item Preference (use item containing preference) |
Determines the application's primary language based on an application-level item called |
See Also:
"Configuring Standard Application Attributes", "Configuring Globalization Attributes", and "About Supported Globalization Codes"The Application Express engine applies globalization settings for each rendered page. This default behavior can impact the display of certain items such as numbers and dates.
For example, suppose your application determines the application language based on the user's browser language preference. If the Application Express engine determines the users's browser language preference is French, it displays dates and numbers in a format that conforms to French standards. You can override this default behavior and explicitly control how items display by applying a format mask. You apply a format mask by making a selection from the Display As list:
When you create the item
After you create the item by editing the item attributes
To edit item attributes:
On the Database Home Page, click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
Under Items, select the item name.
The Edit Page Item page appears.
Under Identification, make a selection from the Display As list.
See Also:
"Items" for information about item attributes.If your application needs to run in several languages simultaneously (such as Chinese and Japanese), consider configuring your database with a character set to support all of the languages. The same character set has to be configured in the corresponding database access descriptor (DAD) in mod_plsql. UTF8 and AL32UTF8 are the character sets you can use to support almost all languages around the world.
See Also:
"Working in a Global Environment" in Oracle Database Express Edition 2 Day Developer GuideTo translate an application developed in Application Builder, you must map the primary and target application IDs, seed and export text to a translation file, translate the text, and then apply and publish the translation file.
Topics in this section include:
You perform the translation process on the Translate Application page.
To navigate to the Translate Application page:
On the Database Home Page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, select Translation Services.
The Translate Application page appears.
The first step in translating an application is to map the primary and target application IDs. The primary application is the application to be translated. The target application is the resulting translated application.
To map the primary and target application IDs:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Map your primary language application to a translated application ID.
The Application Mappings page appears.
Click Create.
On the Translation Application Mapping page:
Translation Application - Enter a numeric application ID to identify the target application. The translated application ID must be an integer and cannot end in zero.
Translation Application Language Code - Select the language into which you are translating.
Image Directory - Enter the directory from where the images will be obtained.
This attribute determines the virtual path for translated images. For example, if your primary language application had an image prefix of '/images/'
, you could define additional virtual directories for other languages, such as '/images/de/'
for German or '/images/es/'
for Spanish.
Click Create.
The second step is to seed the translation table and then export the translation text to a translation file.
Topics in this section include:
To translate an application, you must seed the translation. Seeding the translation copies all translatable text into the Translation Text repository. After you have seeded the application and specified the language in the Translation Text repository, you can then generate and export an XLIFF file for translation.
The seeding process keeps your primary language application synchronized with the Translation Text repository. You should run the seed process any time your primary language application changes.
To seed translatable text:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Seed and export the translation text of your application into a translation file.
From Language Mapping, select the appropriate primary and target application ID map.
Click Seed Translatable Text.
The XLIFF Export page appears.
Note:
XML Localization Interchange File Format (XLIFF) is an XML-based format for exchanging localization data. For information about the XLIFF or to view the XLIFF specification, see:http://www.xliff.org
After you have seeded translatable text, a status box displays at the top of the XLIFF Export page indicating the total number of attributes that may require translation, including the number of:
Existing updated attributes that may require translation
New attributes that may require translation
Purged attributes that no longer require translation
You can use this information to determine if you need to export translatable text for an entire application or just a specific page.
The XLIFF Export page is divided into two sections. Use the upper section of the page to export translatable text for an entire application (that is, all pages, lists of values, messages, and so on). Use the lower section to export translatable text for a specific page.
To export translatable text for an entire application:
Seed the translatable text. See "Seeding Translatable Text".
Under Step 2, Export XLIFF:
From Application, select the appropriate primary and target application ID map.
Specify whether or not to include XLIFF target elements.
Under Export, specify what translation text is included in your XLIFF file.
Click Export XLIFF for Application.
Follow the on-screen instructions.
To export translatable text for a specific page:
Seed the translatable text as described in "Seeding Translatable Text".
Under Export XLIFF for specific Page:
From Application, select the appropriate primary and target application ID map.
Specify whether or not to include XLIFF target elements.
Under Export, specify what translation text is included in your XLIFF file.
Click Export XLIFF for Page.
Follow the on-screen instructions.
When Oracle Application Express generates an XLIFF document, each document contains multiple translation units. Each translation unit consists of a source element and a target element. The XLIFF document can be generated with both the source and target elements for each translation unit. You have the option of generating a file containing only source elements. The updated translations will be applied from the target elements of the translation units.
Use the options under Export to specify what translation text is included in your XLIFF file. Select All translatable elements to include all translation text for an application. In contrast, select Only those elements requiring translation to include only new elements that have not yet been translated. Only those elements requiring translation produces an XLIFF file containing new or modified translation units. Also, if translation units were intentionally not previously translated (that is, the source of the translation element equals the target of the translation element), those translation units will also be included in the file.
After you export a translatable file to XLIFF format, you can translate it into the appropriate languages. Because XLIFF is an open standard XML file for exchanging translation, most translation vendors should support it. Oracle Application Express only supports XLIFF files encoded in UTF-8 character sets. In other words, it exports XLIFF files for translation in UTF-8 and assumes that the translated XLIFF files will be in the same character set.
Translation is a time-consuming task. Oracle Application Express supports incremental translation so that application development can be done in parallel with the translation. A XLIFF file can be translated and uploaded to Oracle Application Express even when only part of the XLIFF file is translated. For strings that have no translation in the corresponding translated application, Oracle Application Express uses the corresponding ones in the primary language.
See Also:
For more information about the XLIFF, or to view the XLIFF specification see:http://www.xliff.org
After your XLIFF document has been translated, the next step is to upload it.
To upload a translated XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
Click Upload XLIFF.
On the XLIFF Upload page:
Specify a title.
Enter a description.
Click Browse and locate the file to be uploaded.
Click Upload XLIFF File.
The uploaded document appears in the XLIFF Files repository.
After you upload an XLIFF document, the next step is to apply the XLIFF document and then publish the translated application. When you apply an XLIFF document, the Application Express engine parses the file and then updates the translation tables with the new translatable text.
Publishing your application creates a copy of the base language application, substituting the translated text strings from your translations table. This published application can then be used to render your application in alternate languages.
Remember that in order to run an application in an alternative language, you need to run it with globalization settings that will cause an alternative language version to display. For example, if the language is derived from the browser language, you must set the browser language to the same language as the translated application.
To apply and publish a translated XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
In the XLIFF Files repository, click the View icon adjacent to the document you want to publish.
From Apply to, select the appropriate primary and target application ID map.
Click Apply XLIFF Translation File.
Click Publish Application.
To delete an uploaded XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
In the XLIFF Files repository, select the check box to the left of the document title.
Click Delete Checked.
You should verify the existence of the translated application after it is published. Translated applications do not display in the Available Applications list on the Application Builder home page. Instead, use the Application Navigate list on the left side of the page.
Note that in order for a translated application to appear in Application Builder, you need to make sure that you have correctly configured the application Globalization attributes.
If your application includes PL/SQL regions or PL/SQL processes or calls PL/SQL package, procedures, or functions, you may need to translate generated HTML. First, you define each message on the Translatable Messages page. Second, you use the HTMLDB_LANG
.MESSAGE
API to translate the messages from PL/SQL stored procedures, functions, triggers, or packaged procedures and functions.
You create translatable messages on the Translate Messages page.
To define a new translation message:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Optionally translate messages which are used by PL/SQL procedures and functions.
On the Translate Messages page, click Create.
On the Identify Text Message page:
In Name, enter a name to identify the text message
In Language, select the language for which the message would be used
In text, enter the text to be returned when the text message is called.
For example, you could define the message GREETING_MSG
in English as:
Good morning %0
Or, you could define the message GREETING_MSG
in German as:
Guten Tag %0
Click Create.
Use the HTMLDB_LANG
.MESSAGE
API to translate text strings (or messages) generated from PL/SQL stored procedures, functions, triggers, packaged procedures, and functions.
Syntax
HTMLDB_LANG.MESSAGE ( p_name IN VARCHAR2 DEFAULT NULL, p0 IN VARCHAR2 DEFAULT NULL, p1 IN VARCHAR2 DEFAULT NULL, p2 IN VARCHAR2 DEFAULT NULL, ... p9 IN VARCHAR2 DEFAULT NULL, p_lang IN VARCHAR2 DEFAULT NULL) RETURN VARCHAR2;
Parameters
Table 14-2 describes the parameters available in the HTMLDB_LANG
.MESSAGE API
.
Table 14-2 HTMLDB_LANG.MESSAGE Parameters
Parameter | Description |
---|---|
|
Name of the message as defined in Oracle Application Express. |
...
|
Dynamic substitution value: |
|
Language code for the message to be retrieved. If not specified, Oracle Application Express uses the current language for the user as defined in the Application Language Derived From attribute. See Also: "Specifying the Primary Language for an Application" |
Example
The following example assumes you have defined a message called GREETING_MSG
in your application in English as Good morning%0
and in German as Guten Tag%1
. The following example demonstrates how you could invoke this message from PL/SQL:
BEGIN -- -- Print the greeting -- HTMLDB_LANG.MESSAGE('GREETING_MSG', V('APP_USER')); END;
How the p_lang
attribute is defined depends on how the Application Express engine derives the Application Primary Language. For example, if you are running the application in German and the previous call is made to the HTMLDB_LANG
.MESSAGE
API, the Application Express engine first looks for a message called GREETING_MSG
with a LANG_CODE
of de
. If it does not find anything, then it will revert to the Application Primary Language attribute. If it still does not find anything, the Application Express engine looks for a message by this name with a language code of en-us
.
See Also:
"Specifying the Primary Language for an Application" for information about the Application Primary Language attributeYou create a dynamic translation to translate dynamic pieces of data. For example, you might use a dynamic translation on a list of values based on a database query.
Dynamic translations differ from messages in that you query a specific string rather than a message name. You define dynamic translations on the Dynamic Translations page. You then use the HTMLDB_LANG
.LANG
API to return the dynamic translation string identified by the p_primary_text_string
parameter.
You define dynamic translations on the Dynamic Translations page. A dynamic translation consists of a translate-from language string, a language code, and a translate-to string.
To define a dynamic translation:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Optionally identify any data that needs to be dynamically translated to support SQL based lists of values.
On the Dynamic Translations page, click Create and specify the following:
In Language, select a target language.
In Translate From Text, enter the source text to be translated.
In Translate To, enter the translated text.
Click Create.
Syntax
HTMLDB_LANG.LANG ( p_primary_text_string IN VARCHAR2 DEFAULT NULL, p0 IN VARCHAR2 DEFAULT NULL, p1 IN VARCHAR2 DEFAULT NULL, p2 IN VARCHAR2 DEFAULT NULL, ... p9 IN VARCHAR2 DEFAULT NULL, p_primary_language IN VARCHAR2 DEFAULT NULL) RETURN VARCHAR2;
Parameters
Table 14-3 describes the parameters available in the HTMLDB_LANG
.LANG
API.
Table 14-3 HTMLDB_LANG.LANG Parameters
Parameter | Description |
---|---|
|
Text string of the primary language. This will be the value of the Translate From Text in the dynamic translation. |
...
|
Dynamic substitution value: |
|
Language code for the message to be retrieved. If not specified, Oracle Application Express uses the current language for the user as defined in the Application Language Derived From attribute. See Also: "Specifying the Primary Language for an Application" |
Example
Suppose you have a table that defines all primary colors. You could define a dynamic message for each color and then apply the LANG
function to the defined values in a query, for example:
SELECT HTMLDB_LANG.LANG(color) FROM my_colors
If you were running the application in German and RED
was a value for the color column in the my_colors
table. If you defined the German word for red, the previous example would return ROT
.
If you are building a multilingual application, it is important to understand how globalization codes affect the way in which your application runs. These codes are set automatically based on the application-level Globalization attributes you select.
NLS_LANGUAGE
and NLS_TERRITORY
determine the default presentation of number, dates, and currency.
Table 14-4 describes the globalization codes in Oracle Application Express.
Table 14-4 Oracle Application Express Globalization Codes
Language Name | Language Code | NLS_LANGUAGE | NLS_TERRITORY |
---|---|---|---|
Afrikaans |
|
ENGLISH |
SOUTH AFRICA |
Arabic |
|
ARABIC |
UNITED ARAB EMIRATES |
Arabic (Algeria) |
|
ARABIC |
ALGERIA |
Arabic (Bahrain) |
|
ARABIC |
BAHRAIN |
Arabic (Egypt) |
|
EGYPTIAN |
EGYPT |
Arabic (Iraq) |
|
ARABIC |
IRAQ |
Arabic (Jordan) |
|
ARABIC |
JORDAN |
Arabic (Kuwait) |
|
ARABIC |
KUWAIT |
Arabic (Lebanon |
|
ARABIC |
LEBANNON |
Arabic (Libya) |
|
ARABIC |
LIBYA |
Arabic (Morocco) |
|
ARABIC |
MOROCCO |
Arabic (Oman) |
|
ARABIC |
OMAN |
Arabic (Qatar) |
|
ARABIC |
QATAR |
Arabic (Saudi Arabia) |
|
ARABIC |
SAUDI ARABIA |
Arabic (Syria) |
|
ARABIC |
SYRIA |
Arabic (Tunisia) |
|
ARABIC |
TUNISIA |
Arabic (U.A.E.) |
|
ARABIC |
UNITED ARAB EMIRATES |
Arabic (YEMEN) |
|
ARABIC |
YEMEN |
Assamese |
|
ASSAMESE |
INDIA |
Basque |
|
FRENCH |
FRANCE |
Belarusian |
|
RUSSIAN |
RUSSIA |
Bengali |
|
BANGLA |
BANGLADESH |
Bulgarian |
|
BULGARIAN |
BULGARIA |
Catalan |
|
CATALAN |
CATALONIA |
Chinese |
|
SIMPLIFIED CHINESE |
CHINA |
Chinese (China) |
|
SIMPLIFIED CHINESE |
CHINA |
Chinese (Hong Kong SAR) |
|
TRADITIONAL CHINESE |
HONG KONG |
Chinese (Macau SAR) |
|
TRADITIONAL CHINESE |
HONG KONG |
Chinese (Singapore) |
|
SIMPLIFIED CHINESE |
SINGAPORE |
Chinese (Taiwan) |
|
TRADITIONAL CHINESE |
TAIWAN |
Croatian |
|
CROATIAN |
CROATIA |
Czech |
|
CZECH |
CZECH REPUBLIC |
Danish |
|
DANISH |
DENMARK |
Dutch (Belgium) |
|
DUTCH |
BELGIUM |
Dutch (Netherlands) |
|
DUTCH |
THE NETHERLANDS |
English |
|
AMERICAN |
AMERICA |
English (Australia) |
|
ENGLISH |
AUSTRALIA |
English (Belize) |
|
ENGLISH |
UNITED KINGDOM |
English (Canada) |
|
ENGLISH |
CANADA |
English (Ireland) |
|
ENGLISH |
IRELAND |
English (Jamaica) |
|
ENGLISH |
UNITED KINGDOM |
English (New Zealand) |
|
ENGLISH |
NEW ZEALAND |
English (Philippines) |
|
ENGLISH |
PHILIPPINES |
English (South Africa) |
|
ENGLISH |
SOUTH AFRICA |
English (Trinidad) |
|
ENGLISH |
UNITED KINGDOM |
English (United Kingdom) |
|
ENGLISH |
UNITED KINGDOM |
English (United States) |
|
AMERICAN |
AMERICA |
English (Zimbabwe) |
|
ENGLISH |
UNITED KINGDOM |
Estonian |
|
ESTONIAN |
ESTONIA |
Faeroese |
|
ENGLISH |
UNITED KINGDOM |
Farsi |
|
ENGLISH |
UNITED KINGDOM |
Finnish |
|
FINNISH |
FINLAND |
French (Belgium) |
|
FRENCH |
BELGIUM |
French (Canada) |
|
CANADIAN FRENCH |
CANADA |
French (France) |
|
FRENCH |
FRANCE |
French (Luxembourg) |
|
FRENCH |
LUXEMBOURG |
French (Monaco) |
|
FRENCH |
FRANCE |
French (Switzerland) |
|
FRANCH |
SWITZERLAND |
FYRO Macedonian |
|
MACEDONIAN |
FYR MACEDONIA |
Gaelic |
|
ENGLISH |
UNITED KINGDOM |
Galician |
|
SPANISH |
SPAIN |
German (Austria) |
|
GERMAN |
AUSTRIA |
German (Germany) |
|
GERMAN |
GERMANY |
German (Liechtenstein) |
|
GERMAN |
GERMANY |
German (Luxemgourg) |
|
GERMAN |
LUXEMBOURG |
German (Switzerland) |
|
GERMAN |
SWITZERLAND |
Greek |
|
GREEK |
GREECE |
Gujarati |
|
GUJARATI |
INDIA |
Hebrew |
|
HEBREW |
ISRAEL |
Hindi |
|
HINDI |
INDIA |
Hungarian |
|
HUNGARIAN |
HUNGARY |
Icelandic |
|
ICELANDIC |
ICELAND |
Indonesian |
|
INDONESIAN |
INDONESIA |
Italian (Italy) |
|
ITALIAN |
ITALY |
Italian (Switzerland) |
|
ITALIAN |
SWITZERLAND |
Japanese |
|
JAPANESE |
JAPAN |
Kannada |
|
KANNADA |
INDIA |
Kazakh |
|
CYRILLIC KAZAKH |
KAZAKHSTAN |
Konkani |
|
KOREAN |
KOREA |
Korean |
|
KOREAN |
KOREA |
Kyrgyz |
|
RUSSIAN |
RUSSIA |
Latvian |
|
LATVIAN |
LATVIA |
Lithuanian |
|
LITHUANIAN |
LITHUANIANA |
Malay (Malaysia) |
|
MALAY |
MALAYSIA |
Malayalam |
|
MALAYALAM |
INDIA |
Maltese |
|
ENGLISH |
UNITED KINGDOM |
Marathi |
|
ENGLISH |
INDIA |
Nepali (India) |
|
ENGLISH |
UNITED KINGDOM |
Norwegian (Bokmal) |
|
NORWEGIAN |
NORWAY |
Norwegian (Bokmal) |
|
NORWEGIAN |
NORWAY |
Norwegian (Nynorsk) |
|
NORWEGIAN |
NORWAY |
Oriya |
|
ORIYA |
INDIA |
Polish |
|
POLISH |
POLAND |
Portuguese (Brazil) |
|
BRAZILIAN PORTUGUESE |
BRAZIL |
Portuguese (Portugal) |
|
PORTUGUESE |
PORTUGAL |
Punjabi |
|
PUNJABI |
INDIA |
Romanian |
|
ROMANIAN |
ROMANIA |
Russian |
|
RUSSIAN |
RUSSIA |
Russian (Moldova) |
|
RUSSIAN |
RUSSIA |
Serbia |
|
CYRILLIC SERBIAN |
SERBIA AND MONTENEGRO |
Slovak |
|
SLOVAK |
SLOVAKIA |
Slovenian |
|
SLOVENIAN |
SLOVENIA |
Spanish (Argentina) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
Spanish (Bolivia) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
Spanish (Chile) |
|
LATIN AMERICAN SPANISH |
CHILE |
Spanish (Columbia) |
|
LATIN AMERICAN SPANISH |
COLUMBIA |
Spanish (Costa Rica) |
|
LATIN AMERICAN SPANISH |
COSTA RICA |
Spanish (Dominican Republic) |
|
LATIN AMERICAN SPANISH |
PUERTO RICO |
Spanish (Ecudor) |
|
LATIN AMERICAN SPANISH |
ECUDOR |
Spanish (El Salvador) |
|
LATIN AMERICAN SPANISH |
EL SALVADOR |
Spanish (Guatemala) |
|
LATIN AMERICAN SPANISH |
GUATEMALA |
Spanish (Honduras) |
|
LATIN AMERICAN SPANISH |
GUATEMALA |
Spanish (Mexico) |
|
MEXICAN SPANISH |
MEXICO |
Spanish (Nicaragua) |
|
LATIN AMERICAN SPANISH |
Nicaragua |
Spanish (Panama) |
|
LATIN AMERICAN SPANISH |
Panama |
Spanish (Paraguay) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
Spanish (Peru) |
|
LATIN AMERICAN SPANISH |
PERU |
Spanish (Peurto Rico) |
|
LATIN AMERICAN SPANISH |
PEURTO RICO |
Spanish (Traditional Sort) |
|
LATIN AMERICAN SPANISH |
SPAIN |
Spanish (United States) |
|
LATIN AMERICAN SPANISH |
AMERICAN |
Spanish (Uruguay) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
Spanish (Venezuela) |
|
LATIN AMERICAN SPANISH |
VENEZUELA |
Swedish |
|
SWEDISH |
SWEDEN |
Swedish |
|
SWEDISH |
FINLAND |
Tamil |
|
TAMIL |
INDIA |
Telugu |
|
TELUGU |
INDIA |
Thai |
|
THAI |
THAILAND |
Turkish |
|
TURKISH |
TURKEY |
Ukrainian |
|
UKRAINIAN |
UKRAINE |
Urdu |
|
ENGLISH |
UNITED KINGDOM |
Uzbek |
|
LATIN UZBEK |
UZBEKISTAN |
Vietnamese |
|
VIETNAMESE |
VIETNAM |
Zulu |
|
ENGLISH |
UNITED KINGDOM |