birt barcode maximo Setup instructions for the locale module in Font

Encode QR Code in Font Setup instructions for the locale module

To set up the locale module, follow these steps: 1. 2. Enable the locale module at Modules. Upload the language translation folder to the root Drupal folder (Figure 6-25). All translation files now live in the Drupal directory.

Figure 6-25. Upload the language translation folder to the root Drupal folder. 3. 4. Navigate to Configuration Languages, and select Add language. Select the predefined language from the drop-down list, and click Add language (Figure 626). Drupal will automatically import language translation files into the system if they were correctly uploaded.

Figure 6-26. Select the predefined language from the drop-down list, and click Add language. 5. Configure how languages will be detected and displayed (Figure 6-27). Should languages display differently depending on URL, the user s selection, or another You need to select at least one check box from DETECTION METHOD and click the ENABLED checkbox. Make sure the configure it after saving if applicable!

Figure 6-27. Navigate to Configuration Languages and select DETECTION AND SELECTION to configure how languages will be detected and displayed. NOTE: Configuration, Languages, and DETECTION AND SELECTION should be screen text style.

Navigate to Configuration Translation interface to see how many strings were translated (Figure 6-28).

Figure 6-28. Navigate to Configuration Translation interface to see how many strings were translated. 7. Click the TRANSLATE tab, and search in the results by Only untranslated strings to see all untranslated strings. Click edit to quickly update a string. In Figure 6-29, the string An AJAX HTTP error occurred does not have a Ukrainian translation.

Figure 6-29. Click the TRANSLATE tab, and search in the results by Only untranslated strings to see all untranslated strings. The string An AJAX HTTP error occurred does not have a Ukrainian translation.

If there are a number of strings that require translation, it is easier to download the language translation file and edit it with a gettext translation editor such as poedit (http://poedit.net). Click the EXPORT tab, and select the translation to export under EXPORT TRANSLATION (Figure 6-30).

Figure 6-30. Click the EXPORT tab and select the translation to export under EXPORT TRANSLATION to edit the translation file. Navigate to Structure Blocks, and place the language switcher (interface) block in the appropriate region. This block allows a user to switch between the different language translations via links.

As previously mentioned, the translation module provides a UI to translate a node into other languages. To set up the content translation module, follow these steps: 1. 2. 3. Enable the content translation module at Modules. Navigate to Structure Content types, and edit the content type that requires translation. Select Publishing options, and select Enabled under Multilingual support to allow one translation per node (that is, a node can exist only as English or Ukrainian) or Enabled, with translation for multiple translations (which allows both English and Ukrainian per node), as shown in Figure 6-31. This is set to Disabled by default.

Figure 6-31. Edit the content type that requires translation. After Multilingual support is enabled, a Language drop-down will appear with all installed languages on the create content form, as shown in Figure 6-32. Note that a Language neutral node cannot have multiple translations.

Figure 6-32. After Multilingual support is enabled, a Language drop-down will appear with all installed languages on the create content form. If Enabled, with translation was selected in the previous step 3, a TRANSLATE tab now appears when viewing a node. To translate a node to another language, click the TRANSLATE tab and add translation for the required node (Figure 6-33).

Figure 6-33. To translate a node to another language, click the TRANSLATE tab when viewing a node and add translation. After a translation has been created, you can now check whether the node requires updated or not. When editing a translated node (that is, not the source node, with the original language) and the translation is not complete, select This translation needs to be updated in the translation settings (Figure 6-34).

Figure 6-34. After a translation has been created, you can now check whether the node requires updating. When updating a source node, you can select Flag translations as outdated if translated nodes should be flagged as requiring an update (Figure 6-35).

Figure 6-35. When updating a source node, you can select Flag translations as outdated if translated nodes should be flagged as requiring an update. The local and translation module both add options to the Content list screen. Navigate to the Content list screen and filter results by Status Outdated translation to view all outdated content (Figure 6-36).

Figure 6-36. Navigate to the Content list screen and filter results by Status Outdated translation to view all outdated content.