...
- Importing a task with terminology into translate5 for editing
→ this is not covered here, since that terminology currently can not be searched in the termportal. - Provide TBX files with the terminology → use file-system based import
- Get TBX files from Across via crossApi
Depending on which way the terminology should be imported, the TermImport Plug-In must be configured.
The configuration files are located Structure of this docu:
| Table of Contents |
|---|
File-system based term import
It is also possible to To import a TBX file files from the file system into translate5s termCollections use the file-system based import.
For this a configuration file maps the TermCollection name with the file name of the TBX and the collection name with the customer number. In addition the config file defines the import directory, where the files are read from.
...
| Code Block |
|---|
;;;; ATTENTION: the below variables need to be placed above the areas [FileMapping] and [CollectionMapping] ;import directory of the tbx files importDir=/var/www/translate5/data/tbx-import/filesystem/; ;mergeTerms: Allowed values: true or false. ;If this is true, terms will be merged as described at https://confluence.translate5.net/display/TAD/Term+Collection. ;Otherwise all terms will be added to the termCollection, if the ID in the TBX does NOT exist already in the DB ;when the ID of the termEntry of the TBX does already exist in the DB, the terms of this termEntry will always be merged mergeTerms=true ;Deletes all termEntries in all listed termCollections, that have a modification date older than the listed one. ;Since every entry that exists in a TBX gets a new updated date on TBX-import, even if it is not changed: Simply set this date to yesterday to delete all terms, that are not part of the current import ;The updated date is a date internal to translate5 and different from the modified date of the term, that is shown in the interface deleteEntriesModifiedOlderThan=2018-05-01 ;Deletes all termEntries in all listed termCollections, that have a modification date older than the the start of the current import. ;possible values: true or false deleteEntriesOlderThanCurrentImport=true ;Deletes all term proposals older then deleteEntriesModifiedOlderThan date. ;If the deleteEntriesModifiedOlderThan is not set, then the current date will be used ;The current date will be used also when deleteEntriesOlderThanCurrentImport is true ;possible values: true or false deletProposalsOlderThan=true ;;;; ATTENTION: the above variables need to be placed above the areas [FileMapping] and [CollectionMapping] ;mapping between tbx file and term collection name [FileMapping] Term.tbx=exampletermCollection; Term1.tbx=exampletermCollection; Term2.tbx=exampletermCollection; example2.tbx=exampletermCollection2; example3.tbx=exampletermCollection3 ;mapping between term collection name and customer number [CollectionMapping] exampletermCollection3=1000; exampletermCollection2=1003; |
...
| Code Block |
|---|
crossAPIurl=http://win.translate5.net
crossExportFilesDir=/var/www/translate5/data/tbx-import/crossapi/
apiUsername=crossapi.user
apiPassword=pass
;mergeTerms: Allowed values: true or false.
;If this is true, terms will be merged as described at https://confluence.translate5.net/display/TAD/Term+Collection.
;Otherwise all terms will be added to the termCollection, if the ID in the TBX does NOT exist already in the DB
;when the ID of the termEntry of the TBX does already exist in the DB, the terms of this termEntry will always be merged
mergeTerms=true
;Deletes all termEntries in all listed termCollections, that have a modification date older than the listed one.
;Since every entry that exists in a TBX gets a new updated date on TBX-import, even if it is not changed: Simply set this date to yesterday to delete all terms, that are not part of the current import
;The updated date is a date internal to translate5 and different from the modified date of the term, that is shown in the interface
deleteEntriesModifiedOlderThan=2018-05-01
;Deletes all termEntries in all listed termCollections, that have a modification date older than the the start of the current import.
;possible values: true or false
deleteEntriesOlderThanCurrentImport=true
;Deletes all term proposals older then deleteEntriesModifiedOlderThan date.
;If the deleteEntriesModifiedOlderThan is not set, then the current date will be used
;The current date will be used also when deleteEntriesOlderThanCurrentImport is true
;possible values: true or false
deletProposalsOlderThan=true
;mapping between across export template and term collection
[FileMapping]
template-1.export=exampletermCollection
;mapping between term collection name and customer number
[CollectionMapping]
exampletermCollection3=10001;
exampletermCollection2=10002;
exampletermCollection=123456789; |
...