The inputs of its users and the freedom of the development allow to develop outstanding features. For example:
- VisualReview: Review in perfect layout — for most file formats
- Inline MS-Word style Track Changes
- You decide, which TM / MT-engine you want to integrate (default OpenTM2 & Moses)
- 100.000 segments & 1000 files per task with high performance
- Terminology Portal (mobile ready!)
A complete bullet list of features can be found in translate5 Confluence.
VisualReview: Review in perfect layout — for most file formats
With the VisualReview plug-in for translate5 users can proofread or postedit content in perfect layout (PDF quality). Still the changes go directly back into your bilingual source.
Supported are most file formats: For example Indesign, FrameMaker, MS Word, MS Powerpoint, HTML, etc.
Full automated process integrations with other CAT-tools are possible and e.g. for Across already available.
Inline MS-Word style Track Changes
Inline MS-Word style Track Changes allow users to change content and see the changes marked analogous to MS Word Track Changes: Added content is highlighted, deleted content highlighted and crossed out.
A tooltip shows, who applied the change and when it has been applied.
For every user a different highlight color is used. This is true for several users in the same workflow step (you can assign the same workflow step to multiple users) and for users across workflow steps.
You decide, which TM / MT-engine you want to integrate (default OpenTM2 & Moses)
The flexibility of "match resource integration" (how we call it) is brought to the translate5 community by the translate5 crowdfunding from 2015 to 2017.
It allows to integrate new match resources (translation memory or machine translation engines) with very little effort in translate5.
The mechanism that integrates the match resources is completely independent from the resource - only an appropriate connector has to be build. If the API of the resource is good, the integration is done quickly. The integration of Lucy LT for example was a matter of one development day of work.
The match analysis and pre-translation mechanisms work in a way agnostic to the integrated resource: You simply select the translation memories you want to use (independent if they are OpenTM2 memories or others) and a translation is simulated in the background during the import process. The resulting match values are counted, including internal fuzzies (fuzzy matches that will be generated during translation).
100.000 segments & 1000 files per task with high performance
If you work on a task with 100 segments and 1 file or on one with 100.000 segments (or more) and 1000 files — you will barely recognize a difference in performance. Translate5 is as smooth and fast as always. (Imports of course take longer with more segments ;-) )
Terminology Portal (mobile ready!)
The terminology portal in its current stage is aimed at end users, who want to search for terminology. It can be used stand-alone (without using other translate5 components) by language service providers and industry companies alike (or of course together with other translate5 components).
At the current stage the maintenance of terminology is still meant to be done in other tools like [i]-match, Multiterm or crossTerm (we are looking for supporters for the next stage of the development!)
TBX files can be imported via REST-API, from the filesystem or directly from crossAPI.