-
Team, Professional, Business and Enterprise plans
Get in touch with Sales for licensing questions.
-
Team, Ultimate and Enterprise plans (Legacy)
Get in touch with Sales for licensing questions.
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.
Continuous jobs and Automated Project Creation (APC) are independent from each other. Continuous job settings have no effect on APC behavior.
|
Feature |
Continuous Jobs |
Continuous Projects |
|---|---|---|
|
Monitors (via an integration connector) |
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.
Using the Continuous jobs feature, updated versions of an original file from a repository are uploaded to an existing project, overwriting the older version of the same file.
When new strings are added to a file in a repository, the modified source strings are updated and any deleted source strings are deleted as well. Unchanged strings that are already translated are copied to the updated version of the job.
Job Updates:
-
The job is monitored periodically based on the settings.
-
If a change in the source file is detected, the job is updated in all workflow steps.
-
If the job that is being updated is opened in the CAT web editor (i.e. someone is working on it), a notification is displayed to the user, and they are prompted to reload the job.
-
Segments are updated based on the changes made in the source file.
-
Before updating, unchanged segments are copied together with the translation in the target.
-
The target is cleared for segments with the changed source. (The previous translation for confirmed segments isn't lost because it's saved in the translation memory.)
-
Segments deleted from the source file are also deleted from the job.
Job status updates:
When a source file is updated, then:
-
If the job status is Completed or Delivered, the status is updated to Emailed.
-
If status is Cancelled, job content and status is unchanged.
Jobs can be re-imported from the menu on the jobs table.
-
All other statuses stay unchanged.
-
If a multi-step workflow is used, the status of each step is treated independently.
Example:
Exporting translations back to the repository:
-
The translation is periodically pushed back to the repository based on the frequency set in the settings. Translated target segments are exported only if they have been modified.
-
Jobs can be manually exported by selecting Export to online repository from the menu. Even unchanged files will be exported.
-
Even unconfirmed modified segments are exported.
-
If a multi-step workflow is used, only changes in last workflow step are exported; the status of previous steps must be set to Completed but the step from which the changes are exported does not.
-
By default, each target file is exported to a folder specified in project settings.
Restrictions:
-
Only available for specified file formats.
-
The file must be uploaded from an online repository using a connector.
Continuous jobs are presented in the project page with . The tooltip indicates when the job was last updated.
Note
If there are problems with a continuous job, hovering over the ellipses displays job information. Click See history to display a detailed history of the job to help troubleshoot where and when the problem may have occurred.
-
RESX
-
XML, Multilingual XML
-
PO, Multilingual PO
-
XLSX, Multilingual XLSX
-
Properties
-
CSV, Multilingual CSV
-
JSON
-
YAML
-
Android XML
-
iOS strings
To import continuous jobs to a project, follow these steps:
-
When creating a job, in step two, click on Add from online repository , select a repository/file and click OK.
The selected file is displayed on the New Job page.
-
Select the Import files as continuous jobs radio button.
-
This option only appears if at least one of the selected files is supported for Continuous Jobs.
-
-
Finish creating the job.
To set continuous job frequencies, follow these steps:
-
Job frequencies can be set globally or on a project level.
-
Globally
From the Settings
page, scroll down to the section and click on Continuous job settings.
The page opens.
-
Project
From a Project page, click Edit.
The page opens.
Click Continuous job.
The frequency settings are displayed.
-
-
Select frequencies
-
This controls how often the repository is checked for updates. (The shortest interval available is every 30 minutes.)
-
This controls how often the translated content is exported back to the repository. (The shortest interval available is every 30 minutes.)
-
-
Click Save.
Settings are applied to any new jobs.