Hello Stefano Bellezza,

Apologies for the delay in responding.  First of all I tried to verify this in 2011 but that version won’t open these mif files at all.  So I used 2014 and this allowed me to reproduce your problem.  In 2014 I see this:

In 2017 this:

Note that you can see the tags if you use the display filter in the Review ribbon and filter on All Content as I have done here.  You can also drag them into the target segment if necessary and this may be helpful while we investigate this so you can at least place them where you like in the target text.

Now, if I compare this with a “good one”:

The problem is now reasonably clear to me.  I believe Studio may have been “fixed” to move opening and closing tag pairs externally if they are empty because they are not needed, and as they are preceded in this case by a placeholder tag Studio is assuming that all of the tags can be moved out of the way so you don’t have to deal with them.  Unfortunately in your case you do.  So the superfluous bold tags seem to be causing the movement of the tags outside the translatable area.

So whilst I think this behaviour is intentional I will discuss it with the development team to see what they think.  In the meantime try dragging them in like this:

Hope that's clear and you have a bit of a workaround for now until we determine whether this is anything we can sensibly fix with an option or not.  I can imagine there are occasions when you'd prefer these tags to be moved away, so it's probably a tricky one to get right for everyone without making this an optional thing.

Regards

Paul

Thank you, Paul. I didn't realize that there was an "All Content" command - and trust me, I've been looking for it for a while!

The only problem I see with your workaround is that I have not been able to similarly fix the source segment (Studio categorically refuses to let me drag the tags in, no matter how many times I tell it to unprotect tags and let me edit the source), so I would be committing TUs where source and target are not perfectly aligned (as rightfully pointed out). Not very risky in this particular instance, but you can see how it could become dangerous under different circumstances. Anyway, we'll make do with it for the time being.

Unknown said:

The only problem I see with your workaround is that I have not been able to similarly fix the source segment (Studio categorically refuses to let me drag the tags in, no matter how many times I tell it to unprotect tags and let me edit the source), so I would be committing TUs where source and target are not perfectly aligned (as Christine Bruckner rightfully pointed out). Not very risky in this particular instance, but you can see how it could become dangerous under different circumstances.

Indeed, and completely agree.

Unknown said:

The only problem I see with your workaround is that I have not been able to similarly fix the source segment (Studio categorically refuses to let me drag the tags in, no matter how many times I tell it to unprotect tags and let me edit the source), so I would be committing TUs where source and target are not perfectly aligned (as Christine Bruckner rightfully pointed out). Not very risky in this particular instance, but you can see how it could become dangerous under different circumstances.

Indeed, and completely agree.