After logging in, the project overview appears; the view of the project manager.
The following two options are available in the project menu:
Delete project completely: Deletes a project completely.
Refresh project: Updates the project list.
Column | Explanation |
---|---|
TaskGuid | In this column, you can see the Globally Unique Identifier, i.e. the unique identifier of the respective project. |
Id | In this column, you can see the automatically assigned identification number of the respective project. The project ID is incremented automatically. |
Actions | The “Actions” column contains the following button:
|
Name | The project name is displayed in this column. |
Client | The name of the end client is displayed in this column. |
Project manager | The name of the project manager responsible for the project is displayed in this column. |
Source language | This column displays the source language of the project from which the translation is being performed. |
Order no. | The manually entered order number of the project is displayed in this column. |
Project description | If available, the project description is displayed in this column. |
Order date | This column displays the date that was entered as the order date when the project was created. This is usually the date on which the project was created, but it can also be changed manually during creation. |
In the “Users” tab, users can be assigned to the various workflow steps of the project – as in the “user association” step during project creation. This can be done at any time during the ongoing project. It is also possible to inform users about the user association again by e-mail.
If required, users can also be removed from a task despite the respective client’s user assignment defaults. |
The language resources used in the current project can be managed in the “Language resources” tab:
Click on the “Start analysis” button below to analyse the project files again based on the adjusted settings and pre-translate them depending on these settings.
When performing the analysis, quality assurance and terminology check are also carried out in parallel. |
In the “Analysis” tab, you can recalculate the project total amount based on the current analysis:
The time stamp of the analysis used is noted in the top line, as well as the information whether or not internal fuzzy matches were taken into account in the analysis in question. |
The “Quality assurance” tab shows all errors registered by automatic and manual quality assurance in the task selected above. The “Re-check” button at the bottom can be used to restart the quality check and thus update the info in the quality assurance tab.
In the “Manage files” tab, translator packages can be downloaded and uploaded for editing in another tool than translate5.
It is important that the translator package contains the correct (sub)folder structure:
Currently, the following .xliff file formats can be exported and imported: xlf, .xlif, .xliff, .mxliff, .mqxliff, .xml. | |
The functionality of downloading and re-importing translator packages can be deactivated in the configuration of your translate5 system if required. | |
The functionalities in the “Source files” and “Reference files” sub-tabs are not implemented yet. |
In the “Properties” tab, the following properties defined during project creation can be changed/added for each task within a project:
If no users have been assigned yet, the way of collaborating in the workflow can be set (simultaneous, competing, sequential).
If necessary, individual project managers, delivery deadlines, project descriptions, etc. can be defined here for the individual tasks of a project. |
The current project’s configuration can be adjusted in this tab, provided this option is activated in the system settings.
The project’s event messages are listed here. An event code is listed for each event, which can be looked up via a link in the corresponding Git directory. The messages do not include the complete system log; however, it can be accessed via this tab.
The events belong to one of the following categories:
information | |
error | |
warning |
Information that is underlined, is mandatory. This is marked with a 1 in translate5. | |
Start typing in the drop-down field to find options more quickly. For languages, for example, you can type in the ISO code: “de-de” will find “German (Germany) (de-DE)”. |
To create a project, click on the “Add project” button in the project overview.
The “Create project” window opens. Enter the following values on the left-hand side:
You can further specify:
A preset for the three checkboxes can be defined in the system configuration. These settings can be overruled at client level. | |
The file format and segmentation settings can be defined in the file type filter configuration. |
On the right-hand side of the “Create project” window, you can specify the following information in the “General” tab:
The various project files can also be uploaded via drag-and-drop:
|
You can add a PDF or HTML file or a URL in the “Visual file upload and configuration” tab. Use the “Connect layout to” drop-down to specify whether the visual layout should be connected to the source language or to the target language.
For this functionality, the Visual plug-in is required. |
At the bottom of the window, you will find the following buttons:
In this step, you select the workflow for the current project and assign the individual workflow steps of the project task(s) to the users.
Workflow steps that are not assigned to a user are skipped in the project. | |
If you require workflows other than the two standard ones, please contact us. Any individual workflows can be configured at database level. | |
The user assignments can be predefined in the client profile. | |
The collaboration type can only be defined for the entire project. It is therefore not possible to switch workflow types between the individual tasks. |
Assign the task’s workflow steps to the users on the right-hand side of the window by:
The workflow steps that have already been assigned then appear in the view on the left-hand side and can also be removed again. In order to do this, the line with the user association in question can be marked by clicking on it and then deleted using the “Remove” button.
Not all workflow steps need to be assigned, but only those that are required in the current project. All the others are automatically skipped by translate5. |
At the bottom of the window, you will now find the following buttons:
In this window, all language resources – i.e. translation memories, engines for machine translation and TermCollections – are displayed that are available for the client, for whom the project is being created. The language resources can be selected or deselected by ticking or unticking the box. It is important in which column the tick is placed:
These three options are unavailable and greyed out if no language resource is available or activated. | |
The “Associate language resources” window appears a second time when a project with pivot language is created, so that the language resources can be selected and configured for the target language on the one hand and for the pivot language on the other hand. |
In this step, project-specific configurations can be made if these are to deviate from the current standard and/or client settings.
In order to find the relevant settings quickly, this window offers the following functions:
At the bottom of the window, you will now find the following buttons:
After confirming, translate5 switches to the project overview, focussing on the project that has just been created, and the import is run in the background. This step can also be seen in the right-hand side of the window, where the tasks of the project are listed, and their statuses are displayed.
If user notification is active in the project, the corresponding e-mail notifications are sent to all users assigned in the workflow immediately after the import is completed and processing of the first workflow step can begin.