Hi Pascal Zotto , would it make sense to markup content that you don't want translated with inline locked tags?

Hi Patrick Andrew Hartnett,

not really as it has to happen on the fly in our translation provider plugin with the help of term lists or rules that we partly set up as they occur during translation but on the other side we can influence the code of the plugin before launching it with Trados to tell it how to handle these strings. So it has to happen during translation within the plug-in and not at file preparation level before translation even starts.

But for some languages inline locked tags also makes no sense as they may need to be slightly adapted to grammar after "translation" against TM or MT process.

Hi Patrick Andrew Hartnett,

not really as it has to happen on the fly in our translation provider plugin with the help of term lists or rules that we partly set up as they occur during translation but on the other side we can influence the code of the plugin before launching it with Trados to tell it how to handle these strings. So it has to happen during translation within the plug-in and not at file preparation level before translation even starts.

But for some languages inline locked tags also makes no sense as they may need to be slightly adapted to grammar after "translation" against TM or MT process.

Hi Pascal Zotto 

You're going to have to figure out how the mark up the content that you don't want transalted.

From what you saying, you can't include lock tags during the preparation phase and remove them when you receive the translation from the provider, correct?  I'm not understanding this as it's your translation provider and you have access to prepare the content before translation and then adapt it again once you receive the translation response.

You could also think about replacing the content that you don't want translated with a placeable and then convert the placeable to text from the translated content?

HiPatrick Andrew Hartnett,

because the rules can be changed on the fly, during translation to optimize results for all translation provider queries (and for all used translation providers at once) after the segment where you discovered you need a new rule to get better results. In that case you add a new rule or edit an existing one.

Sometimes the rules are NOT known before files get prepared and we also don't use the inbuilt Trados kategories (Date, currency, variables, aso. from TM settings). They are quite often a pain in the a$$ as they offer wrong results (or need to be set for each TM individually) so we override them with our settings to get more correct results. Therefore most inbuilt tagging options might not work.

With our tool you create the rule globally and it works for all translation providers (TM, MT, aso.) that have that specific rule collection implemented.

e.g. for one of my last translations I had a name of a machine that was quite straightforward (2 words with a hyphen in between), nevertheless MT managed to offer me around 10 different (often nonsense) translations for it... oO

So I had to adapt the rules to get it correct all the time and to adapt the term to grammar rules. As the files were also prepared by the client you guess I could not even have implemented interal locked tags or anything else when importing the project, even if I would have known the rules to be used before.