Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Description

Instant-translate is translate5 api interface which can be used for translating text and files using the translate5 language resources (term collections, translation memories or machine translation engines).

Available language resource for instant translate are the assigned resources of a customers of the current logged-in user.

For translating files, the file-extension must be configured accordingly.

Translate text with translate5 language resources .

URL:

/editor/instanttranslateapi

Available Methods:

GET

Specialities:

To be able to search for a text, there must be available language resources assigned to a customers of a user

Availability:

-

Translate text resource Layout

Name

Type

Info

text

string

The string to translate.

source

string

The source language to translate from. Must be valid rfc5646 code.

targetstringThe target language to translate to. Must be valid rfc5646 code.

Translate a file with translate5 language resources

Please ensure that:

  • the filetype is supported (e.g. by Okapi),
  • TermTagger is running,
  • LanguageResources for the desired language-combination are available (order of their application: first termCollections, second TMs, third MTs).

Translating files can take a while.

URLMethodsParametersDescription

/editor/instanttranslateapi/fileprepare

POST

fil: multipart/form-data; the file to translate.

source: string; the source language to translate from. Must be valid rfc5646 code. When no domainCode is provided this is mandatory.

target: string; the target language to translate to. Must be valid rfc5646 code. When no domanCode is provided this is mandatory.
domainCode string Unique sdl language cloud engine id(domainCode).

Step 1: Prepare a task for import of the file and run the pretranslation.

Response (example): {"taskId":"539"}

/editor/instanttranslateapi/fileimportGET

taskId: int; the taskId given in the repsonse of step 1

Step 2: Run the import of the task with the pretranslation.

As long as the import is running, the response in step 3 for this file will say "isImporting" instead of returning the download-link. You might need to repeat step 3 until you get the link.

The translated files are available until their configured lifetime is over; then they will be removed automatically.

Response (example): {"taskId":"539"}

/editor/instanttranslateapi/filelistGET

Step 3: Get a list of all pretranslations that are currently available for the InstantTranslate-user including their downloadUrl.

Response: allPretranslatedFiles with the data for each pretranslation-file:

  • array[taskId] = array(taskName, downloadUrl, removeDate)
  • downloadUrl: 'isImporting' | 'isErroneous' | 'isNotPretranslated' | url (the url starts a common task-export; the translated file is included in the exported ZIP)

Configuration of InstantTranslate

runtimeOptions.LanguageResources.searchCharacterLimitmap
Maximum character per language resource allowed for search. The configuration key is the language resource id, and the value is the character limit. Ex: {{"1": 100},{"2": 300}}
runtimeOptions.InstantTranslate.pretranslationTaskLifetimeDaysint2How many days do you want to keep pretranslated files before the system removes them?
  • No labels