Enabling/Disabling Support for Multiple Language Content

1. Open siteroot\web.config.
2. Set the value of ek_EnableMultilingual to 1.

   NOTE: To disable, set the value to zero (0).

3. Save web.config.

Determining Which Languages are Available

Prerequisite

Only members of the Administrator Group or those assigned to the XLIFF-Admin role can view, add, or edit language settings. See Also: Using the Roles Screens .

A locale consists of a language and a region. For example, English (United States) describes the variation of English used in the United States, as opposed to English (English U.K.) used in the United Kingdom.

Each locale's identifier consists of a language code and region code.

• fr-FR = Language:French + Region:France
• pt-BR = Language:Portuguese + Region:Brazil
• es_419-AR = Language:Latin American Spanish + Region Argentina

You can create a new locale, if needed.

Setting the Default Language

When you install Ektron, the default language is US-English (1033). The default language determines which edition of content is displayed if a site visitor does not select a language, or a visitor selects a language other than the default and navigates to page for which content does not exist in the selected language. In that case, Ektron looks for the selected language's Fallback Locales. For more information, see Setting the Fallback Locale. If content is not available in any of its Fallback locales, Ektron displays that content in the default language (if available).

IMPORTANT: You must enable a language before setting it as the default. See Also: Determining Which Languages are Available

To change the default language for your multi-language website:

1. Open yourwebsite\web.config.
2. Set the value of ek_DefaultContentLanguage to the locale id of the default language. For example, 1031 for German. For a list of locale ids, see Ektron Workarea > Settings > Localization > Languages and Regions.
3. Save web.config.

Viewing Your Site in Another Language

When a site visitor selects a language then navigates to a page on your site, Ektron uses the following criteria to determine which language edition of content to display.

1. Display content in the selected language, if available.
2. If that edition is not available, check the language's Fallback Locale. If it is set and content is available in that language, display that. See Also: Setting the Fallback Locale
3. If content is not available in the Fallback Locale, display it in the default language. See Also: Setting the Default Language
4. If no editions are available, display nothing.

To let site visitors to view your site in any enabled language, your developer places a LanguageSelect server control on any template. See Also: LanguageSelect

You can also indicate a language-edition by adding a language parameter to a quicklinka special kind of hyperlink that jumps to another content item on your Web site. (A regular hyperlink jumps to a Web page on the internet.). For example, products.aspx?LangType=1033 displays the English (US) edition of the products.aspx content. This syntax automatically sets the language cookie.

NOTE: For a list of the decimal value of each supported language, see Ektron Workarea > Settings > Localization > Languages and Regions.

Creating an external link to a page of foreign content

If another website links to a multi-lingual page on your site, the URL must include the language ID parameter. For example:

www.ektron.com/web-content-management-solutions.aspx?LangType=1036

Creating Multi-language Content

Prerequisite

You have permission to add content to the folder.

1. Navigate to the content folder in which you want to create the content.
2. Choose View > Language and select the language in which you want to create the content. If the desired language is not available, see Determining Which Languages are Available.

   You can also view all content in a folder, regardless of language. This menu makes it easy to find content in a selected language.

   —Image—

   

   The View Contents of Folder screen displays the language of each content item.

   —Image—

   

3. Click Add Content () and create the content as you would any content. See Also: Creating New Content
4. When applying metadata, you can only use metadata definitions created for the selected language. See Also: Working with Metadata

You can set up a separate approval chainA series of users or user groups who must approve content before it can be published. for each edition of a content, and can create collectionA list of Ektron content links for display on a Web page.s, menus, taxonomy categories, and tasks in any supported language.

NOTE: Alternatively, you can designate certain sections of text within a content item to be included or excluded from certain languages. See Also: Creating One or More Localized Paragraphs

Modifying Page Content Based on Language Selection

If a template’s text should change according to a user’s language selection, use a case statement to provide the language-specific content. Assume you want to create editions of the menu that runs under the header in 3 languages: English, French, and German:

NOTE: This procedure uses the header.asp file delivered with the RC International sample site as an example.

