Continuous localization helps in projects and jobs that have incremental changes and require a continuous delivery of updated translated texts. It is the integration of the localization workflow into the development process instead of the tradition of it happening after the development process. As an example, in the software development environment, updated text strings are automatically handed off to the TMS and processed in time with the release cycle.
Continuous jobs and continuous projects do not have the same abilities.
|
Feature |
Continuous Jobs |
Continuous Projects |
|---|---|---|
|
Monitors |
Single Files |
A folder of files |
|
Single project |
Files from different repositories and locations |
One folder in one repository (excepting Git and Sitecore where multiple folders can be monitored) |
|
File types |
Limited |
All |
|
Workflows |
Yes |
Yes |
|
Unchanged segments carried forward to updated file |
Yes |
Yes |
|
Pre-translation |
Yes |
Yes |
|
Due date calculations |
No |
Yes |
|
Analyses/Quotes |
No |
Yes |
When using the update source function the word calculation related to a subscription word allowance is run in a different way in order to consider only the amount of text that has been added or changed in the updated content.
The job summary indicates the number of segments and word count of the initial upload of a job.
Using the update source function, a previously imported file can be updated with a new source file.
Adding four sentences (two unchanged with a total of 17 words, two changed with a total of 4 words), the job summary indicates the counts of the latest version as well as the aggregated counts.
Added segments: last total segments number + changed segments number
Added wordcount: last total word count + total words added in changed segments
In our example:
Added segments: 3 + 2 = 5
Added wordcount: 19 + 4 = 23
An additional update (four sentences with two unchanged with a total of 4 words, and two changed with a total of another four), the job summary is updated with this latest version and the aggregation includes all updates.
Note
Changes made to source segments in the editor do not impact subscription word count. However, those changes do impact how word count is calculated when using the update source function; the uploaded file is compared to the version of the file visible in the editor. If a file is uploaded to a project, edited in the editor by joining segments, or the addition or removal of some words and then uploaded again, the word count of the changed segments is added to the subscription word count.
Automated project creation can be configured to continuously update an existing project. When enabled, a new project is created and used continuously for all updates to the source files already in that project instead of creating a new project every time a source file change is detected.
Project templates are only applied during project creation and not when new or existing jobs are updated.
When source files are updated, linguist are notified by email and in the editor in which options to immediately reload the source Reload now or to wait until the source is updated again Reload later are available. The source can also be updated manually with Update job.
Job status updates:
-
If the status is New, Emailed, Accepted, Declined, or Rejected the job is reloaded and status maintained.
-
If the status is Completed or Delivered the job is reloaded and the status is changed to Emailed.
-
If the status of first workflow step is Cancelled, the job is left unchanged.
-
Before updating, unchanged segments are copied together with the translation in the target.
-
If a job in continuous project is deleted and an update of the source file in the online repository is made, a new job is created.
Reopening of completed continuous projects when new work is detected:
-
If a project is set to Completed and CP scans a repository to find processable work, it sets the project to Assigned to indicate new work.
-
If the status of an existing project is Cancelled and a file has been modified or a new one is detected, a new continuous project is created.
Exporting translations back to the repository
-
When the project is continuous, jobs are exported when the last workflow step is Completed.
-
Jobs can be manually exported by choosing > . Even unchanged files will be exported.
-
Each target file is stored in a target path specified in the CP settings.
Re-importing:
-
Jobs can be re-imported from the menu on the jobs table.
Integrations:
-
If a due date scheme is defined for a service associated with a continuous project, it is applied to new or updated jobs.
-
If a price list is defined for a service associated with a continuous project, it is used to generate quotes for new or updated jobs.