I've given clean example just to illustrate problem with the function. In real life its never this simple, see below:

As you can see quoted UI references can be in any location of the sentence, thus simple concatenation wouldn't work. Furthermore, these steps would never be approved by translation agencies, because usually there is a translator->proofreader->second editor->in country reviewer involved in the process, where any person may change any part and just expect that Auto-propagation function apply his/hers edits throughout the document.

I've given clean example just to illustrate problem with the function. In real life its never this simple, see below:

As you can see quoted UI references can be in any location of the sentence, thus simple concatenation wouldn't work. Furthermore, these steps would never be approved by translation agencies, because usually there is a translator->proofreader->second editor->in country reviewer involved in the process, where any person may change any part and just expect that Auto-propagation function apply his/hers edits throughout the document.

Good morning.
I just spotted an issue in a file am working on and I wonder if this is also related to a faulty auto-propagation. It is related to a segment that starts with a number value but what is odd is that what changes is the text and not the number. See below:

Even though it mentions that the translation is a Context match, in the translation memory I am working with, both central and project TM, this translation does not exist. The one that does exist is 1000 miles = 1.000 millas, and this segment also occurs in this same file only a few segments down. Have you noticed this kind of issue before?

Thanks, Sónia

Good morning Sónia, that's an interesting one.  Looks buggy to me but I will check with the team here and let you know.  I did a quick test like this:

I confirmed #1 and this autopropagated #2 which had the same number value but a different unit.  This is clearly incorrect behaviour, but it's also explainable I think.  If you put the cursor into #1 you see this:

Note that the entire number and it's unit is recognised as a single placeable.  When you go to #2 then "1000 km" is also recognised as a single placeable and as you translated this previously Studio just says, ok here's another placeable with the very same number so I'll do what I did last time.  It seems to be ignoring the unit and just reading the number.

I think that's a pretty loose explanation, because if it was consistent I would have expected "1234 miles" and "1457 km" to do the same thing which it doesn't.  It onoly does this if the numbers themselves actually match.  But I think it's got something to do with this.

I'll let you know what the team have to say and what we can do to resolve it permanently.

In the meantime I think the best approach is to not change "miles" to "millas" as you translate.  Rather allow Studio to get the numbers right and the units wrong in a consistent way and then at the end of the translation just do  global search & replace in one go.  This will save you a lot of headaches and it'll be much faster.

Regards

Paul

The problem is that “miles” shouldn't be part of the placeable. It's a unit, yes, but not a symbol like “mm” or “km”.

I tested it in Studio 2014 and same thing.

... Jesús Prieto ...