To create a new job, click on the name of a project on the page to open it and follow these steps:
Job details
-
From a page, in the table, click New.
The page opens.
-
Click Upload file, drag and drop a file on the field or Import from integration if available.
The uploaded file is presented at the top of the field and can be deleted if required
.
is set at the project level.
-
Select target languages (based on project definition).
-
If custom fields have been set as required by an administrator, select or provide those fields.
-
If permissions have been given to add custom metadata fields, these can be added by clicking the Add custom field dropdown list under and selecting what is required.
-
Click Create.
Job(s) are created and added to the list of jobs on the project page.
Workflow
-
Select a pre-translation option.
-
Click in the empty field to add a provider(s) from the dropdown list if required.
-
Jobs can be assigned to multiple providers—either Linguists or Vendors—when creating a new job, editing a job, or when using project templates.
-
Jobs can be accepted only by one Linguist at a time.
-
-
Provide (if applicable).
-
Select to automatically send email notifications to providers specified in step 4. Choose an email template from the dropdown list, and set an interval for sending the notifications (if applicable).
Example:
Three providers have been selected for Czech target language and an interval has been set for 10 minutes. When the selected workflow step starts:
-
Email notification is sent to Provider 1 immediately.
-
Email notification is sent to Provider 2 in 10 minutes.
-
Email notification is sent to Provider 3 in 20 minutes (10 minutes after last notification sent).
-
In projects with workflow steps, the steps are presented in the page. The are pre-populated from first workflow step settings, but each step can have individual , and settings.
File import settings
-
-
If source file is in a multilingual format (.XLSX, .CSV or .XML), ensure the correct file type is selected and specify how file content is to be imported and presented in the editor.
Example:
allows users to define the status of any segment that already contains the target translation.
and provide additional information for the translation and can be displayed in the editor.
specifies the maximum number of characters that can be contained in the target translation; characters above the limit are highlighted in the segment.
allows application of regular expressions to convert specified text to tags.
-
If importing an XLIFF file containing HTML code, import the file as Wordpress XLIFF.
-
If under the is not specified, Phrase tries to determine the encoding from the file header. If this is not possible, default encoding is used.
-
For most cases (not for binary formats): UTF-8
-
Java properties: ISO-8859-1
-
SRT: windows-1252
-
Joomla INI: Must be in UTF-8 (It is not possible to change it with Input and/or Output encoding settings.)
If the file is imported with corrupted characters, check the actual encoding of the file and set the accordingly.
-
-
Advanced settings
-
Set segmentation rules for the job.
-
Optimize how matching is managed for the job.
-
Provide files for the in-context preview of the original translatable document in one of the following formats:
-
.HTML file
-
.ZIP package containing a main .HTML file plus any additional .HTML or resource files (such as CSS, images)
-
.SVG file
File size limits: up to 100 MB per .ZIP file and 1 GB for the entire batch of files during bulk import.
-
Common Errors:
-
INVALID_REQUEST: The input file cannot be processed.
A general error informing that there was a temporary problem while importing the file; try importing again after a minute.
-
INVALID_REQUEST: Cannot process document which has cells merged across rows! See row # - The file may not be of the selected type (BILING_XLS).
This error is displayed if importing a Multilingual XLSX file with merged cells in any of the columns designated for translation.
-
If text from import is not displayed, ensure the character set is correct.