As indicated in the Codex Overview article, Codex allows to upload traditional files to be translated on Wezen Translate. Codex allows to streamline the file import process by making use of Codex Profiles: as each file format have its technical specificities, it is recommended to define templates for each of them and a dedicated profile for it. This way, whenever you import a new file that follows a template, only the relevant content from the source file will be sent for translation right after the upload.
Requirements
- You must have manager role to access Codex Profiles page and edit them
Parameters for a Codex Profile
| Parameter | Mandatory | Description | Old parameter |
|---|---|---|---|
| content | yes | Paths to contents to send for translation | selectionPathList |
| context | no | Paths to contents to be used as translation context inside tasks | contextsPath |
| groups | no | References to be used to group contents to translate and to be used as context in the same tasks | groupingPaths |
| contentNames | no | Names to be given to paths in selectionPathList and contextsPaths, usually more friendly (ex: "short description" instead of "[0,1,2]") | contentNames |
| groupsNames | no | Names to be given to groups from groupingPaths, usually more friendly (ex: "myfile.xlsx - Wezen Codex" instead of "myfile.xlsx - group1") | groupingPathsNames |
| targetInjections | no | XLS, XLSX, XLSM only: columns where to save translated contents | targetInjections |
| targetInjectionsRange | no | XLS, XLSX, XLSM only: columns where to save translated contents, with target languages already specified in columns' headers | targetInjectionsRange |
You can also find more information about the syntax and the proper values to be used in scripts here.
Detailed articles for each file format
You can find some details about how to make great profiles for different files in those articles: