Reviewing and correcting translated content
If it is part of your company's process, you can review translated content to ensure the primary components are there and look as you expected.
- Review before import
You can have an in-house reviewer review the content after you receive it from the LSP and before you import it into CCMS Web. Some local environment setup is required for this approach, which MadCap Software does not support or recommend. However, if you require the translations to be reviewed in-house before import, it is possible.
- Review the content itself after import
- Use a Collaborative Review or Approval
After import, you can create a Collaborative Review or an Approval for translated content
In addition to creating a Collaborative Review for the current Language Manifest, you can also create a Collaborative Review that is redlined against previous Language Manifests for the same map and language, to get a better look at what changed between translations. See Create a Collaborative Review redline for a Language Manifest for more information.
After translated content has been imported and reviewed, it might be necessary to make corrections. Some corrections might be as simple as correcting a typo or removing extra spaces. Other corrections might be more complex.
You can make simple corrections directly to the translated topic by checking it out (from
within the context of the Localization Manifest) and editing it, just as you would
content in Authoring. (Users who need to do this must have the Translation Coordinator
role or another role that can edit content at Translation:in review
.)
If the error originates from something in the Authoring topic, be sure to correct that
topic as well to ensure the error doesn't continue to occur in future translations.
Retranslating
If the error is more complex, it might be necessary to retranslate the content altogether. CCMS Desktop features a Retranslate from Source option that makes this easy to do. CCMS Web does not have this option yet but you can accomplish the same thing.
- Leave all files that need corrections at Translation:in review.
- Move all files without errors to Translation:done to avoid importing them again unnecessarily.
- Notify the LSP of the issues that need to be corrected. They can make the corrections to their copies of the source files and send you the corrected files to re-import. In this way, the LSP can keep the preferred translation current in translation memory to improve future translations.
- Re-import the corrected files and review them again to ensure the corrections have been made.