Below you will find out how to manage versioning within a Codyt project. You need to take into account different scenarios here:
| Child pages (Children Display) |
|---|
How to upload a new version of your document:
If you have already translated the first version of a document in a Codyt project, and now wish to translate a second version of that same document, the first action to undertake consists in reaching the 'Documents' tab of your project:
Now, right-click on the document for which you have a second version, and select the option 'Manage document':
In the pop-up that appears, select the 'Upload new version' tab and upload your new document:
Click 'Next' once you have uploaded your document and selected the target languages of your project. You will then be redirected to another pop-up page where you should indicate the document version, and it is recommended to tick the option 'Use alignment to optimize reuse of previous translations' if the new version has a similar content and text structure.
| Tip |
|---|
You should not tick this option if sentences were added, or removed from the previous version. Please note that aligning complex script languages such as Japanese or Chinese with non complex script languages such as English or French may yield problematic results. |
The system will then process the document using the project's configurations.
Now, if you reach the 'Jobs' tab of your project, you will see that you can filter on the jobs for the past and current document version:
If you have enabled the project memory for pre-translation, then your new version will retrieve all the contents done during the work in the previous job.
You can easily check the content differences in the word counting icon, where new words will be highlighted in the recently created job (if any), and also when opening the editor, where pretranslations from a previous version will be marked with a blue or green arrow.
...
| title | Remember |
|---|
Changes in the job statuses
Depending on the status of the job before the versioning process, the new version will be:
- For already completed jobs → New version will be "Not Started", if there were any text changes that require further attention
- Jobs which were in progress will pass into completed → New version will be not started/not assigned depending on the type of supplier dispatching you have chosen (retrieve previous worker of the job, original project assignment, etc.). These users will be notified of an update on the text leading to a new job, due to the versioning process.
- Jobs which were not started/Inactive/Not assigned will pass into cancelled → New version triggers back the same job configurations available in the original version.
Here a wrap-up table of the different possibilities described above:
...
*Job will be proposed again only if contents have been changed.
Invoicing new versions
...
Any time working documents are modified, you will be able to trigger a versioning process to save and reuse the ongoing work.
Below you will learn how to manage versioning within any of the project types Wordbee handles. You need to take into account different scenarios:
| Child pages (Children Display) | ||
|---|---|---|
|