Features of translate5

For a screenshot with the most important features, please see our overview page.

Test translate5 immediately, free of charge, and without registration at translate5.net!

Feature Overview

Project Management & Workflow

Task Overview

The task overview of translate5 is listing all tasks to which a user in workflow is allocated. If the user is allocated to the role of a project manager, he can see all tasks.

In the task overview of translate5, all imported tasks can be flexibly filtered according to their features:

  • Order number
  • Name of task
  • Source language
  • Relay language
  • Target language
  • Status
  • The number of users allocated to the task
  • Project manager
  • Number of words
  • Delivery date (expected)
  • Delivery date (actual)
  • Reference files included
  • Terminology tagged
  • Order date
  • Source language can be edited

As is standard in translate5, filters can be combined across several features. This way, all projects of a project manager can be found in a language combination, for example.to the top

Import and Export of Tasks

Tasks are directly imported and exported from the task overview. Files are exported in the same format (SDLXLIFF or CSV) as they were imported. A task can include any number of files in the import. A task can include both SDLXLIFF- and CSV-files.


translate5 supports SDLXLIFF as import format. In addition, the SDLXLIFF-syntax for the "track changes" functionality is supported in the export.


translate5 supports CSV as import format. As in SDLXLIFF, changes can also be tagged in CSV in the export. When importing, the codings UTF-8, ISO-8859-1, and WINDOWS-1252 are supported. For more on CSV as an import format, please refer to Information about operation of translate5.to the top

Task Activities in Workflow

With each task, the following actions are available to the user according to the roles allocated to him and the workflow status of the task:

Processing of Task

A click opens the task for processing in the editor of translate5. The action is only available, if the user was assigned a respective workflow role for this task and it is his turn for processing in the workflow.

A user with the role of a project manager is always able to process all tasks that are not processed by another user at the moment.

Opening a Task for Viewing

Each user is able to open a task for viewing regardless of his role and his status in the workflow, which is allocated to him. The user with the role as a project manager is always able to open all tasks for viewing.

Finishing a Task

Tasks that can be currently processed, can be finished by a user. After that, the user will not be able to process anymore. He signals with the completion that he finished processing the task. If there are no other users for whom this task is still open in the current workflow step, the workflow will initiate the next workflow step.

Completely Finishing a Task

A user with the role as a project manager is able to completely finish a task. Thereby, all allocated users cannot process it any longer - regardless of whether or not they themselves already finished their task. The individual task status of the user, however, remains intact in the background and can be viewed at any time.

Reopening Completed Task

A user with the role as a project manager is able to reopen a completely finished task. By doing this, the individual task status of the user is affecting the ability of processing the task again.

Allocating Users to a Task

A user with the role as a project manager is able to allocate users to a task as well as a role to the users in the workflow. The same holds true for the workflow status where such an allocation is located. A project manager is able to add or delete allocations in the workflow at any time - or also change the workflow status of a task.

Exporting a Task

A user with the role as a project manager is able to export tasks (with or without "Monitoring changes"). Each user (i.e. also editors and translators) is able to export MQM-statistics collected on a subsegment base.

Deleting a Task

A user with the role as a project manager is able to delete a task from translate5 entirely.to the top

Basic Workflow

Workflow Roles

The translate5 basic workflow knows three workflow roles: Editor, translator, and visitor.

Workflow Steps

The translate5 basic workflow knows two workflow steps: "Editing" (1st step allocated by the role as an editor) and "checking of editing" by the translator (2nd Step allocated by the role as a translator) It is possible to allocate only users with the role as an editor to a task in the workflow - then the second workflow step is omitted. The role as a visitor is not allocated to any workflow step. It has no function in the workflow chain. A user with the role as a project manager is able to open a task in the workflow for viewing at any time, but not able to process it.

Workflow Status of Task Allocations

Each allocation of a user with a role to a workflow step has a status where this allocation is currently located. The translate5 basic workflow knows the following workflow statuses:

  • Open: The task can be currently processed by the user.
  • Waiting: The user can process the task as soon as it is his turn in the workflow.
  • Completed: The user completed the processing of the task and thus cannot open it for processing anymore.