1. In the template file, declare each menu option a variable. For example:

   Dim t_search, t_products, t_support, t_news, t_careers, 
     t_calendar, t_home, t_login, t_site_lang, t_contact, 
     t_copyright, calendar_id

2. Enter case statements that provide the value of each variable in each language. (1031—German; 1036—French.) The following case statement is for the search menu option.

   Select 
     Case ContentLanguage 
     Case "1031" t_search = "Suche" 
     Case "1036" t_search = “Recherche" 
     Case else t_search = "Search" End Select

When a user visits a page controlled by this template and selects French or German as the site language, the page is refreshed and the translated values appear on the template.

Modifying Images Based on Language Selection

Many Web page templates also include images that require translation. To set up templates to invoke images in the user-selected language:

1. Add to the library each image that should change when the language changes. For example, if your company’s tag line is translated into 3 languages, upload the 3 images into the library.
2. You should include the language in the title of the image. For example, tagline_English, tagline_French.
3. Create a separate content block for each language-specific image. Each content block must have a unique ID number.
4. Insert the appropriate image into a content block for each language. For example, insert the tagline_English image into the English content block.
5. Insert the content blocks into the appropriate templates. For example, insert the English content block into the English template.

Creating a New Locale

1. Go to Workarea > Settings > Localization > Languages and Regions.
2. Click Add (). The Edit Language Details screen appears. A partial image is shown in the following image.
   —Image—

   

• Language—can display the major languages in every country (via the Show All radio button), or the most common world languages (use the Common radio button). If you are unsure about which languages are used in a country, move to the Region field, select a country, and click the Recommended radio button. Then, go back to the Languages field; you will see all languages spoken in the selected country by percentage.
• Region—provides several options for finding the new locale's region or country.
  • If you selected a language above, you can select from a list of countries that use the language. To do that, click Recommended and scroll below the list of multinational regions. Click the country of the locale you are defining.
  • To select from an alphabetical list of all countries, click Show All and scroll below the list of multinational regions.
  • If the language's locale is not tied to a specific country but is connected to a region, select the region from the regions list.
• Locale—assign a locale ID to the new language. The locale ID must be unique, but is free-form, so you can customize it. It could be based on a target market, for example, “youth” for English US young adults (for example, youth-US), or “euro” for English in Europe (euro-UK), or even “klingon” (klingon-US). If you select a language, the field is filled in for you. Typically, the suggested value is adequate.
• Fallback Locale—For every language, you can set a Fallback Locale, a language in which content appears if it is not available in the selected language. If content is not available in the fallback locale, Ektron looks for content in the fallback locale's Fallback Locale. If content in that language is not found, Ektron looks for up to 4 additional fallback locales. At that point, if content is still not found, Ektron tries to display the content in the default language.

  For example, your website's default language is US English. You have some content in Swiss German (de-CH). The fallback language for that is Austrian German (de-AT), and the fallback language for Austrian German is German (de-DE). If the content on a page is not available in Swiss German, Ektron tries to find an Austrian German edition. If it cannot find that, it looks for a German edition. If that is not available, it tries to display an English edition. See also Setting the Fallback Locale.

  In certain situations, you may want no fallback locale. That is, you want to display nothing if content is not available in the selected language. To accommodate this, None is an option in the Fallback Locale drop-down list.

  NOTE: If you set None as the Fallback Locale for any language, and content is not available in the selected language, nothing appears on the page and no other languages are checked.

• Language Tag—assign a language code to the language. This section of the screen contains important information about this field.

  IMPORTANT: Unlike the Locale field, the Language Tag field must conform to the IETF BCP 47 (Best Current Practice).

