Table of Contents

1.Portal Content Translation 2.Creating Translation Worklist 3.Assigning Texts and Releasing Worklists 4.Generate the translation data 5.Release the worklist for translation 6.Searching for the Worklists and Uploading translations 7.Translating Texts 8.Publishing Translations

1. Portal Content Translation

This articel describes the process for translating Portal content by which we can achieve Internationalization. SAP Enterprise Portal provides a process for translating the texts. Multilingual object metadata for portal objects that is stored in the database of the Portal Content Directory (PCD). If a property of a portal object has type text attribute, it is marked as a text and can be translated (e.g. name, description). The translation process is supported by two tools that can be called from the content administration role. Choose Content Administration -> Portal Content Translation -> Translation Worklist Coordination or Worklist Translation. These tools are used to coordinate and to translate translation worklists. Process flow : The following graphic shows the flow of the translation process for portal objects. The blue process steps belong to "Translation Worklist Coordination", and the orange steps to "Worklist Translation". !!!!Insert Oicture of Processflow!!!!! At the end of the translation process, the "Publishing" step automatically writes the texts back to the objects to which they belong. The texts are written to the Portal Content Directory (PCD) or stored at the location of the corresponding PAR files.

2. Creating Translation Worklist

Prerequisites
To create a worklist, you need at least read/write permission for the Portal Catalog folder in which you want to create the object.

Procedure
In the delivered role for content administration, choose Content Administration -> Portal Content -> Translation Worklist Coordination. Place the cursor on a folder in the Portal Catalog and choose New -> Translation Worklist with the secondary mouse button. Under Step 1 "General Properties", enter the following:

Translation Worklist Name: Name of the worklist (required) Translation Worklist ID: ID of the worklist (required) Translation Worklist ID Prefix: You can enter an optional prefix for the worklist. We recommend that you use a namespace prefix and only include objects in the worklist if they have this prefix in their name. Master Language: Master language (required) Description: Description (optional)
Choose Next. In Step 2 "Summary", you can check the entries you made so far. Choose Finish.

If you donotwant the worklist to be opened immediately after the generation process for editing, deselect the option Open for editing when wizard completes.

Choose OK Now you can see the screen as below The wizard generates the new object and stores it in the indicated folder in the Portal Catalog. Depending on the options you selected in Step 6, your worklist is now available for editing.

3. AssigningTexts and Releasing Worklists

In this process you have to fill a worklist with text strings and you can then release it for translation.

Prerequisites
You have to be in the edit mode of the worklist.

Procedure
In the Portal Catalog, click on individual objects whose text parts you want to add to the worklist. With the secondary mouse button, choose Add <Object> to Translation Worklist. You can add a number of objects to a worklist at the same time. To do so, click on a folder in the Portal Catalog and choose Add all objects to translation worklist with the secondary mouse button. The worklist with the list of all added objects is displayed as below. The worklist itself is also part of the list. Select the necessary Objects from the list or you can select all of them by choosing select all. The following functions are available:

Remove

Removes objects from the worklist Displays the properties of individual objects that you added using the Property Editor.

Properties

Object Preview

Displays how iViews and pages will be displayed in the browser view of the portal

Sorts the objects in the object list Selects or deselects all objects contained in the object list
If you would like to include dependent objects when you generate the worklist (for example all objects that are in a role and their source objects), you must select the option Include all objects on which the translated objects depend. Dependent objects are not included in the default setting. If you want to include dependent objects, you can define a namespace filter so that only objects having a certain namespace prefix are added. If the worklist has a namespace prefix, it is automatically entered here.

4. Generate the translation data

You see a preview of the translation data. You can now exclude certain objects from the worklist by selecting and deleting them by the 'remove' objects option.

5. Release the worklist for translation

The status of the worklist is now "Released for translation". In this case you cannot add any more objects to the worklist. You can cancel the release. To do so, choose Cancel Release. You then return to Step 3 of this procedure. The worklist again has status "new". You can again add objects, generate the worklist, and then release it for translation.

Now after Releasing the worklist for translation you should see the status as in the below figure: Status of translation worklist is "Released for Translation". It is not possible to add new objects to the translation worklist

If you would like to add few more objects you can cancel the Release by clicking the button "Cancel Release". Then you can add few more objects to the worklist and again Generate the translation and Release Objects for Translation.

6. Searching for the Worklists and Uploading translations

Prerequisites
The administrator responsible for coordinating worklists created a worklist and released it for translation.

Procedure
Choose Content Administration > Portal Content Translation > Worklist Translation.

Find a worklist by entering an ID or with a generic search. The worklists found are listed.

When you select a worklist, the following statistical data is displayed:

Status, for example "Released for Translation" Last Changed By

Last Changed At Details about the translation statistics (how many strings in a worklist were already translated and how many were not

Define the source and target languages.

You can also define "Raw Texts" as the source and target languages. These are texts that have no language code. "Raw texts" can be used for example as source language when you translate "bad" English into "good" English.

Choose Load for Translation A list of all translated text strings is displayed, sorted in increasing order by number. You can now translate the texts.

7. TranslatingTexts
Prerequisites
The texts were uploaded for translation

Procedure
You see the list of texts to be translated. Sort the list by the number of the text string (increasing or decreasing), source and target language, status or object ID.

Select a text string whose status is "Not Translated". The text string is placed in an area below the list of texts to be translated. Enter the source text in the reserved area. With Copy Souce Text you can copy the source text directly into the area for the target language.

Process the entire worklist by translating one text string after another with Next and Previous.

Save the texts with the Save all pushbutton or save each text individually by clicking on Next or Previous. In the latter case, selectSave each time you choose Next/Previous.

A worklist need not be completely translated before it can be set to status "translated". A worklist can be set to "translated" at any time, even if only part of a worklist has been translated. Choose Content Administration -> Portal Content Translation -> Worklist Translation.

Find the worklist, select it, and choose Mark as "Translated". The status of the worklist is now "translated".

8. Publishing Translations
Publishing a translation means that the translated text strings are written back to the objects to which they belong (for example, the translated title of a role to the role object stored in the Portal Content Directory). If it is a PCD object, the text is written to the Portal Content Directory PCD). If it is a resource bundle, the text is stored in the deployment directory of the corresponding PAR file.

Prerequisites
The translation worklist was marked as ?translated" by the responsible translator.

Procedure
In the Portal Catalog, search for the worklist you want to publish and click on the corresponding object with the secondary mouse button. Choose Open -> Object.

In the list of worklist properties, check if the property Translation Worklist Status is set to "Translated".

Select all those Objects in the worklist which are to be published. Choose Publish Translation.

The texts will be now imported to the database.