You need one new duplicate for each language into which content is being translated.
It is recommended that you create each duplicate from the Library, using a separate, clearly labeled folder for each language.
Re-record topics.
Re-recording captures screenshots and object names in the target language.
This provides a translation only of automatically recorded content.
Apply the appropriate template for the target language to update template text.
Use export/import for localization of custom Developer text.
You can export to Word or XLIFF formats.
It is recommended that you check in all content to be translated prior to exporting and export the server version.
Translation is performed external to the Developer.
During import, you can choose to skip documents that were changed after the localization export or overwrite the exported documents with the translations added to localization file.
Translate external content and update glossary links.
Package files containing text, package graphics, and URL attachments must be translated separately from custom Developer text.
If necessary, fix any links to package files that might have been broken during the translation process (for example, if the name of a linked package file was changed).
As a final step after all content has been translated, update glossary links.