Enables the usage of third party TM and MT systems in translate5. To support a MT / TM ti must be implement as a service in translate5. This is quite easy and usually a matter of days. Please contact us, if you need help on this.
Moses MT, OpenTM2, Google, Lucy, MS Translator, SdlLanguageCloud, NEC-TM (as Plugin), PangeaMT (as Plugin), and DeepL (as Plugin, only available for companies with a Support- and Development contract) are supported so far. For SDL GroupShare support please ask MittagQI.
TM/MT systems (or in general language resource) can be associated to tasks. In such tasks the user gets automatically found matches to the segments he is editing.
Also a concordance search is provided.
Provides access to the data of the configured language resources (TM,MT and termcollections).
GET / POST / PUT / DELETE
Non filebased langauge resource can only be added by the "admin" role. Users with the role "pm" can add filebased entries.
segmentId: integer; the id of the segment to be queried
|returns a list with query results, format see below|
|/ /search||GET / POST|
query: string; the string to be searched in the underlying service
|returns a list with search results, format see below|
|/ /download||GET||-||Returns the uploaded TM file - if any.|
|/ /import||POST||tmUpload: TM file uploaded as multipart/form-data||Imports the given TM file into the chosen Language Resource instance|
|/ /tasks||GET / POST|
Gives some status information about the tasks associated to a specific Language Resource.
Triggers a reimport of the chosen tasks into the TM.
Search / Query result format
Additional meta data of the returned match/search result, empty if not available.
|created||date||Meta data, creation time stamp of the returned match/search result|
Meta data, creator of the returned match/search result
|lastEdited||date||Meta data, last edited time stamp of the returned match/search result|
|lastEditor||string||Meta data, last editor of the returned match/search result|
matchrate of a found match, 0 for search results.
The found source text.
"loaded" wenn all is OK, "servererror" when we got an error in the queried service.
The found target text.
The queried Language Resource, just for reference.
Langauge-Resource Instance Resource Layout
|entityVersion||integer||GET only, set by server|
Custom name of the match resource.
|sourceLang||integer||GET / POST, non editable after creation; numeric DB id of the language|
|targetLang||integer||GET / POST, non editable after creation; numeric DB id of the language|
Custom color of the match resource in hexadecimal form, used in the GUI.
POST / GET, non editable after creation
POST / GET, only, set by setting a resourceId
GET only, set by setting a resourceId
POST / GET, can not be changed
|filebased||boolean||GET only, set by setting a resourceId|
|searchable||boolean||GET only, set by setting a resourceId|
|customerIds||array of integers|
POST, PUT: contains an array with customerIds to be assigned to that language resource
|customerUseAsDefaultIds||array of integers|
POST, PUT: contains a subset of customerIds of the above customerIds. The here referenced customers use this language resource by default.
Configuration of the Language Resources
|map||Available file types by extension per engine type. The engine type is defined by source rcf5646,target rcf5646. ex: "en-ge,en-us"|
|integer||3||Number of segments for which matches are preloaded (cached) in the front-end.|
|runtimeOptions.LanguageResources.moses.server||json array||[ ]||Moses MT related: List of available Moses Server, example: [""]|
|runtimeOptions.LanguageResources.moses.matchrate||integer, 0 - 100||70|
Moses MT related: Moses MT penalty value, used as default matchrate since in MT no matchrate is available.