• Alphabet—Some languages can be written in more than one alphabet. For example, Serbian can be written using the Latin or Cyrillic alphabet.
• Custom Ext.—choose between 2 strategies when exporting content for translation: machine translation and pseudolocalization.
  mt (machine translation)

  Using a MachineTranslation Strategy

  When you export content for translation and apply the MachineTranslation strategy, Ektron translates the content using machine translation then immediately imports it. See Also: Using Machine Translation

  The following is an example of how to implement the strategy. See Also: Extending CMS Behavior

  <objectFactory> 
    <objectStrategies> 
      <add name="MachineTranslation"> 
      <strategies> 
        <add name="MachineTranslationStrategyTemplate" 
          type="Cms.Extensions.Templates
            .MachineTranslationStrategyTemplate, 
            Cms.Extensions.Templates"/>
      </strategies> 
      </add> 
    </objectStrategies> 
    <objectImplementations> </objectImplementations>
  </objectFactory>

  pseudo (pseudoLocalization)

  Using a PseudoLocalization Strategy

  NOTE: For background information, see Pseudolocalization (Wikipedia).

  When you export content for translation and apply the PseudoLocalization strategy, Ektron converts the content to pseudo-language text and the immediately imports it..

  The following is an example of how to implement the strategy. See Also: Extending CMS Behavior

  <objectFactory> 
    <objectStrategies> 
      <add name="PseudoLocalization"> 
      <strategies> 
        <add name="PseudoLocalizationStrategyTemplate" 
          type="Cms.Extensions.Templates
            .PseudoLocalizationStrategyTemplate,
            Cms.Extensions.Templates"/> 
        </strategies> 
        </add> 
      </objectStrategies> 
      <objectImplementations> </objectImplementations> 
  </objectFactory>

  Here is an example of how to override the PseudoLocalize method.

  public override void 
    PseudoLocalize(ref string content, PseudoLocalizationEventArgs 
    eventArgs)

  Here are the PseudoLocalizationEventArgs properties.

  LocaleData 
  Locale 
  LocalizableCmsObjectType 
  ObjectType 
  long 
  ObjectId

  Developers use the PseudoLocalize property to write custom code that programmatically starts the export process. Here is an example: Ektron.Cms.Localization.LocalizationExportJob.PseudoLocalize = true;

  Ektron applies the PseudoLocalization strategy if either of the following conditions is met:

  • The target locale’s language tag contains x-pseudo.
  • The export job’s PseudoLocalize property is true.

  Applying PseudoLocalization strategy to a locale

  Applying PseudoLocalization Strategy to a Locale

  You can apply PseudoLocalization Strategy to a locale's language tag in the Workarea. Use the Settings > Localization > Languages and Regions screen's Custom EXT field, as illustrated in the following figure. Programmatically, LocaleData.XmlLang contains x-pseudo.

  —Image—

  

  Overriding the Translate method

  Overriding the Translate Method

  Here is an example of overriding the Translate method.

  public override void 
    Translate(ref string content, MachineTranslationEventArgs 
    eventArgs)

  The MachineTranslationEventArgs have intellisense, but the following is a list of its properties.

  LocaleData SourceLocale
  LocaleData TargetLocale
  LocalizableCmsObjectType ObjectType
  long ObjectId

  Ektron applies the Machine Translation strategy if either of the following conditions is met.

  • The target locale’s language tag contains x-mt
  • The export job’s MachineTranslate property is true

  Developers use the MachineTranslate property to write custom code that programmatically starts the export process. Here is an example: Ektron.Cms.Localization.LocalizationExportJob.MachineTranslate = true;

  Applying machine translation strategy to a locale

  Applying Machine Translation Strategy to a Locale

  You can apply Machine Translation Strategy to a locale's language tag in the Workarea. Use the Settings > Localization > Languages and Regions screen's Custom EXTfield. Programmatically,LocaleData.XmlLang contains x-mt.

• ASP.NET Culture—specifies the region for formatting dates, times, currencies, and so on. This value is assigned to the ASP.NET Culture property. See Also: How to: Set the Culture and UI Culture for ASP.NET Web Page Globalization.

  For instructions on setting a custom culture, see the following Ektron Knowledge Base article: HOW TO: Using Locale Builder to create custom locales

• ASP.NET UICulture—specifies the natural language of resource strings. This value is assigned to the ASP.NET UICulture property. See Also: How to: Set the Culture and UI Culture for ASP.NET Web Page Globalization
• Flag Icon—used in the Workarea as a quick, visual indicator of the locale, it is important for each locale to have a unique flag. Flag files must be 16x16 pixel .gif images. Ektron provides several flags, which are installed to the /siteroot/WorkArea/images/application/flags/ folder. Any flags with elements in common with the locale's language and region appear as choices. If there is no flag next to the locale you are creating (for example fr-017, French in Africa), you can create an image, assign that name to it, and place it in the designated folder. Then return to this screen, select the locale, and select the image.
• Native Name—the name of the locale in its native natural language. That is, what the people in that locale call their own language and region.
• English Name—the name of the locale in English.

