|
|
Manual translation |
|
|
|
|
|
Manual translation |
|
|
|
|
|
|
Manual translation |
|
|
|
|
|
Manual translation |
|
|
|
|
|
|
||
The manual service exports the translation data onto the file system. Every translation submission is converted to a zip archive containing .xlf files (the source data in XLIFF format) and instructions. This allows you to deliver the translation assignment by sharing the export folder or by manually sending the submission package to the translators.
The service checks for finished translations in a designated import folder. The translators can also manually upload the completed zip package through a specific system page (the default instructions provide a link).
|
Important!
The package containing the completed translation must have the same names as the original source package for all .xlf files and the parent zip archive. The system uses the names as identifiers when importing the translated data. |
To set up the manual translation service, go to Site Manager -> Settings -> Content -> Translation services and configure the settings in the Manual translation section:
Translation submission export folder |
Specifies the path of the folder where the service creates the zip packages with the translation source data (XLIFF files and instructions).
If empty, the ~/App_Data/Translations/Export/ folder is used. |
Translations import folder |
Sets the path of the folder from which the system imports zip packages containing completed translations.
If empty, the ~/App_Data/Translations/Import/ folder is used. |
Delete ZIP after successful download |
If enabled, the system deletes the zip packages containing finished translations after importing the XLIFF data. |
In addition to the .xlf files that store the translation source data, the manual translation service places instruction files into the exported zip packages. The instruction files are created as copies of template files found in the ~/App_Data/CMSModules/Translations/Template/ folder under your web project.
By default, the folder contains the Instructions.html file. You can modify the content of this file according to your own requirements and even add additional instruction files that the service will include in the zip packages.
You can use context macro expressions in the text of instruction files to dynamically insert the values of the given submission. For example:
•{% Submission.SubmissionSourceCulture %} - returns the culture code of the translation source language.
•{% Submission.SubmissionTargetCulture %} - returns the culture code of the target language.
•{% GetTranslationPriority(Submission.SubmissionPriority) %} - returns the priority set for the submission (low, normal or high).
•{% Submission.SubmissionDeadline %} - returns the date and time of the submission's deadline.
•{% Submission.SubmissionInstructions %} - returns the additional instructions entered for the submission.
•{% Submission.SubmissionWordCount %} - returns the total number of words in the translation source text.
•{%SubmissionLink%} - returns the URL of a system page where users can upload finished translation packages.
