Editor Manual

Once a user has finished editing a page in one of the project’s languages and released it, e.g. the Jobs page in German, they now want to submit it to the translation workflow from German into another language, for example French.

To do so, the user selects the respective page and starts the Translate this page workflow on this element. This workflow opens a window asking for further translation settings.

You may decide whether a preview page should be generated or not. A preview page might help the translator by providing relevant context information.

Finally, the user might decide whether the entire page should be translated or only particular sections or maybe only the page form. The Translate Page Form option defines whether the page data itself should be translated or not. The page data can contain texts relevant for translation (e.g. the name of the page or meta informations).

The Translate All Sections option defines whether to translate all sections of the given page or to limit translations to certain sections which will appear if the respective option has been chosen. A list of all translatable sections will be shown from which the user may select those they wish to be translated.

Figure 2. Register Page Settings

This workflow allows you to submit all pages within the a folder to the same translation workflow at once.

Importantly, you can decide to submit only include the pages of the selected folder or to also include all pages in any subfolder.

Figure 3. Registering Pages in a Page Folder

A particular or a list of datasets might be submitted to a translation workflow as well.

If a particular dataset is to be translated, simply select the respective dataset and start the Translate this dataset workflow. The workflow will allow you to add other datasets from this datasource as well.

Figure 4. Registering a Dataset

Additional workflows are available which allow you to select any page, folder or dataset without the need to actively visiting the page (ContentCreator) or selecting it (SiteArchitect).

The workflows are similar to those described above and need no further disucussion.

First of all, you have do define the source and target language. Although your project may contain several languages, you can only choose from a certain list of combinations.

The list of available choices is provided by your administrator (or any user who has the required permissions) and depend on the particular project.

Each workflow requires the user to choose one translation language combination.

Figure 5. Form element used to select a language mapping

If you want to pre-assign a choice to particular folders, you may select the respective folder in SiteArchitect, navigate to its metadata tab and select a language combination.

This choice will be chosen by default whenever a translation workflow is being executed on the folder or any of its content elements.

Of course, you may change the default choice at any time simply by choosing a different one.

Second, TranslationStudio distinguishes between urgent and regular translations.

Figure 6. Translation Type

Urgent translations will be processed immediately and will usually be transferred to a Translation Memory System fast.

Regular translations will be added to a translation queue and transferred to a Translation Memory System if certain criteria are met, e.g. a minimum number of pages to be translated. These criteria are configured for each project associated to a language combination.

Third, TranslationStudio allows a user to choose a workflow to be executed once the pages, sections or datasets affected by the translation request workflow have been imported again after a successful translation.

This setting is optional. Crucially, the respective workflow’s first activity must not be started automatically but requires a manual transition triggered by user input.

Figure 7. Workflow to be executed

Please verify that the permission settings allow for the respective workflow to be executed on the given elements.

The workflow will not be executed by the user submitting a page etc. for translation but by the (technical) TranslationStudio user configured using the ServerManager.

Fourth, you may want to provide a particular date this translation should be completed.

Importantly, there is no guarantee that the translation is completed in time; it is just a means of indicating potential urgency.

Figure 8. Completion Date

Finally, TranslationStudio will only translate translatable (text) data and ignore other non-translatable components such as checkboxes etc.

In some cases, however, you may wish to also update those non-translatable input fields as well. Some workflows will provide an option to do exactly this.

If chosen, TranslationStudio will copy the non-translatable fields of a page or section from the source into the target language right before the translation is merged.

Figure 9. Copying non-translatable input field

TranslationStudio allows you to decide which page and/or section forms are to be excluded from translation requests. To do so, TranslationStudio offers two options.

Both options are available in the element’s metadata:

Figure 10. Excluding content from translation

Logically, if no restriction is specified, a page/section will be processed in a translation request.

In general, TranslationStudio distinguishes between the following states:

With more pages being translated, it simply gets more difficult to monitor the translation status of each page. TranslationStudio offers various means to keep track of the translation progress.

Detailed email notifications are sent to inform a user about a status change. This feature requires an email address set for each FirstSpirit user working with TranslationStudio.

If you edit a page using ContentCreator, you may notice a small box on the lower left corner.

This icon provides you with general translation status information for the entire page.

Figure 14. TranslationStudio Status Icon

Importantly, this info box does not differentiate between sections and pages. As long as there is information available for at least a page or a single section, this box will appear.

If you want more detailed information, a report component allows for a more advanced feedback option.

Figure 15. TranslationStudio Report Component

You may limit the search criteria to source or target language or translation states to narrow down search criteria. You may also provide a page or section id to search for very specific information.

Each search result entry will allow you to open a more detailed dialog. This dialog will have either a link (ContentCreator) or a button (SiteArchitect) to allow you to jump to the respective page or section directly.

If enabled, TranslationStudio allows you to monitor general application statistics such as

To access the dashboard, simply open your browser and navigate to the FirstSpirit server and open the dashboard, e.g. https://my-firstspirit-server:8000/translationstudio/dashboard

Figure 16. TranslationStudio Dashboard