Setting the Fallback Locale

1. Go to Workarea >Settings > Localization > Languages and Regions.
2. Click Edit ().
3. Click Rename or Change Fallback Locale () for the language of interest.
4. Use the pulldown in that language's Fallback Loc column to select a fallback locale.
   —Image—

   

   NOTE: If you set a language's Fallback Locale to None and the language is part of a fallback chain, if content is not available in that language, the chain terminates there.

5. Click Save () in the row of the language you are changing.

Translating Content Manually

Use this procedure to initialize new foreign language content with content from a source language, then translate the content manually. The copying should facilitate the translation. For example, an editor translates content from French to German. The editor copies the French edition to new content whose language is German. As the editor translates the French edition into German, the French content is deleted. Any images in the content usually would remain, and all formatting (tables, bullets, and so on) is retained.

1. Go to the View Contents of Folder screen for the content you want to translate. Its status must allow editing (it cannot be submitted or pending).
2. Choose View >Language and select an original language.
3. Click the content you want to translate. It appears on the View Content screen.
4. Use the Add drop-down list in the upper right corner to select a language into which you want to translate the content. The original language content appears.
   —Image—

   

5. Translate into the new language then delete the original content. At this point, you can click Translate Content () to have the software translate the content. You can then edit as needed to perfect the translation. When done, click the Paste Content button.

   NOTE: You cannot translate XML Smart Forms using the Translate Content () button.

6. Translate the Title and Summary.
7. To add metadata to content, metadata specifications must have been created for the selected language. See Also: Working with Metadata
8. When you save the content, it is saved as the edition of that content in the selected language.

Using Machine Translation

Ektron includes a machine translation feature, which is powered by the Google Translation Service. To see a list of supported languages, go to http://translate.google.com/.

NOTE: Machine translation is not supported for all languages in the Language Settings screen. Also, you cannot translate XML Smart Forms using this method.

Like most software-based translation, someone fluent in the new language should verify that the translation is appropriate within the context of the page.

The machine translation feature lets you choose a glossary (that is, a field, industry, or subject area). This helps the software find the best translation for a term or phrase in that field.

Follow these steps to use the machine translation feature.

Prerequisite

Your Ektron administrator has enabled the feature. See Also: Enabling Machine Translation

1. In the Workarea, open the folder that contains content to be translated.
2. Choose View > Language and select an original language (that is, the language from which it will be translated).
3. Click the content you want to translate. Its status must allow editing (that is, its status cannot be submitted or pending). It appears on the View Content screen.
4. Use the Add drop-down list in the upper right corner to select a new language for the content.

   NOTE: If you do not see the language on the drop-down, you need to enable the language. See Also: Determining Which Languages are Available

   —Image—

   

5. The original language content appears.
6. Edit the title if appropriate.
7. Click Translate Content (). The Translation screen appears.
   —Image—

   

8. Select the source (old) and target (new) languages.
9. If the content should refer to a specific glossary, select one from the drop-down list.
10. Click Translate. The translation appears.
11. If the translation looks OK, click Paste Content. The translated content replaces the original content in the editor. Modify as needed.
12. Translate the Title and Summary.
13. To add metadata to the content, metadata specifications must have been created for the selected language. See Also: Working with Metadata
14. When you save, the content is saved as the selected language edition of the content.

NOTE: When the View Contents of Folders screen reappears, it is probably set to the source language. In this case, you do not see the new content in the target language. To see it, click View > Language and select All or the target language.

Exporting Content to XLIFF

You can copy content into XLIFFXML Localization Interchange File Format; for exchanging localization data. files that you can submit to a translation agency, or translate the content "in house." When the translation is complete, you import translated content to Ektron.

You can translate these kinds of Ektron information.

