Hi Community,

I have an interesting case where the customer would like to record info in the TM about segments (metadata not on the file level, like in the TM custom field values / update settings, but on the individual segments)..

They work with RESX files, where each translatable value has a key (like metadata). It does not appear for translation, only the value.

So they have Home as they key which has Home as value, for example. But they have cases where House is the key which has Home as value, for example. And only 'Home' appears for translation in both cases, but they have different context.

It would be important for them to be able to distinguish between the different context, and not apply the same translation where the context is different. So when Home is in the context of House, it should not apply the same translation as when it was in the context of Home. Hope it makes sense?

I tried testing it, changing the key (context) in the file but having the same value, but Studio gave the same translation, even when the key was different. I understand the translation memories record further details than what is visible in the metadata (e.g. information of the preceding and succeeding segment), but it does not seem to register this kind of data.

What do you think? Have you came across similar issue before?

Thank you,
Greta