Hi, I have the same issue. I process idml files with SDL SR2. All the conversion process is fine, but after that when I open the sdlixff file, SDL SR2 crashed and disappeared without showing any error message.

I can only use SDL 2017 to open these idml projects without crashing. idml files make SDL 2021 crash a lot. 

Before opening idml files for translation in the Editor view, check your Options settings.
In the "Formatting display style" box of the Editor section, select "Show all tags but do not show formatting." Then, you will be able to open idml files without crashing.

I had the same problem and your solution works fine! Thank you.

Thank you, I've spent half a day trying to figure out why 1 IDML-file from 7 of the same project was causing a crash without any message and your solution solved my problem.

This worked for me as well, March 2023. Can we get a fix/patch yet? This should also be the first suggestion rather than repair/reset.

 Frode Aleksandersen 

Can you confirm two things please:

1. full version number of your product:
   Trados Studio 2021 - 16.2.12.9338
   Trados Studio 2022 - 17.0.6.14902
   
   
2. Did you have some font in the IDML that you don't have installed... or maybe some non UTF-8 compliant font in the IDML?

Hi Paul 

I use Trados Studio 2021 - 16.2.12.9338. As this is a Studio Package provided by a client, I have no idea about fonts.

Please reach out to me directly on email at frode@atoo.no - maybe we can get to the bottom of this and get it fixed once and for all. This is a 100% reproducible crash on my side (no error message - Studio just closes after trying to open the file in the editor).

/frode

Frode Aleksandersen 

We'd need the source file to get to the bottom of this... not the package.  Do you know what version of Studio was used to create the package?

Paul  I don't know what version was used to generate the package, but IMO Studio should _never_ crash like this even if there's a version mismatch. I can provide the package if that's what's needed, provided it's deleted after you're done with it. I also have a set of other IDML packages from the same client, and they're fine.

 Frode Aleksandersen 

ok - send me the package - pfilkin at sdl dotcom

I'll test in 2021 and 2022 but in all honesty if it opens in 2022 you are unlikely to get any dev time to review it in 2021 because there is a simple workaround.  If there was no workaround it would get a higher priority but like this by the time it reached the top of the queue 2021 will no longer be supported at all.

So I'll happily see what can be done to address this if the problem exists in 2022.  But I think it will help to know where the package came from as this is the first question we'd be asked before we could even give this to the dev team. If it was created based on a version that had some bug in handling particular content in InDesign files that is no longer present in 2021/2022 then it will not be addressed at all.

 Frode Aleksandersen 

ok - send me the package - pfilkin at sdl dotcom

I'll test in 2021 and 2022 but in all honesty if it opens in 2022 you are unlikely to get any dev time to review it in 2021 because there is a simple workaround.  If there was no workaround it would get a higher priority but like this by the time it reached the top of the queue 2021 will no longer be supported at all.

So I'll happily see what can be done to address this if the problem exists in 2022.  But I think it will help to know where the package came from as this is the first question we'd be asked before we could even give this to the dev team. If it was created based on a version that had some bug in handling particular content in InDesign files that is no longer present in 2021/2022 then it will not be addressed at all.

Frode Aleksandersen 

Thanks for sending me the package.  I replied to your email, but the essence of the email would be to note these things:

• I don't have a problem with the package using 2022
• I can repro your problem using 2021
• the workaround is trivial -  "Show all tags but do not show formatting."

So I don't think it's realistic to expect any work to be done on this for 2021.  We are too close to the end of support for 2021 anyway and as the workaround is so simple it really will not make it anywhere close to the top of a list of priorities to focus on.