Italic (added manually) is another Tags too.
Let me check it out.

myItalicTags are "formatting tags" so if you configured like this I have nothing to say anymore - all are fine with me;

Unknown said:

Yes, I could do that indeed but then SDL wouldn't report the one italic tags that have been deleted, which I need to know.

Then for example set the Tag Verifier options accordingly... e.g. turn off only reporting of ADDED tags and keep the reporting of DELETED tags turned on... or let Studio report everything and use your own brain and some logic over the the reported messages, e.g. sort the messages by clicking on the column header and then selectively ignore (i.e. remove from the list) only those message you want (rightclik on the message and see the menu... the "Ignore All Messages" command ignores actually all messages of the same (righclicked) "kind", not ALL of them...
Or similar...

Unknown said:

I just don't know how to tell SDL that Italic from the source and italic from the formatting options in the editor view are all fine with me if they are applied to the same word. As long as an italic word in the source is translated in italic in the target, it's ok.

This simply CANNOT be told Studio in any way... There isn't any artificial intelligence built-in, so Studio cannot recognize that the italicized target word is exactly the translated source italicized word and not any other one.

The tag verification uses simple common-sense logic - all tags present in source are expected to exist in target. Period.
Any exceptions from this simple rule must be checked using additional layer of logic at the user level.

Note (mainly because of Hoon "Mister Smartypants" Kim's weird notes which will surely follow ;-) ):
Of couse this all is about the default built-in tag verification.
If you would be able to develop your own verification plugin, you can build any additional logic in it... but that's a totally different story, not applicable  to majority of common users.

Hi Evzen,

Thank you for your answer :) I don't know how to "quote", so I'll just copy-paste the parts I need to answer to.

sort the messages by clicking on the column header and then selectively ignore (i.e. remove from the list) only those message you want (rightclik on the message and see the menu..
Yes, this is what I am doing at the moment. But SDL needs about 10seconds to process each "ignore"-setting, and I have over 8.000 messages to deal with....

Studio cannot recognize that the italicized target word is exactly the translated source italicized word and not any other one.
Sorry, I must have been very unclear: SDL reports lots of segments as "italic tag missing" although there is indeed an italic tag both in the source AND in the target. The only difference is that the translator didn't use the QuickInsert function to insert the italic tags from the source to the target, so I had to italicize everything afterwards, using the "italic"-function in the editor.

It seems SDL does not recognize both formats as one "italic"-format, but as 2 different formattings although they look exactly the same and bear the same tag codes. I don't know why. As a result, I got those 8.000+ error messages, where more than half of them are in fact no issue at all. My point was how to tell SDL that italic is italic, no matter if it has been copied from the source or edited afterwards.

The tag verification uses simple common-sense logic - all tags present in source are expected to exist in target. Period.
Yes, and it would be very nice if it would indeed work that way, but it doesn't! SDL reports missing italic tags where there are in fact italic tags in the target as well as in the source. It wouldn't be an issue to read each and everyone of them if it were a smaller text - but it's another game entirely with a 10.000 segments-file full of tags (about 30.000 in all). 

Hi Evzen,

Thank you for your answer :) I don't know how to "quote", so I'll just copy-paste the parts I need to answer to.

sort the messages by clicking on the column header and then selectively ignore (i.e. remove from the list) only those message you want (rightclik on the message and see the menu..
Yes, this is what I am doing at the moment. But SDL needs about 10seconds to process each "ignore"-setting, and I have over 8.000 messages to deal with....

Studio cannot recognize that the italicized target word is exactly the translated source italicized word and not any other one.
Sorry, I must have been very unclear: SDL reports lots of segments as "italic tag missing" although there is indeed an italic tag both in the source AND in the target. The only difference is that the translator didn't use the QuickInsert function to insert the italic tags from the source to the target, so I had to italicize everything afterwards, using the "italic"-function in the editor.

It seems SDL does not recognize both formats as one "italic"-format, but as 2 different formattings although they look exactly the same and bear the same tag codes. I don't know why. As a result, I got those 8.000+ error messages, where more than half of them are in fact no issue at all. My point was how to tell SDL that italic is italic, no matter if it has been copied from the source or edited afterwards.

The tag verification uses simple common-sense logic - all tags present in source are expected to exist in target. Period.
Yes, and it would be very nice if it would indeed work that way, but it doesn't! SDL reports missing italic tags where there are in fact italic tags in the target as well as in the source. It wouldn't be an issue to read each and everyone of them if it were a smaller text - but it's another game entirely with a 10.000 segments-file full of tags (about 30.000 in all).