• State Verified Answer
  • Replies 6 replies
  • Subscribers 433 subscribers
  • Views 8077 views
  • Users 0 members are here
Options
Related

"Internal error: Multiple tags with the same ID Italic have different start tag properties"

David Burnett

Help! I am currently in the middle of a large Trados Package. Yesterday, I started getting this error message. I have a tight deadline, but now I cannot save my work. I looked over the various solutions provided for this error and it seems that uninstalling CU8 is the best option. Will I lose my current work if I revert to CU7? Where do I get CU7 from? How do I install it?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    "Internal error: Multiple tags with the same ID 'Bold' have different start tag properties" - My error message is actually not 'Italic' but 'Bold'
  • 0 in reply to David Burnett

    Hi  ,

    It looks as though the package was created in an earlier version of Studio which is why you see this problem. I think you have three ways to deal with this if your client is cooperative:

    1. Revert to CU7. You do this by going to your Programs and Features in windows control panel, then Installed Updates and removing the latest update to Studio which is probably down at the bottom of the list (at least mine is)

    2. Save the source file from your project instead of the target (if you can) and then pretranslate this from your TM. Send your client the target file and your TM

    3. Send your client your TM for this file and let them pretranslate and save the files. If you added to a large TM then create a new TM, add it to your project and update your translation into it

    It's an unfortunate situation but hopefully something in here will help.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    There is another solution I forgot about that might be useful, depends how many tags are in your file. Go through your translation and remove all the tags for bold or italic that were placed using the Quick Insert. Then put them back using the tag from the source and not the Quick Insert. If you actually carry the tags over from the source you never have this problem anyway.

    You might also be able to apply them using Quick Insert as long as they are all using the Quick Insert in CU8 and not from a previous version. But I would go for carrying the source tags across as this is always a better way to work.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    I really appreciate the quick response, especially on a Sunday. I found this comment particularly helpful. Going through the documents that were giving me problems and identifying the tags that were causing the error messages took a little extra time, but I was able to save the package and complete the project without having to revert to CU7. Many thanks for for all of your help, Paul.
  • 0 in reply to Paul

    Hi Paul. You seem to have a good handle on how to solve this problem. I'm having the same problem as well, except with bold rather than italics. I'm using Studio 2015.

    Three of your options looked manageable to me, but I have questions about each of them:

    1) For the last solution you mentioned (quoted below), how do I identify which tags were placed using Quick Insert? There is quite a lot of bold text in the document and I really don't know where to start. 

    Paul said:
    Go through your translation and remove all the tags for bold or italic that were placed using the Quick Insert.

    2) If I wanted to use to solution of reverting to CU7 (what does CU7 mean, by the way?), how would I do this in Windows 10?

    Paul said:
    3. Send your client your TM for this file and let them pretranslate and save the files. If you added to a large TM then create a new TM, add it to your project and update your translation into it

    3) For the solution above, I would like to do what you suggested (create new TM, add it to my project and update my translation into it), but the only way I know of to update a TM is through Batch Tasks, which has to save the files before performing the Batch Task, am I right? So I'm not sure how to do this...

    I know this is a pretty old thread, but any help would be greatly appreciated! This is a 16,000 word project that I'm already falling behind on.

    Thanks in advance!
  • 0 in reply to Paul

    Hi again Paul. Not to worry, I think I have everything sorted out. In the end, I closed my files without saving (unintentionally, actually) and when I reopened them, I hadn't lost much work. I ran them through the TM again to update anything that wasn't saved, then I used your advice from a different post to identify any segments that didn't match the TM using the "Confirm and translate to next fuzzy segment" feature (since just before I had the problem, I had been tweaking earlier parts of my translation, but I couldn't remember what). Maybe the Autosave helped ensure that I didn't lose too much as well. Thank you for all your helpful posts!