Erica Schidt 

Erica Schidt said:

There is no Column 4679 in the document, so I don't know what I would do correct this. 

That 4679 column is in the document.xml file under the word folder, as reported by Word:

You can see what’s there if you change the extension from DOCX file to ZIP. Then go to the word folder in Windows Explorer and open the document.xml file with a decent text editor, such as Notepadd++. Now go to that 4679 column number (you’ll see the column number in the status bar):

My bet is that there is a wrong character there (it can be a blank square character □) that you may delete it (at least to test if it works). Now save the document.xml file and close it in Notepad++ and recreate the docx file. Can you open it now in Word? If so, you may consider delete that offending character from the original XLF file. Your IT team should be able to help you here, but if you are stuck, please come back.

Erica Schidt 

Converting any xml based format to Word is the worst idea you could have. Word will destroy the source file structure and what you get in the end will never comply to the standard your source file was created with.

So solving the problem with saving Word as target is not really what you need. We should try to figure out why the xlf files cause problems.

To do that, I need a little bit more information. Which software has created the xlf files? Have you used a dedicated xlf file type or just tried to add the files to your project as is? If so, which project template did you use? Have you possibly imported any project templates from previous Studio versions to your current one? Can you possibly share such xlf file with me in private? If so, please post to info at tts-td dot com.

Hello there,

Thank you both for your input. After downloading Notepad++, I am unable to open the document.xml file using the application. When I right-click the file, I am not given the option to open with Notepad++. It automatically opens with the regular notepad which does not yield answers. In any case, according to Jerzy, it seems like converting to XLF to Word is not a long-term solution, as it seems I am discovering.  

I worked extensively with IT support and TRADOS community for three weeks trying to resolve the XLF crashing issues before resorting to Word files. The XLF files were created by integrators who converted Storyline Articulate templates in November 2025.

The files are set up using SDL XLIFF file type in TRADOS project settings. This is the same configuration I've used successfully for 1.5 years on previous projects without issues. But I am happy to try something different. I'm also happy to send sample files to info@tts-td.com. The files crash after 30 seconds to 45 minutes with stack overflow errors.

Let me know what you recommend.

Once again, thank you so much, Erica

Erica Schidt 

Anna-Maria has already offered you a direct support. Nonetheless you can send me a sample file and I will look into it. If the xlf is not standard, a dedicated file type might be necessary.

Erica Schidt 

Anna-Maria has already offered you a direct support. Nonetheless you can send me a sample file and I will look into it. If the xlf is not standard, a dedicated file type might be necessary.