The project manager is able to change each task allocation for each user at any time.

Workflow Status of Tasks

Regardless of workflow status of task allocations, a task in itself has a status in the workflow. This status is affecting the task allocations:

  • Open: The task can potentially be currently processed by users.
  • In process: A user is currently processing this task. Thus, it is inaccessible to all other users for processing, but open for viewing.
  • Finished: The project manager finished the task. Regardless of the status of their task allocations, the users are not able to process the task anymore.

The Workflow Chain

The workflow chain consists of workflow steps of the translate5 basic workflow: "Editing" and "Checking of Editing". Or, according to the choice of the project manager, only "Editing".

When allocating users to a task, the standard status of a task allocation is "open" to editors and "waiting" for translators. However, the project manager can freely decide on this differently, if he deems it reasonable.

Whenever all editors have completed a task, the workflow chain will jump to the 2nd workflow step "Checking the editing". The task status for all translators is automatically set on open, and they receive an e-mail with the message that it is their turn.

This e-mail includes a list of all segments, which were amended by the editor. For these segments columns "segment numbers", "source texts", "target texts - processed", "status", "QM", "auto status", "match rate" and "comments" are displayed in the E-Mail. Internal tags, QM subsegment tags, and terminology labels can be seen in this e-mail, just like in translate5, if the e-mail client is supporting this. The project manager also receives an analog e-mail. In addition, his e-mail includes the list of all translators now starting the processing.

Whenever the next user is opening his task, he initially will - due to the preset filtering - only see the segments, which were processed in the previous workflow step.

Whenever a task has been completed in its last workflow step, the project manager will receive an e-mail about it. This e-mail includes a list of all segments, which were amended in the last workflow step.

The following screen shot is a sample of the content of such an e-mail:

In addition to the e-mail, the processed segments are saved in a machine-readable XLIFF-file. This is attached to the e-mail and resides in the file system in the task folder.


High Performance with Large Amounts of Data

The performance of translate5 is independent from the size of the project. Whether there are 100 segments, 10,000, or 100,000 segments in a project - the speed of operation remains the same. This is possible due to state-of-the-art architecture: Only the current 100 segments are always downloaded to the browser. Advance loading in the background allows seamless work.to the top

Any Number of Segments can be Continuously Scrolled in a Project

All segments of a project can be processed in a table that can be continuously scrolled. Opening and closing individual files is no longer required. Consequently, 500 small files can be processed by the editor just as efficiently as 3 large ones.to the top

Hundreds of Files in a Project

Each individual file of a project is displayed in a file tree analogous to Windows Explorer. This can be nested arbitrarily deep and contain any number of files. Folder hierarchies reflect the folder structure in the import list.to the top

Usability: Approach When Editing

Highly Flexible Filtering and Sorting of all Segments

Source language, target language, edited target language, relay language, comments, and all meta data are listed in their own columns in translate5. Each of these columns can be filtered and sorted and can be faded in and out.


The filters can be combined with each other by AND operation. This way, for example, all segments that are tagged "Must be revised" and were translated by "Translator A", can be selected with a few clicks and then edited. Or all segments can be selected, which contain the word "IT" in the source language and the word "data processing" in the target language.


Additionally, the segment overview can be sorted in an ascending or descending order after each column - regardless of whether a filter is set or not. This way, for example, all segments with match rates between 90 and 99 percent with "status 1" can be initially edited and then all those with "status 2".to the top

File Overview in Tree Structure - Clicking on File takes you to Beginning of Respective File

Each individual file of a project is displayed in a file tree analogous to Windows Explorer. This can be nested arbitrarily deep and contain any number of files. Folder hierarchies reflect the folder structure in the import list. By clicking on a file, you get to the first segment of this file in the segment table.to the top

Files in Tree Structure can be Resorted

