Skip to Content

8 steps and 2 tools is what it takes to translate texts of portal objects in SAP Enterprise Portal 6.0 on Web AS 6.40. The translation process is supported by two tools: Translation Worklist Coordination and Worklist Translation and here are the steps to make it happen

Step 1: The first tool to use is Translation Worklist Coordination. Here you can create a Worklist and add the content to be translated. The content can be included by selecting the objects in the portal Content Catalog, and via the context menu. Select the option: Add object to translation worklist.

image

Step 2: After including the content to be translated, you should generate the translation data, as shown in the picture below:

image

Step 3: At this point, you can exclude content you do not wish to translate as well as visualize all the objects that have been added to the list. At the bottom lower end of the Editor you will find a button “Release for translation”, please click on it. This enables you to begin the text translation in the next steps.

image

Step 4: Launch the Worklist Translation and look for the one you are willing to: translate, traducir, traduire, übersetzen,

image

Step 5: Now you are able to select among a list of numerous languages; pick the language target for your texts and load the desired worklist for translation.

image

Step 6: Translate the content. Here you have the option to click on the box at the bottom to save automatically once you have entered the text and clicked Next.

image

Step 7: In the top right corner you have a button: Set Worklist as translated. You should set the status of the Worklist to be able to release it for the end users.

image

Step 8: Going back to the initial tool Translation Worklist Coordination, select the Worklist and publish the translation.

image

That is all you need to do. Enjoy!

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. I wanted to see how the new translation options and workflow would look like. So that has anwered all my questions except:  Do you know if we will have something similar on SP2?
    (0) 
  2. I wanted to see how the new translation options and workflow would look like. So that has anwered all my questions except:  Do you know if we will have something similar on SP2?
    (0) 
  3. I wanted to see how the new translation options and workflow would look like. So that has anwered all my questions except:  Do you know if we will have something similar on SP2?
    (0) 
  4. Gaurav Gandhi
    I have tried this before also. But one thing i would like to know is that, while doing translation, for any object such as iView/page etc, we generally see two or more entries.
    Here should we translate all the entries or should we translate only one? I suppose some of the entires are for the description or the id that we generally enter?
    Kindly suggest!!
    (0) 
  5. Gaurav Gandhi
    I have tried this before also. But one thing i would like to know is that, while doing translation, for any object such as iView/page etc, we generally see two or more entries.
    Here should we translate all the entries or should we translate only one? I suppose some of the entires are for the description or the id that we generally enter?
    Kindly suggest!!
    (0) 
  6. Gaurav Gandhi
    I have tried this before also. But one thing i would like to know is that, while doing translation, for any object such as iView/page etc, we generally see two or more entries.
    Here should we translate all the entries or should we translate only one? I suppose some of the entires are for the description or the id that we generally enter?
    Kindly suggest!!
    (0) 

Leave a Reply