Tried it out with simple file.
In my case, there is no error and there is no result (Italic) too.
Looks like a bug, it should be fixed.

regards

Try like this.
testing) at SDL Trados Studio add Italic some word, and see what is happening at MS Word
workaroud) at MS Word add the same tag pair (exactly same color/size/font etc..) when you "Find and replace" it/them.
In my case it worked

- turn "Track changes" off
- what is retrofit ? I tested with regular
- "Bold" looks dumb too. Very nice..

Erratum: it works very well... until I try to save my work. I get the error message that the starting tags don't match, but I don't know why... Any idea what I could do to fix that?

Good.

I just have tried and failed making VBA to do the same thing.
Made the same tags successfully at MS Word review file though,
they are refusing to be a proper tags at SDL Trados Studio when updated.
I guess, there are some hidden things to be handled that I do not know at the moment.

It does not matter.

Have a nice Sunday.

I found the main reason why my 1st workaround didn't work.
My whole idea and its implementation in VBA are good enough.
But, the intrinsic limitations/characteristics of sdlxliff refusing my workaround successfully finished.

A segment must have at least one Italic tag originally (that means, at SDL Trados Studio step not exported review MS Word step afterward).
If you have at least one Italic tag in your segment, you could add Italic tag at it without any kind of limitations. But, If you do not have it at original step, forget about it. That's impossible.

I'm not going to call it a bug. Because it is not even a bug.
For the purpose of changing this kind of tiny stuffs, Exporting and Importing whole file
(and more worse, in this case the file itself is just Huge) is silly, waste of time. 

아무도 관심 안 갖는 지꺼리, 베린 시간이 아까워서 몇 글자 남깁니다. 

Maintenant c'est fait parfaitement.
Jetzt ist es perfekt gemacht.

Unknown said:

아무도 관심 안 갖는 지꺼리, 베린 시간이 아까워서 몇 글자 남깁니다. 

Maintenant c'est fait parfaitement.

I'm wondering - are you perhaps the same individual as "Kelly Edward" who used to flood the forum by weird posts between September and December 2017?
Your rhetoric sounds very similar.

If you are wondering about these two lines.
The first one is "This is just record of few lines for my precious time even though nobody is interesting".
The latter one is... nah use Google. Because, I made it from there (Korean -> French).

looks like, I see a corrupted Policeman here.

Once, I was in Praha.
That's nice city.
If I had a chance I'll be there again for sure.

Have a nice day

I believe You have solved this problem perfectly using my PlugiIn already.
Did I understand your comment wrongly ?

In that case there should be no more 'serious' comment about it between you and me.
But, looks like you are still serious about it.
I'm confusing.

1. I showed you two(2) workarounds
2. the 1st workaround revealed itself fail finally (I'll tell you about it technically later on)
3. the 2nd workaround (my SDL Trados Studio PlugIn), you have tested it and satisfied with it. Right ?

SDL Trados Stduio Editor View is just showing the file, "sdlxliff".
Talking about the Italic only, sdlxliff has three fold tier structures.
1st tier is central, located head of the file it is the only one in the file.
2nd tier is local-central, located at the head of each segment if it has Italic tag(s) inside of it. It is the only one in the segment.
3rd tier is pure local, located at the exact point it showing the user Italic. It has 1:1 corresponding so could be so many.

my 1st workaround is regarding the 3rd tier only(indirectly because you are in MS Word at that moment). Naturally, If the segment has Italic originally(that means, it has 1st/2nd tier already ready), it does not matter you added extra Italic 100 times or not. But, If your segment do not have Italic originally at all (that means, it does not have 2nd tier for sure, and probably neither the 1st tier too), you can do nothing, nothing at all. Even though my VBA codes (3rd tier) are perfect, when the review file imported back to SDL Trados Stduio, it make only Error at the first appearance of my Italic.

my 1st workaround is finished like this. Fail. That is why I wrote tier structure has "intrinsic limitations" or characteristics. Plainly to say, this kind of tier structure is too complicated, needlessly, I guess.

Ah, the 2nd workaround - my SDL Trados Studio PlugIn is dealing with sdlxliff directly, so you do not have to care about this silly structure.
It is just adding Italic and forget about the rest.
That is so easy and fast, Right ?

I recommend you to test with it before you post something if possible.
I myself keep this simple rule strictly always if possible.

You have questioned "from the scratch ?"
My answer should be "Yes, of course."

I'm attaching a jpg.
It shows screen of all the "a/e/i/o/u"s changed from normal (scratch) to Italic and goes back to normal (scratch).

regards

Hi Hoon Kim,

Yes it is indeed - it works wonder!! Unfortunately after all the changes I made successfully, SDL didn't want to save my work and sent following error message :

Do you happen to have any idea why?

Let me take a look at it.

Hmm, yeah, I found it too.

(I missed it, because I was not interested in 'Saving'.)