Community/Tizen.org-Translators

From Tizen Wiki
Jump to: navigation, search

Multilingual Site Details

There are many components to a multilingual site that will make the experience for users navigating in their respective language much better. The tizen.org sites must take into account these details and implement a strategy and policy that provides this best case experience. There are really two parts to translating a website for a multilingual experience:

  1. Interface Translations
    These include items such as menus, buttons, forms and other parts of the interface that assist the user in moving around the site.
  2. Content Translations
    These are the pages of content that provide the bulk of useful information for the user. These include documentation, blogs, events, and general page content.

Interface Translations

Onscreen Translation Process:

The onscreen translator will allow users with the "translator" role to translate interface strings while navigating in their respective language. The first step in doing onscreen translations is to switch to the language you are translating into. After you are viewing the site in that language, the onscreen translator will show up at the bottom of the screen and can be opened. The interface will show 3 separate boxes. It can sometimes be helpful to open up another browser tab to view the site in English, so you can more easily locate the strings.

  1. Text on the page
    • Browse or search for the string that needs translation. If the string has already been translated, it will display as highlighted green and you'll need to search for the translated version. If not, it will show up un-highlighted in English.
    • Select the string by clicking on it
  2. Source
    • Once the string has been selected it is then moved into the source box automatically
    • This box tells the user that they will be translating the correct string
  3. Translation into language
    • Proceed to translate the string into the users respective language
    • Click on the 'save the translation' button to instantaneously make these changes
    • 'Translation stored locally' will appear in the source box if the translation has been saved
    • Existing translations are cached, so revisions may not show up until cache has cleared on 1 hour intervals

Translate Interface Admin Area:

There are situations where it is difficult to find the string in the onscreen translator. Another option for those with the "translator" role is to use the Translate Interface Admin Area. This allows you to view strings and insert translations directly as well.

  1. Search for the string in English that you would like to translate
  2. Use the filters to reduce the number of strings returned
  3. Select the "edit" link to view the translations, edit them or add a new one (will display all languages for the string).
  4. Select "Save Translations" to save any changes

Import Interface Translation Process:

There is a specific process for translating the interface strings that allows us to leverage the Lingotek translation platform. This process is not automated yet and needs to be run on each site.

  1. Update strings
    Each text group should be updated so they are all accounted for.
  2. Export text groups
    Each text group that is being translated should be exported as a .po file. You only need to export a single language, normally the default "French". These files should be named in the following pattern: tizen-[site]-[text-group].po or an example from the main site would be: tizen-www-menu.po, or tizen-developer-menu.po.
  3. Update document in Lingotek
    Once you have the .po files for the different text groups, the documents in Lingotek can be updated to include any new strings added to that text group.
    • Select the document that you would like to update.
    • Select the "Update" option from the Actions drop-down menu.
    • Select the local file that you're updating the document with. Should be name exactly the same.
  4. Translate the new strings
    The document will go through the workflow quickly since most of the strings will have already been translated. Once it's in the Translate phase, you can select that link to translate in a particular language. The "Approve and Next" button should select the next untranslated string.
  5. Download the translations
    From the Actions drop-down, select the "Download" option and select the languages to download.
  6. Import .po files
    It is now time to import the correct .po file for each language into the correct text group in the site you're translating. Select the translated .po file, the language you're importing into, and the correct text group. Keep the "Mode" the same.

String Categories:

Do Translate:
  • Menu
    The menu text group contains the menu items that you see in the main navigation and sidebar. These are the items that are added to content to create the proper structure for the site. Although the content itself is translated differently and detailed in the "Content Translations" section below, the menu item associated with content is not included in this.
  • Views
    Views are the listings of content in various sections on the site. The strings associated with these listings are important for general navigation of the content listings. Views also provides the filtering capability in many cases.
  • Node types
    The strings in the Node types text group are for items associated with the content forms and display of content.
  • Fields
    The strings in the fields text group are for items associated with the content forms and associated with the node type text group. These are items such as labels or field descriptions.
  • Boxes
    There are some pieces of content on the home pages that can not be translated as normal content and need to be translated as if they were interface strings. This is where the Boxes text group comes in. Boxes are simple pieces of content that are limited in scope and primarily appear on the home pages.
  • Taxonomy
    Taxonomy is the categorization and tagging system for tizen.org. These are the terms and tags given to content by authors or set by an administrator. These strings often show up in forms that users fill out to put content into.
