Import translated content
Once the translation agency completes its work on the submission, it is time to import the translations into CCMS Web.
Until this phase in the workflow, CCMS Web does not add any new objects to the Content Store. An import of translations triggers the creation of a version of the object for the target language.
Because localization is an extremely flexible process, your own approach to managing what you import and when you import it really hinges on your company standard processes, the agency, and any potential issues you have to solve along the way. That means that while you cannot import individual objects, you can create a zip file that includes an assortment of translated content at the time that best suits you and best fits the arrangement you have with your translation agency. That's because imports are not tied to any particular translation or language manifest, but to their filename.
Since the translation manifest is a snapshot, nothing changes there. However, the language
manifest dynamically updates and all imported objects that were dimmed now have a
status of Translation:in review
. The primary exception is for
images that did not require translation. The other exception has to do with the
import itself. If you import only a portion of the objects you submitted for
translation, all objects still out for translation retain the In
translation
status and remain dimmed.
- The Title column uses the translated title.
- The Filepath column changes from
/content/authoring
to/content/translation
To import translated content: