Planned for Future Release

As part of terminology modernization in Studio, we can now plan this for a future release. No ETA yet but will be updated when we get there.

Termbase "Hitlist Settings" in the sdlproj file

Hello,

We need a modification on how the termbase hitlist is set.

We have several termbases in which forbidden terms are entered and the translator has to see this during his work. In all versions since Studio 2009, the settings can only be modified by the translator.

--> It would be ideal that Studio gets settings from the sdlproj. This would save configuration time for the translators and quality check time for the project management. Most important is that relevant term fields will be displayed in the terminology recognition pane. The way it is display (font, style) is not that important. To avoid conflicts with the settings a translator would have entered or changed himself, it would be good that Studio keeps the translator's own settings and simply adds the required fields given in the sdlproj.

use cases:
the field "status" has to be shown in a given termbase "X".
the sdlproj file in the translation package contains a corresponding setting that will be implemented in the user settings
Case 1: user has no setting for the termbase X yet --> Studio adds the field "status" to the setting for X, with default style and font
Case 2: user has already a setting for X: "definition" has to be shown --> Studio adds "status" in the setting for X". "definition" will still be shown.
Case 3: user has already a setting for X where "status" is shown in orange --> Studio does not change anything in the user settings

Is it something you could implement?

Kind regards

Sébastien

Parents
  • I can only second the comments above - governing the hitlist settings centrally as part of the project (and in my case I mean Trados Enterprise project settings) would be great to ensure that the translators or reviewers see the relevant fields in the term lookups without having to manually adjust the settings. Please implement this feature.

Comment
  • I can only second the comments above - governing the hitlist settings centrally as part of the project (and in my case I mean Trados Enterprise project settings) would be great to ensure that the translators or reviewers see the relevant fields in the term lookups without having to manually adjust the settings. Please implement this feature.

Children
No Data