The initial, unfiltered, and unsorted sequence of the segments in the overview corresponds with the order of the segments in the files and the order of the files in the file tree. If this order does not comply with the editor's needs, he can resort files in the file tree by simply dragging & dropping - the order of the segments in the overview will change accordingly.to the top

Quality Assurance

Quality assurance is the purpose of editing a translation and consequently the purpose of translate5. Therefore, translate5 provides quite a number of interesting and in part unique features for quality assurance exceeding the actual editing.

MQM Quality Assessment on Subsegment Base

With translate5, MQM tags can be allocated to any partial sections of segments. The values selectable for the MQM tags can be flexibly specified at the start of the project. Values can be, for example: "Wrong terminology", "bad phrasing", "wrong translation" etc. So, an MQM tag marks the respective paragraph to a certain, qualitative extent. In addition, an MQM tag-specific comment and an evaluation (of grave, mean, or light mistakes) can be assigned to each MQM tag.

It can be determined in translate5 which MQM types are available by default for a task. In addition, when creating a task, each task can be given its own set of MQM types only valid for this task.

translate5 creates on-the-fly MQM statistics on assigned MQM tags at any time. It can be accessed within the Editor in graphically well presented form or alternately as an XML download. With the help of the QTLaunchpad (see below), a percentage value describing the translation quality objectively, can be calculated based on this statistics.

MQM tags can also be inserted into the source language and separately evaluated accordingly. This way, even translation errors, which already originated in quality problems of the source language, can be gathered in a useful way. Whether this is possible or not can be set when creating the project.

MQM quality assessment on subsegment base was inspired by and implemented for QTLaunchpad. In short, the multi-dimensional quality metrics (MQM) developed by QTLaunchpad includes a concept and a procedure to define and measure translation quality according to uniform standards - regardless of whether the translation was done by a human or a machine. Before QTLaunchpad, no approach for reliable comparability existed. QTLaunchpad is a project supported by the EU by DFKI (Deutsches Forschungsinstitut für künstliche Intelligenz)Dublin City University, University of Sheffield and Athena Institute for Language and Speech Processing. Therefore, translate5 presents an ideal setting for measuring translation quality with the criteria of QTLaunchpad .to the top

QM and Status Assessment on Segment Base

Aside from the labeling of subsegments with QM tags, one or several QM criteria can be assigned to each segment as a whole. Additionally, a status value can be assigned to each segment. Which QM criteria and status values are available here, can be set in translate5.to the top

Sophisticated Labeling of Terminology

The labeling of terminology in the segment is state-of-the-art in modern translation environments - as is also the case in translate5:

  • A TBX file is turned over to translate5 during import. Based on this file, terms in the imported, bi-lingual files (e.g. SDLXLIFF) are labeled and accordingly visually high-lighted in the segment overview.
  • For terminology labeling, translate5 uses the XliffTermTagger by Prof. Klemens Waldhör, which is also licensed under Open Source. Aside from exact hits, XliffTermTagger also supports stemming, fuzzy matching, and tolerance in the use of upper and lower case letters. It is specified in translate5, which of these procedures and which fuzzy value is used.
  • The segment meta data show all terms belonging to the same term as the term in the segment - even if they themselves do not come up in the segment.
  • The segment meta data indicate at each term, whether it is a preferred term, an allowed term, or a banned term.
  • The term definition is visible at each term as soon as the mouse is dragged over it - with source-language terms the source-language definition and with target-language terms the target-language definition.
  • translate5 goes one step further than most of the solutions subject to charge: The terminology in the target segment is labeled, even if the corresponding source-language term does not exist in the source segment.
to the top

Support for "Track Changes" in Trados Studio by translate5-Export

When exporting a project from translate5, it is optional to insert modification tags. Whenever a document exported in such a way is opened in Trados Studio, the changes performed in translate5 by the editor, are part of the "track changes" functionality within Trados Studio. With the function "Monitoring changes", they can be accepted or denied within Trados Studio.to the top

Searchable Comments on Segment Base

