Assigning Texts and Releasing Worklists 

Use

You have to fill a worklist with text strings. You can then release it for translation.

Prerequisites

You are in edit mode for a worklist.

Procedure

...

       1.      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. The worklist itself is also part of the list.

Note that the text parts of the content objects, and not the content objects themselves, are added to the worklist.

The following functions are available:

Remove	Removes objects from the worklist
Properties	Displays the properties of individual objects that you added using the Property Editor.
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

       2.      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.

Resource bundles are automatically included in a worklist if you add iViews and want to include dependent objects during generation. An iView or iView template always refers to a PAR file containing the executable code. When the worklist is generated, only the text parts of the PAR files are included. If you perform the generation without dependent objects, no resource bundles are included in the worklist.

       3.      Generate the translation data.

You see a preview of the translation data. You can now exclude certain objects from the worklist.

You can see if the worklist contains resource bundles using the special icon ().

       4.      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.

Result

You created a worklist that your translators can now translate. At the moment there is no built-in workflow, that is translators must be informed in the usual manner (for example with e-mail).