Under Community Review

Make Variables (non-translatables) a resource

If an account has multiple Language Processing Rules, but the same list of Variables (non-translatable words) across the board, you have to manually upload the variable list to each Language Processing Rule whenever there's an update - for example, whenever a new product or feature name is added to the list.

It would be much more efficient to have a DNT (do-not-translate) list be a resource that you can add to the Language Processing Rules (or to a Project Template, or a Translation Engine), so that you only have to update the list once.

Screenshot of Trados Enterprise Customized Language Resources page, highlighting the 'Variables' column with 'Customized' status for both German and English languages.

Vera Malysheva
Parents

  • Hi Vera,

    This would be challenging technically and break older Studio versions. However, an alternative approach we could potentially do without impacting Studio, could be to allow copying Variable lists from one LPR to multiple others at once, so you only have to make the change in one place and then "apply" it. Would that work?

    Thanks,
    Luis

Comment

  • Hi Vera,

    This would be challenging technically and break older Studio versions. However, an alternative approach we could potentially do without impacting Studio, could be to allow copying Variable lists from one LPR to multiple others at once, so you only have to make the change in one place and then "apply" it. Would that work?

    Thanks,
    Luis

Children
No Data