translate5 captures comments in a column of its own within the table structure. As all other columns, too, the segments of a project can be filtered or sorted in translate5 on the basis of the comment column. For example, all segments with comments can be displayed on top - or only those segments with comments of a specific user can be displayed.

Each comment shows, which user created the comment when.

Your own comments can be edited or deleted at any time.to the top

Blocking of 100% Matches

When creating a project, 100% matches can be disabled by the editor for editing.to the top

Editing of Source Language

Quality problems of the translation can frequently be traced back to ambiguities or quality problems in the source language. With translate5, the source language can also be processed, if the project manager sets the appropriate setting. This is particularly interesting for labeling source-language errors with MQM subsegment tags as well.to the top

Usability: Display

Ergonomic Mode Reduction of the Display to the Essentials

The Ergonomic Mode of translate5 reduces the display of the elements, which are continuously needed for editing. In addition, the font is conveniently enlarged. Faded-out elements can also be faded in again at any time within the Ergonomic Mode.to the top

Flexibly Adjustable Display - Fading in and out of Columns, Restructuring of Columns, etc.

All columns of translate5 can be dynamically faded in and out as well as moved by the user. This applies to the editing mode and display mode as well as to the Ergonomic Mode. The file tree and the segment meta data can also be faded in and out at any time. Thus, at any time, the user can customize translate5 so that editing is most convenient to him/her.to the top

In Display Mode, Tags can be Completely Faded Out

The display mode is for easy and quick reading without distracting elements. Therefore, the tags are completely faded out here. This requires the deactivation of editing of segments in the display mode.to the top

User Interface in German and English - Easily Expandable to Additional Languages

The user interface of translate5 is currently available in German and English. Localization takes place when an XLIFF file is translated and can thus be very easily expanded to any language.to the top

Efficient Editing

Automated Adaptation of Repetitions

Repetitions of segments can be automatically replaced in translate5 without the editor having to touch them again. Depending on the setting, exactly which repetitions need to be replaced happens either fully automatically without request or on request. The repetition editor displays the source segment, target segment, and the information, whether the source segment is repeated, the target segment is repeated, or both. In addition, the user is notified, whether the currently displayed segment is faded in or out in the current filtering of the segment overview.

Compared to other editing solutions, translate5 is also capable of automatically replacing repetitions, which are only identical in the target language, but differ in the source language.to the top

Use of a Relay Language

Your German-Russian editor does not understand any German? With translate5, you can set up your German-English translation as a relay language when importing the project. With each segment, the English translation is then available to your Russian editor, in addition to the German source language.to the top

Reference Files - File Attachments for the Project

Reference files or other files important to the project, can be transferred with translate5 when importing the project. They are then available to the editor in its own collapsible section for downloading.to the top

Short Tag Mode, Full Tag Mode, and Fade-out of Tags

Tags are visible in translate5, as usual, as small, graphic units. They can be changed in their position by dragging & dropping and by copying & pasting. The tag display can also be switched:

  • In standard, the short-tag mode is active. Tags are numbered consecutively and not labeled. In mouse-over, the full tag can already be seen here, which actually exists in the bi-lingual format.
  • In full-tag mode, the tag can be seen in full length.
  • In display mode, the tags are completely faded out.
to the top

Auto Status

If the editor saves a segment, it gets automatically the auto status "Edited". If a segment is automatically recognized as a repetition and adjusted, it has the auto status "Auto-edited". Analog statuses are set for the project manager and translator. All segments can be filtered and sorted based on their auto status.to the top

Post Editing & Machine Translation

Several Alternate Target Language Columns

With the help of CSV import, several alternate translations can be imported for the target language. These are displayed side by side each in their individual column in the translate5 editor. The alternate translations can be separately processed, filtered, sorted, and labeled with MQM-tags. For each alternate translation, a separate, statistical evaluation takes place. This feature is particularly interesting for improving the quality of machine translation.to the top

MQM Quality Assessment on Subsegment Base

The MQM quality assessment based on segments is particularly suited for the qualitative improvement of the results of machine translation. It is used for allowing the comparison of the results of various machine translation tools - and to be able to also compare them with human translation quality. For additional information see here.to the top

