| Warning |
|---|
| Be careful: NEC-TM integration with translate5 is currently deprecated. If you need the latest translate5 to work with NEC-TM, you might need additional development. In this case please contact translate5's development team at www.translate5.net. |
| Category | LanguageResource |
|---|---|
Purpose | Integrate NEC-TM as LanguageResource. |
Bootstrap Class | editor_Plugins_NecTm_Init |
| Type | Core plug-in (delivered with translate5 core) |
Please note
To use the NEC-TM translate5 plug-in you have to install NEC-TM itself as shown here. The NEC-TM translate5 plug-in only provides the connector between translate5 and NEC-TM, not NEC-TM itself.
Description
- For each translate5 instance only one set of NEC TM credentials is configured.
- username
- password
- a range of one or more top-level tags (these tags can only be set in the configuration on instance level of translate5)
- All this data is passed on authentication of this translate5 instance with NEC TM and thus only TM data below the top-level tags can be accessed (plus all public data). To ensure this is in the responsibility of NEC TM.
- On login and when the user enters the LanguageResources, translate5 queries NEC TM for all tags that can be accessed with the system credentials in NEC TM. The existing tags are saved in the translate5 DB. Tags that already exist in translate5 DB but do not exist any more in NEC TM are removed from the DB and from all language resource associations (current implementation: without any notification to the user or admin).
- When a new NEC language resources is added in translate5, all tags are offered to choose from that translate5 in step 3 above has gotten from NEC TM.
...
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.
Attention regarding user scopes: For every tag combination you want to use for language resources in translaste5, you have to create a separate user scope. For example if you have the categories / tags tag1, tag2 and tag3, that you want flexibly combine in translate5 for language resource usage, you need 7 scopes:
- Scope 1: tag1
- Scope 2: tag2
- Scope 3: tag3
- Scope 4: tag1, tag2
- Scope 5: tag1, tag3
- Scope 6: tag2, tag3
- Scope 7: tag1, tag2, tag3