• content, including summary, comments, and metadata
• a portion of a content (see Creating One or More Localized Paragraphs)
• forms, including response message, comments, and metadata
• all menus (you cannot choose individual menus)
• assetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s (You cannot export. zip files.)
• taxonomya content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure. data

Ektron supports versions 1.0, 1.1, and 1.2 of the XLIFF standard. You specify the version you are exporting in the web.config file, using the ek_XliffVersion element. Any listed version can be imported.

Creating a Multi-language Translation Package

Use the Multi-language Translation Package to create and control groups of content that require translation. Translation packages contain any type of content managed by Ektron including

• HTML
• XML Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input.s
• assetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s like Microsoft Word documents, PDFs
• images. Images (.gif, .png, .jpg and so on) are also managed with their associated source documents like Photoshop (.psd) files.

For ease of use, you may add content and folders to one or more Translation Packages.

After creating a Translation Package, you use the Export for Translation screen's Select Packages field to export the content for translation. See Also: Exporting Content to XLIFF

Only content that’s selected for that package and marked “Ready for Translation” is exported. See Also: Marking Translation Statuses

Prerequisite

You must be a member of the Administrators group or be assigned to the XLIFF Admin role. See Also: Defining Roles

A resource file is not human-readable. To make it so, use Microsoft’s resgen utility, then translate the human-readable, .txt version of the file. The following example shows a portion of it.

add menu title=Add Menu
lbl ad serverip=Domain Controller IP
alt: remove collection items text=Click here to remove items 
	from this collection

Each string has the following components:

• English description—includes information about where the text appears. For example, btn text appears on a button.
• an equal sign (=)
• English text—The text displayed on the screen, for example, a button label, menu item, or mouse-over text.

For each string, translate the text to the right of the equal sign. Then, run the resgen utility on the .txt file again, indicating the translate-to language. This converts the file back to a machine-readable format. Finally, move that file to the appropriate language folder under workarea/images, and enable the new language in the Workarea.

Prerequisites

• The alphabetical, 4-character identifier of the country/language into which you are translating. See CultureInfo Class from the MSDN website.
• The server that hosts Ektron must have Visual Studio.NET.

1. Copy the resgen.exe utility from C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bin\NETFX 4.0 Tools to the your-web-site\Workarea\resources folder.

   In Visual Studio 2008, the resgen.exe utility is typically located in the <SDK dir>\bin directory, located via HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows.

2. Go to Windows Start button > Microsoft Visual Studio 2010 > Visual Studio Tools > Visual Studio Command Prompt to open a command window.
3. In the command window, change the directory to the your-web-site\Workarea\resources folder. For example, cd C:\Inetpub\wwwroot\CMS400Min\Workarea\resources.
4. Insert the following text: resgen EKResource.en-US.resources anyfilename.txt
   You can assign any name to the .txt file. A .txt file of resource strings converted to a human-readable format is created in the resources directory.
5. Open the .txt file.
6. Replace all single backslashes (\) with a double backslash (\\).
7. Translate the text following every equal sign (=). Be careful not to change any occurrences of n surrounded by double backslashes (\\n\\).
8. Save and close the .txt file.
9. Open the command window (as described in Step 2) and insert the following:

   resgen anyfilename.txt EKResource.two-character country 
     code-two-character language code.resources. 

   Replace anyfilename.txt with the file you named in Step 4. In this example, the .txt file is named span_translation.txt. For example, to indicate that the Workarea is being translated into the Spanish/Spain, enter resgen.exe span_translation.txt EKResource.es-ES.resources.
   When the conversion is complete, Writing Resource File ...Done appears in the command window.

10. The Workarea\resources folder includes several resource files. If one exists for the translate-to language, it is overwritten. If one does not exist, it is created. To follow our example, the EkResource.es-ES.resources file was updated with your changes.
11. **Your website's Workarea\images folder contains text images that need translation. If the country/language into which you are translating has subfolder within Workarea\images, inspect its images to see if they need translation. If the country/language into which you are translating does not have a subfolder within Workarea\images:
    1. Create a new folder whose name is the language code into which you are translating.
    2. Copy the files in the Workarea\images\en folder.
    3. Paste those files to the folder you created in Step 10a.
    4. Review the files in the folder you created in Step 10a. Translate text as needed.