Don't Translate:
  • Built-in interface
    These are the strings and translations that come from Drupal and the contributed modules that are installed with Drupal. Most of the strings contained in this text group are located in administrative areas that a normal user visiting tizen.org would not see. These built-in interface strings can be translated for just the tizen.org site, or they can be translated "up-stream" in the Drupal community and pulled back into tizen.org. The up-stream translation management for these is [1](https://localize.drupal.org/translate)
  • Rules
    The Rules text group are the strings associated with emails generated to users or some on-screen notices when a form is submitted.
  • Countries
    These are the countries users can select on their profile page.
  • Metatag
  • Blocks

Content Translations

Issues 1:

Problem: There are times when the services connection between the Lintogek servers and tizen.org is not completed. When this happens the document is created in Lingotek fine, but the proper response from Lingotek never reaches tizen.org so the content appears to have not been synced.

How to spot: When a page is uploaded to Lingotek with the "Upload" button, the full round robin from Lingotek should update the page and display the "Download Translations" fieldset. This way you can see the phases in the workflow. When the connection is somehow interrupted and this fails, that fieldset will not be visible.

How to fix: When the above happens, it's important to delete the document in Lingotek and re-push the content. This will establish the proper values in both systems.

If page is "Pushed" twice to Lingotek, it will create a duplicate document on the Lingotek side. Please contact mshaver.

Content Translation Process

Translating a piece of content using the Lingotek Workbench.

Format Tags:

Translate a format tag using the Lingotek Workbench when a link is incorrect, out of place, or nonexistent within a string. There is a specific set of steps to perform this operation properly.

  1. Locate a format tag to translate within the users respective language
  2. Click on the 'Translations' tab
    • This is located underneath of the title next to the 'View Published' tab
  3. Select the language that the user would like to translate by clicking on the name
    • This will open up the Lingotek Workbench in a new web browsing tab
  4. Make sure the user is using the New Workbench
    • Go to the 'view' drop-down menu
    • If there is a blue dot next to 'New Workbench' then the user is on the correct version
    • If not, then select the 'New Workbench' option by clicking on it
  5. Use the language comparison boxes at the bottom of the page to locate the format tags
    • Click the format tag that the user would like to translate
  6. The string that was selected now appears in the Review Translations box
    • User can view the original text and current translation now
    • The format tag is shown in the original text but not the current translation
  7. Drag the blue arrows from the format tag in the original text around what the user wants to be the format tag in the current translation
    • When dragging the arrows a cursor will become your mouse, use this to place the format tags
  8. Click the green 'Save and Close' button
    • Now that the format tag has been placed in the Current Translation box it is time to save the string
  9. Go back to the 'Translations' tab on the Tizen website from step 2
  10. Click the check box next to the language that the user just translated the format tag into
  11. Now click the download button to update the revisions that were just made by the user
  12. Double check that the revisions downloaded correctly

Segments:

Translate a segment using the Lingotek Workbench when it needs a revision. There is a specific set of steps to perform this operation properly.

  1. Locate a segment to translate within the users respective language
  2. Click on the 'Translations' tab
    • This is located underneath of the title next to the 'View Published' tab
  3. Select the language that the user would like to translate by clicking on the name
    • This will open up the Lingotek Workbench in a new web browsing tab
  4. Make sure the user is using the Classic Workbench
    • Go to the 'view' drop-down menu
    • If there is a blue dot next to 'Classic Workbench' then the user is on the correct version
    • If not, then select the 'Classic Workbench' option by clicking on it
  5. In order to find a specific segment the user needs to open the Document Viewer tool
    • Go to the 'view' drop-down menu
    • Click on 'Document Viewer'
    • This will open up a new window where the user can select a specific segment
  6. Check the Source box
    • Make sure that the segment the user would like to translate is selected
  7. Switch back to the 'New Workbench'
    • Go to the 'view' drop-down menu
    • Select the 'New Workbench' option by clicking on it
  8. The string that was selected now appears in the Review Translations box
    • User can view the original text and current translation now
  9. Edit the translation in the Current Translation box
  10. Click the green 'Save and Close' button
    • Now that the segment has been revised in the Current Translation box it is time to save the string
  11. Go back to the 'Translations' tab on the Tizen website from step 2
  12. Click the check box next to the language that the user just translated the segment into
  13. Now click the download button to update the revisions that were just made by the user
  14. Double check that the revisions downloaded correctly