What are some best practices for sequential localization?
There are some recommended configuration settings and process steps for optimizing sequential localization.
Description
We use the sequential localization method and would like to know the recommended best practices.
Solution
- To only include files that require translation in the localization kit, edit
the system/conf/localizationmanagers.xml file and make
sure
<config name="full.context">false</config>
is set tofalse
. The default isfalse
. - To enable auto-translation, edit the
system/conf/localizationmanagers.xml file and make
sure that
in.context.exact.matches
is set totrue
. The default is false. - In the system/conf/localizationmanagers.xml file, the
include.default.images
setting adds the images as .image files in the localization kit. This is not to enable the translation of those images, but to provide context for the translators if their tool supports the preview of DITA topics.
-
Before performing a Localize, check the status of the files in the target languages. If the map exists in the target languages, it should be at Localization:done. This will ensure that all of the files of the source map are processed and that the translations are updated if they need to. If some files in the target languages are at still at Localization:in translation or Localization:review, they will not be updated, which will result in a partial update.
If the content in the target language is not at Localization:done and you want push the new version of the map anyway, to reset the translations to the latest version, all files that are not at Localization:done should be changed back to Localization:tb translated. This can be done with the Retranslate from source feature.Warning: If changing the status back to Localization:tb translated manually, make sure that the topics are not set to Localization:done when cycling through the statuses. - After performing a Localize and before preparing a kit, review any topics that are at Localization:review and change their status to Localization:done.
-
If a topic is reused in multiple maps and is currently at Localization:in translation, it will not be included in subsequent localization kits, even if the content in English has changed. It can only be out for translation once.
- When the content is imported, it is automatically set to Localization:review. At this status, it is still possible to import new translations. The content should remain at this status as long as the translations are not final. If you need to make corrections to the translated content that has been imported, ask the translators to do the corrections and to send the corrected files. Then do the import again.
- Once you have imported the final translated content, review the topics and
move all of the content to Localization:done. If this step is not performed,
the next translation will not work correctly. Note:It is possible to set up the localization workflow to skip the Localization:review state. Contact IXIASOFT for assistance on how to do this.