Open topic with navigation
The Translation Process
A typical translation process will involve variant sites and number of translation features.
- Creating a new page in the Master Site
- Creating original content for a Master Site page.
- Saving as draft.
- Sending the page into workflow or to Translation directly.
- While in Site Editor, users can decide to publish the content on the Master site immediately, send it to workflow that has a translation step. Many users can also submit pages for translation using the Translation Activity menu. See "Submitting a Page for Translation"
- Once a page is in a batch, the batch can be sent for translation immediately or held and sent at a later time.
- NOTE: a page with In Translation status cannot be edited in Site Editor.
- Once a minute, iAPPS checks for new batches, checks the database to pull the content to be translated, and sends it to Clay Tablet. Clay Tablet works with many third-party translators and can accept a large number of translation standards, such as xliff. As part of this process, the system also looks for returned, translated content and pulls it to the iAPPS database.
- When the page is received from Clay Tablet a new version is created for the page as it would be for a normal workflow. Content items are also versioned, but are not moved to the Content Library (and associated DB tables) unless they are approved and published.
- In Translation Activity, authors or administrators can see the returned translation awaiting them. They can either accept or reject the translation.
- If it is rejected, it will no longer be available on the system.
- Accepted Translations move to the appropriate content library.
Users can see a quick overview of Translations using the Translation Activity container on the main iAPPS Control Center Dashboard.
More detail is available on the Translation Activity Screen, which can be reached from either the Translation Activity container or the Authoring Activity drop-down mega menu.
See "Translation Activity" for more detail.
