Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Config nameValuesDefaultDescription


list[]NEC-TM Api Server; format: ["SCHEME://HOST:PORT"]
runtimeOptions.plugins.NecTm.credentialslist[]Credentials (licenses) to the NEC-TM API; format: ["username:password"]
runtimeOptions.plugins.NecTm.topLevelCategoriesIdslist[]These top-level categories (NEC-TM calls them tags) are always send to NEC-TM in addition to the categories defined with your current NEC-TM language resource. So if you set a category here, for all NEC-TM language resources that you create in your translate5 instance only segments will be send for your queries, that contain the categories, that are set here. This definition can stay empty.
Enter the NEC-TM's tag-ids here, not their tag-names! Example: ["tag391","tag840"].
runtimeOptions.worker.editor_Plugins_NecTm_Worker.maxParallelWorkersinteger3Max parallel running workers of the NEC-TM-categories-synchronization worker

Configuration of NEC-TM for translate5


You have to create only one user in NEC-TM per translate5 instancse. These user credentials you set in the translate5 configuration.

Tags (Categories in translate5's language)

All tags / categories, that you want to use in translate5 to sub-select data from your NEC-TM for certain language resources have to be created in NEC-TM.

If you want to use more than 1 translate5 instance with the same NEC-TM, but make the TMs of both instances completely separate, you have to create an translate5 instance specific tag and assign this tag to the runtimeOptions.plugins.NecTm.topLevelCategoriesIds of your translate5.

User scopes

For each tag / category, that you want to make use of in translate5, you have to create an own, separate user scope at your translate5 user in NEC-Tm and assign this tag (and only this) to this scope. If you use an translate5 instance specific tag (see above) you have to add this instance specific tag to each scope as well.

In translate5 you still will be able to define language resources to which you assign more than one category / tag. If you do so you will get only matches for segments, that have all categories / tags of your language resources.