The following list shows the important features of translate5 in bullets without detailed explanation.

It aims at giving an overview of the software and is addressed to people, who know how translation software and translation business works.

General features

• Tabluar views of translate5 (including editor) 
  • are sortable and filterable. Filter can be set as AND filters in several columns.
  • are "endless" grids, which means you can scroll through the table from the first to the last entry with great performance, even with 100000 entries in a tabluar view (implemented for editor; soon also for other views).
  • Order of columns can be changed by drag and drop
  • Columns can be hidden and shown
  • default column order and visibility can be configured on system level for task overview and user overview

Editor

• All general features for tabular views (see above)
• If language resources are assigned for all assigned: 
  • Concordance search (can be narrowed to single language resources(
  • Fuzzy matching
• In-Context review
  • with visualReview plug-in active
  • available for practicably all file formats (e.g. MS Office, Indesign, FrameMaker, HTML, etc.)
• In-Context translation (coming soon)
• In-line Track Changes
  • with TrackChanges plug-in active
  • MS Word style track changes
  • different background colors for different users
  • works across workflow steps
• Cascaeded file tree with folder hierarchy for the files of a task and the reference files of a task
  • files sortable, new sort order is respected on export
• Potential usage as integrated editor in other applications without task overview etc. 
• Great performance with large tasks - 100000 segments and 1000 files in a tasks work seamlessly
• Optional pivot language (if reviewer does not understand German, but an English translation is available)
• Search and replace (with replace all, wildcards, regular expressions and case-sensitive options)
• Comments on segment level, filterable for content, date and creator of comment
• Altering of font size
• Keyboard short cuts for all important user interactions
• Auto propagate of repeated segments on saving (configurable if it is down automatic, asked each time for which segments it should be done or never done)
• full tag and short tag mode; hide tags possible with editing disabled
• Bookmarking of segments
• Autostatus column shows 
  • workflow step, in which segment was changed the last time
  • if segment was edited or just saved without changes or auto-propageted
  • if segment is untranslated
• Automated QA checks on segment level:
  • Terminology check against translate5 TermCollections
  • Empty segment check
  • Tag check (potentially configurable, that segment can only be saved without tag errors or only with different whitespace tags than the source; for review tasks the comparison is done against the translation at import time)
  • Spell-, Grammar and Style-Check based on languageTool (Open Source)
• Manual QA based on
  • DQF/MQM on subsegment level (defineable on system and task level; error types in cascading levels)
    • including DQF/MQM statistics (visualized and exportable as XML)
  • QA flags on segment level (defineable different flags on system level)
  • Manual status (defineable different status on system level)
• Meta data columns (by default visible) for
  • Segment no. in task
  • match rate in TM system
  • match rate type (shows, where a segment content comes from)
• Meta data columns (by default hidden) for
  • QA flags
  • Manual status
  • last editor
  • edited at workflow step XYZ
  • target language at import time (for review tasks)
• Optionally add white space tags (non-breaking space, tab, soft return)
• Display of number of segments in current filtering
• "Hovering open segment": If segment is opened, it is possible to scroll under it all segments of the table and also filter and sort these segments
• Segment actions:
  • Save and jump to next in workflow
  • Save and jump to next
  • Save and jump to previous
  • Abort and jump to next in workflow
  • Abort and jump to previous in workflow
  • Abort and jump to next
  • Abortand jump to previous
  • Refocus open segment in context (see "hovering open segment")
  • Reset segment to non-edited state
• Switch of default modes for font size of and visible columns and panels (normal mode, details mode and simple mode (the latter only available with visualReview plug-in active)
• Multiple target language columns (if imported like that in CSV format; see "task overview")

Task overview

• All general features for tabular views (see above)
• Which task actions are available for a user depends on the rights a user has
• Add tasks:
  
  • Importable file formats:
    • All file formats supported by Okapi Framework through Okapi integration
      • An Okapi bconf file can be passed in a zip import package for translate5 to adjust Okapi filter settings (like ignoring Excel cells with certain colors, configuring xml, etc.)
    • SDLXLIFF
    • XLIFF 1.2
    • OpenTM2 XLIFF
    • Across XLIFF
    • Star Transit bilingual file pairs
    • Bilingual CSV (also multiple target language columns possible, that lead to multiple target language columns in translate5 editor, usable for comparing different translations, e.g. with DQF/MQM)
  • decide, if
    • 100% should be editable
    • segments locked in original xliff should be editable
    • source language should be editable (does not export in all export formats, mainly made for CSV so far)
  • Add meta data
    • source language
    • target language
    • customer
    • order number
    • delivery date
    • order date
  • Optionally use pivot language (if reviewer does not know the source language, but e.g. an English translation exists)
• Associate language resources to tasks
  • All language resources are selectable, that are associated with the same source language, target language and customer as the task is
  • Decide if match analysis should include internal fuzzy matches (fuzzy matches produced by segments that are only translated while the task is translated)
  • Decide if pre-translation should be done against associated termCollections and Translation Memories and if yes up to which match rate
  • Decide if pre-translations should be done against assoiated MT resources (only for segments still empty after TM pre-translation)
• View analysis; export analysis as excel
• Assign users to task
  • Multiple users / workflow step
  • Workflow roles 
    • translator
    • reviewer
    • check of review
  • Configure the editor more in detail for users or roles
    •  which source and target columns can be seen
    • if the column name of source and target columns can be read
    • if only DQF/MQM tags can be set, but the content can not be changed
    • if non-editable target columns (target text at import time) can be seen
• Export
  • task in original format
  • task with diff compared to the import stage (main use case: sdlxliff with change marks, that work with Trados Studio track changes)
  • task as xliff 2.1 with reflection of translate5 in-line track changes (who changed what when) and segment meta data (please note: this track changes is complete workflow based, the "diff to import stage" in the previous bullet does not reflect changes within the translate5 workflow steps)
  • MQM statistics as xml
• Change a number of task properties, e.g. task name, project manager, delivery date, delivery date (real), order date (only with PM rights, or if special rights are configured in ACL
• See and filter task meta data
  • source, target and pivot language
  • customer
  • task status
  • task name
  • order number
  • number of words in a task
  • associated users with their workflow roles and workflow status (task table can currently not be filtered along this column)
  • associated language resources (task table can currently not be filtered along this column)
  • reference files available
  • terminology associated
  • project manager
  • order date
  • delivery date
  • delivery date (real)
  • number of files in a task
  • 100% matches can be edited
  • task is a translation or review task
  • locked segments in imported xliff are also locked in task
  • source language is editable

Users

Manage users

• Create and delete users
• Associate users to customers
• Set preferred GUI language of user
• Set system roles of users (do not mix up with workflow roles)
• Set password of user
• Set default languages of this user. When a task is created, users for whom a default language is set are automatically assigned to this task as proofreader.
• A parent user can be set. This user only has any effect, if in the database-based ACL for a PM role is set, that it is not allowed to see all users. If this is the case, a user can only see those users in the user management, for whom he is the parent user. And in addition all users that are children of his children users and so forth.
• On database level it can be configured, if it is allowed to edit or delete a certain user

Change log plug-in

Database-based features

• Detailed configuration of rights and roles possible in translate5 ACL table
• More than 200 options for configuration on system level for translate5 in Zf_configuration table
• "Materialized view" of a task for fast performance on reading segments
• Saving of complete segment history (each editing step of a segment is saved in a history)
• Saving of the time it takes for a user to edit a segment

API

In general: All actions that can be done by a user in the GUI can also be automated via translate5 REST API (by design)

Please note: This feature documentation is by far from complete.

For some features currently you have to screen through other spaces of this wiki, others are not documented at all.

A detailed overview what is done and changing in translate5 gives the translate5 JIRA issue tracker.

Help to complete this list of features is very welcome.