Quote:
Yes, it is a training issue, but everyone makes mistakes as well, so even the most rigorous person may forget to close **some open bracket** in a sentence, and in my case, may forget to add the closing tag where it belongs... Got it?
And, as I said, I do not want to use ONE type of "tag", as it might be used as an internal code by translation software. This is a risk I don't want to take, as I do not know/use/have control on the software used to produce the Word file. Let's assume one moment that ## ## is an internal tag used by such software. What would happen to the file once it is exported into Word? I have absolutely no idea!
I will tell you one thing...you would be much much much much better off if none of this commenting "tagging" was done in your translation software, and ALL of it was done in Word.
Quote:
Now, though your code is great, it replaces all occurrences blindly without doing any order check (to make sure that there is no strOtag in between a correct pair). I am a bit concerned by this issue, and I'd like to find a nice fix for it. Maybe the solution would be the check in the .Find result if the string strOtag exists, in which case I could highlight it in red or any other color, and skip to the next occurrence... Any better idea?
I do. Do all your tagging in Word to start with.