Assessment of Processing Time

For each segment, translate5 records the time spent processing in milliseconds in the database. This happens separately for each revision of a segment. This way, it can be flexibly evaluated with the help of suitable SQL queries, how much time the editor needs. All available segment attributes, like QM flags, status flags, user name, match rate, language combination etc., can be included in the queries.to the top

IT Security

The security of an IT system is first of all a question of the quality of the source code. In addition to that, it is important that security relevant aspects are taken into consideration from the start when planning software architecture and developing features. The third criterion is how quickly errors can be detected, corrected, and installations updated.

Quality of Source Codes

Quality and architecture of the source code are crucial for the security of a program:

  • Can the source code be easily read by developers? Does the developer know very quickly, where what is happening in the source code?
  • Is the architecture of the source code structured in such a way that security relevant processes are running at clearly defined points of the source code?
  • Are all inputs from the web checked and is ensured that they can only be used for the intended purpose?
  • Are all resources of the application subject to an access control system linked to user rights that are to be explicitly assigned?
  • Have measures been taken against session hijacking, cross-site scripting, and CSRF attacks? Are these attack scenarios taken into consideration in the development?

We are taking all these points into consideration during the development of translate5.to the top

Real-Time Error Reporting via Mail

Frequently, it is crucial for the security of a program how quickly programming errors are discovered and corrected. Errors in the program are frequently used as attack vectors when hacking into a system.

MittagQI has chosen a radical approach for translate5 when reporting errors: Each error message from the server in the program sequence is immediately sent to our development team via e-mail. This also applies to companies whose installations we are supporting with a support and update agreement. All translate5 installations supported by MittagQI are thus subject to active monitoring. This way, errors can be immediately corrected and the translate5 installations can be updated.to the top

Is translate5 secure?

The question whether an IT system (like translate5) is secure, can only be answered by experienced developers after reviewing the source code of the software. This question is asked regardless of operating system, used server infrastructure, or programming language - and is solely the result of the way the application is programmed and the IT infrastructure used by the application is managed and serviced.

translate5 and other Open Source applications have - compared to closed applications - the advantage that each developer can view our source code. Unlike fee-based, proprietary applications, you or third parties assigned by you can thus judge for yourself/yourselves, if translate5 is based on a good and secure source code. You can even help locate errors. As a result, open source applications are frequently more secure and more stable than proprietary software.

The second and at least just as important aspect in the security of translate5 is the used server base. Management, currentness, and configuration of this server base are crucial here. translate5 relies on PHP5 on the server - the programming language used most frequently on the web. Since PHP is widely distributed and the PHP development team at Zend (the company behind PHP) has many years of experience, PHP has a very high standard in potential security. It depends on the way PHP is installed and managed, whether this high standard is also utilized by the PHP installation. We recommend the use of translate5 with PHP and Apache under Linux on a dedicated server. This server should be serviced by experienced web managements. Installation under Windows is also possible.to the top

User Management & Registration

User Management

translate5 includes its own user management. A user with the role as a project manager can create, process, and delete users. First name, last name, user name, e-mail, password, and system role(s) can be assigned to the user. System roles define the rights of the user in the system (not in the workflow). Certain workflow roles require certain system roles.

A project manager can reset the password of a user himself/herself. If the password is reset, the user receives an e-mail with the request to reset his password himself/herself (see below).to the top

Registration & Resetting Password

A registration mask limits access to translate5. If a wrong password is repeatedly entered, registration is blocked for 24 hours.

A user can reset his password at any time. To do so, he requests the appropriate link via e-mail, which includes an explicit hash value. With this link, he can reset the password - but only, if he activates the link in same browser within 30 minutes after his request. Otherwise, the link expires and must be requested again.to the top

Modularity of translate5

The source code of translate5 is based on a modular design. This ensures that individual components of translate5 can also be used individually. This initially applies to the base library "ZfExtended", which is also used in other projects of MittagQI. But this also applies to the central editor component.to the top