Handling IDML files after migration to Studio 2017 - formatting tags

Question

Hello all, 
 While doing some migration tests from Studio 2014 to Studio 2017 for IDML files, I came up with the following question; hence I'd really appreciate your help on the following! 
 In the screenshot below (from Studio 2014) formatting tags were outside of the segments and as a result segment successfully pre-translated from TM. 
 
 For the same segment (in Studio 2017), formatting tags for an inexplicable reason have been put within the segment. As a consequence, we lose leverage as this segment drops to 99% match. 
 
 Hereunder you may find the IDML file type settings that we used. 
 
 I've done many tests playing around with the check boxes, unfortunately nothing seems to work. Neither have I found a workaround in wed. 
 Question: Since I used exactly the same source IDML file in both Studio 2014 and 2017, do you have any idea why Studio 2017 adds formatting tags within the segments? Do you have in mind any workaround? 
 Many thanks in advance!

Paul · Accepted Answer

Hi NLG GmbH 
 I can see there has been some confusion around this now because the number I gave you, CRQ-8380, is apparently related to this problem when the files are prepared through WorldServer. The notes refer to a fix for the filetype in the IDML version that was released with CU9 for Studio 2017. I just opened the test file you provided in CU9 and see this, with no formatting tags, so it seems as though your issue has been resolved:

Paul · Answer

Hi NLG GmbH , 
 
There has been a lot of tag handling fixes for IDML since Studio 2014, but I can't be sure which changes relate to your problem. Can I see your source file for testing?

Paul · Answer

Dear NLG GmbH , a short explanation of what I have to do with these files would be handy. If I'm testing leverage on an XML then a settings file would help, but you gave me two files and no settings file so I'm a bit confused. I thought the process would be open the source in 2014, translate in 2014 and store in a TM, then open the same source in 2017 and pretranslate from the TM to see the problem. But you just sent two source files one for 2014 and one for 2017. What am I supposed to test with these? 
 
Thanks

Paul · Answer

Thanks NLG GmbH , that is a better example and I see the problem. I don't know the history of why or even why these apparently inline formatting tags are now showing in 2017 when they didn't before so I have asked the question and will come back to you.

Paul · Answer

Hi NLG GmbH , I actually got the answer faster than I expected... it's a known bug and the team will be working on this shortly. I don't have any timescale or release vehicle yet but you can note CRQ-8380 as the number to follow up with so it's easier to check on progress.

Paul · Answer

Unknown said: How can we search for specific error codes in release notes? 
 That's another mistake I have made because you can't! You can refer to this when discussing with us and it makes it easier to find the appropriate issue, but you can't track them yourself. 
 However, the development team have decided to include these numbers in future sets of release notes so you will find it easier in the future to identify whether your specific issues have been addressed or not.

Trados Studio > 1. Trados Studio

Handling IDML files after migration to Studio 2017 - formatting tags