Rihei Li

And what exactly is the problem with this?  What would you like to see there instead?

Is there any option can keep the real tags in the .TMX files, like <b>, <cf underlinestyle="single">, and so on, not only <bpt xxxx>, <ept xxxx>

Rihei Li

Studio does’t need this, and I’m fact I’m not aware of another translation tool that needs this either. The type of formatting that replaces the tag from the TM is determined by the source document, not the translation memory.

What are you using the TMX for? Just interested as I’ve never seen a TMX with this kind of markup before.

I use another tool for translation, for other tool's TMX file, it shows like below, real tag contents displayed

<bpt i="1" x="1">&lt;cf underlinestyle=&quot;single&quot;&gt;</bpt>

<ept i="1">&lt;/cf&gt;</ept>

<bpt i="2" x="2">&lt;cf bold=&quot;on&quot;&gt;</bpt>

<ept i="2">&lt;/cf&gt;</ept>

Hi Paul, 

Thanks for your reply, regarding your opinion, may I understand below:

If we have one string "I <b>like</b> it" was translated and imported into SDL TM, and next time I need translate another similar string "I <i>like</i> it", the match will be 100%, right?

Rihei Li

Correct.  For example, I created four files (xml, html, MIF, DOCX) with two lines in each.  Same text but messed around with the tags.  I translate the first sentence, confirm to my new TM and the rest are all autopropogated as 100% matches:

Paul, thanks for confirmation, I've also test like yours and same result with you.

But I've seen one option about penalties, even I change them to bigger numbers, the match rate has no impact, so I'm wondering if the formatting penalty was not suitable for these situation?

Rihei Li

That's a good question... but this feature is about actually tag types and not the internal formatting they might represent.  So for example:

I changed the tags in segment #2 so they are now placeholders and not tag pairs.  The result being a 9% penalty because there are now 6 new placeholder tags and it's missing 3 tag pairs... 9 in total.

Make sense?

It's a poor description in the help I think... unless it's really a bug and I'm wrong!!  But given the way Trados Studio works and that it really doesn't care about what's inside the tags, and given it has no clue whether the internal tags of the different filetypes really mean the same thing or not, I think I must be right :-)

Paul, it's clear, thanks for your reply.

Paul, it's clear, thanks for your reply.