12. Enable the new language in the Language Settings screen. See Determining Which Languages are Available
13. Make the new language the default language in the Configuration Setup screen. See Getting Started with Ektron.

Ektron provides the following standard dictionaries.

• uk-UA—Afrikaans
• ar-AR—Arabic
• bg-BG—Bulgarian
• cs-CZ—Czech
• da-DK—Danish
• de-CH—German (Switzerland)]
• de-DE—German
• en-GB—English (Great Britain)
• en-US—English (United States)
• es-ES—Spanish
• fr-FR—French
• he-IL—Hebrew
• it-IT—Italian
• nl-NL—Dutch
• nn-NO—Norwegian (Nynorsk)
• pl-PL—Polish
• pt-PT—Portuguese
• pt-BR—Portuguese (Brazil)
• ru-RU—Russian
• sl-SL—Slovenian
• sv-SE—Swedish
• uk-UA—Ukrainian

If Ektron does not have a dictionary that matches the content language, it proceeds through these steps in the following order:

1. If the language begins with en (for example, en-AU), use the en-GB dictionary.

   If it begins with zh, use zh-CHS.

2. Each language has a default version, indicated by letters before the dash matching the ones after the dash. For example fr-FR. If the default version’s dictionary is available, use it.
3. Use the first dictionary (alphabetically) that begins with the content language. For example, the content language is es-AR, but its dictionary does not exist. The first dictionary alphabetically beginning with es that is available is es-CO, so use that.
4. If none of the above is available, use en-US.

Editing eWebEdit400’s Standard Dictionaries

The following topics explain how to access a screen for working with standard dictionaries, and how to update, edit, replace, and delete individual words as well as entire dictionaries. You cannot edit a word. Instead, delete a word then add the corrected version.

Editing eWebEdit400’s Custom Dictionary

A language’s custom dictionary is created the first time a user uses the Add to Dictionary option while spell checking content in that language. From then on, the dictionary is updated when anyone using that server edits content in that language and uses the Add to Dictionary option. The name of the custom dictionary is formed using:

• the language code of the content
• a dash (-)
• the word custom
• the file extension .txt

So, if the content is French, the file’s name isfr-fr-custom.txt. The file is saved to the root/Workarea/Foundation/RadControls/Spell/TDF folder.

You can edit the custom dictionary manually using an application that updates .txt files, such as Notepad.

The following list explains the fields at the top of the screen. After you enter the selection criteria, click Filter Results to apply the new selections.

IMPORTANT: These criteria have an AND relationship. This means that, if you select several criteria, only content that satisfies all appears in the lower section of the screen.

• Lang/Dialect—Select the language whose content you want to view. To ignore this field, choose NULL. Alternatively, you can select all content not in the selected language. To do that, check the Does not Include box.
• Trans Status—Select the translation status of content you want to view. To disregard this criterion, choose (Any). See Also: Marking Translation Statuses
• Date Created—If desired, enter a range of content creation dates. If you do, only content created within those dates appears below.
• Last Modified—If desired, enter a range of content modification dates. If you do, only content edited within those dates appears below.
• ContentID—To see a particular content item, enter its ID number.
• Folder—If desired, select a folder whose content you want to view.
• Author—If desired, select the person who last edited the content you want to view.
• Title—If you know one or more words in the title of content that you want to view, enter them. You may enter one partial word and find all content whose title includes it.

Viewing Content on the Localization Dashboard

When you open the Localization Dashboard, the lower section displays all content in the Default Application Language.

NOTE: The pagination of the content list is controlled by the <add key="ek_PageSize"> element of your siteroot/web.config file.

On the lower section, you can:

• sort by any column in ascending or descending order by clicking on the column header
• view and work with any content item by clicking it, if you have permission to do so See Also: Managing Folder and Content Permissions
• print current results by clicking Print
• export current results to a Microsoft Excel spreadsheet by clicking Create Report
• edit the selected content's export languages
• change the content's Translation Status
• estimate the word count for one or more pieces of content