Difference between revisions of "Upload translated files"
(→Upload translated files) |
(→Upload translated files to Command Center) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | = Upload translated files = |
+ | = Upload translated files to Command Center= |
This can be used for files sent to the configured translation system - FTP, TMS, MT, LLM - and translated there and it can be used for files first downloaded via [[Download files to translate]]. |
This can be used for files sent to the configured translation system - FTP, TMS, MT, LLM - and translated there and it can be used for files first downloaded via [[Download files to translate]]. |
||
Uploading translated files is started from the [[Individual_Project_Tasks#Localyzer|Localyzer page]] |
Uploading translated files is started from the [[Individual_Project_Tasks#Localyzer|Localyzer page]] |
||
| − | It's more of a way to workaround some issues with TMSs or some translator issues (say, 'parameter mismatch'). |
+ | It's more of a way to workaround some issues with TMSs or some translator issues (say, ''parameter mismatch''). |
To upload translated files, all the files sent in that prep kit for that target locale must be present. They can either follow the zip packaging explained here, or they can be uploaded one by one. |
To upload translated files, all the files sent in that prep kit for that target locale must be present. They can either follow the zip packaging explained here, or they can be uploaded one by one. |
||
| + | In the ''example'' below, Japanese for prep kit 5 needs to be returned for a full 100% translation. |
||
| − | From the Localyzer page, click the 'Upload translated files' button, select the prep kit and the locale, and select either the zip file or each individual files. If the individual files method is chosen, each file being uploaded must match the filename of the files sent to translation. |
||
| + | From the Localyzer page, click the <code>Upload translated files to Command Center</code> button, select the prep kit and the locale, and select either the zip file or each individual files. If the individual files method is chosen, each file being uploaded must match the filename of the files sent to translation. |
||
| − | Once uploaded, the import process will be triggered for that project and follow the normal steps of importing, from making sure all the files are present, are named correctly, can be merged with existing files if necessary, pass the verification checks, and can be pushed to the data source (for example a git repository). |
||
| + | |||
| + | [[File:LocalyzerUploadStep1.jpg|center|600px]] |
||
| + | |||
| + | Once selected, make sure the translated files do match the files sent to translation. Click Upload. |
||
| + | |||
| + | [[File:LocalyzerUploadStep2.jpg|center|600px]] |
||
| + | |||
| + | The import process will be triggered for that project and follow the normal steps of importing, from making sure all the files are present, are named correctly, can be merged with existing files if necessary, pass the verification checks, and can be pushed to the data source (for example a git repository). |
||
| + | |||
| + | In this example, Kit 5 is now fully returned since Japanese was translated and imported without issue. The Localyzer page shows 100% for the translation status. |
||
| + | |||
| + | [[File:LocalyzerUploadStep3.jpg|center|600px]] |
||
Latest revision as of 22:18, 13 January 2025
Upload translated files to Command Center
This can be used for files sent to the configured translation system - FTP, TMS, MT, LLM - and translated there and it can be used for files first downloaded via Download files to translate.
Uploading translated files is started from the Localyzer page
It's more of a way to workaround some issues with TMSs or some translator issues (say, parameter mismatch).
To upload translated files, all the files sent in that prep kit for that target locale must be present. They can either follow the zip packaging explained here, or they can be uploaded one by one.
In the example below, Japanese for prep kit 5 needs to be returned for a full 100% translation.
From the Localyzer page, click the Upload translated files to Command Center button, select the prep kit and the locale, and select either the zip file or each individual files. If the individual files method is chosen, each file being uploaded must match the filename of the files sent to translation.
Once selected, make sure the translated files do match the files sent to translation. Click Upload.
The import process will be triggered for that project and follow the normal steps of importing, from making sure all the files are present, are named correctly, can be merged with existing files if necessary, pass the verification checks, and can be pushed to the data source (for example a git repository).
In this example, Kit 5 is now fully returned since Japanese was translated and imported without issue. The Localyzer page shows 100% for the translation status.
