XLIFF-Export is crashing FM 17.0.5

[andreas_5547]

Dear community,

after updating FM to 17.0.5, it's not possible for me to export a book to XLIFF. I tried different approaches with large/small/real/test books. Each approach ends in the following error message:

I'm surprised that the error message shows that the exceptions are thrown in files under C:\users\ravimetha\source\adobe-framemaker-xliff-plugin\entw\plugin\clients\… (see screenshot above)

This user and/or files don't exist on my environment.

My environment:

• WIN10 Enterprise Version 22H2 (Build 19045.5011)
• FM 17.0.5

Are there any known issues in the XLIFF-Export? Or are there any known workarounds to export a book to XLIFF?

Thanks alot for your help/tips/recommendations.

Andreas

[FrameMaker-dk]

This sounds rather odd.

Can you possibly share your sts settings? I have tried exporting some of my own document and that went well but those are very simple documents.

[andreas_5547]

Hi Bjorn,

thank you for your reply. I would like to give you my settings. Do you have an idea how to share the files? From my office, there is no way for me to upload, use an open sharepoint etc.

[FrameMaker-dk]

You can just take a screendump of the dialogue box and copy paste it into the forum editor. If you need to edit out some of the stuff from the screendump, you can copy paste the screendump into MS Paint beforehand and the copy paste from MS Paint into the forum editor

[andreas_5547]

Perfect, here are my settings (sorry, only in German):

[FrameMaker-dk]

I have tried again using your settings but this time with a complex document. I did not get any errors. I have two suggestions:

I have myself formerly experienced problems when the source text in cross references became too long. You might try disabling the cross references like this and see if it makes any changes. I doubt it will, though.

2: I think something is wrong with the user login for the account you are using. It looks pretty odd that you can have a user address that is not on your system. It may be your Windows User Login or it may be the Adobe account. Are you using an Adobe account with your own name or some share company account?

[andreas_5547]

Thank you. I will try the export without XREF-formats.

For your second option: I found out that the given user login in my error message aligns with one of the FM-developers:

Maybe, the given user account is a relict, fragment, … from the development process?

[FrameMaker-dk]

Good thinking! 🙂  But still very odd!  Seems like you may have installed an update that was not quite finished.  You should probably contact Adobe regarding this issue. Here is a list of the contact options:

https://framemaker.dk/en/customer-support-for-adobe-technical-communication-suite

[andreas_5547 · Accepted solution]

Hi Bjorn,

with your recommendations I played around with different ways and I found the following successful solution:

1. Open XLIFF-Export dialog.
2. Use Adobes default.xts (in program files) as settings file.
3. Set all the needed options.
4. Save my own settings file a a new file in our file system.
5. Export Book as XLIFF.
6. WORKS! 🙂

After successful export, I compared my settings files:

• settings files created with FM 17.0.3 --> file size = 1 kB
• settings file (re-created with FM 17.0.5 from default.xts) --> file size = 74 kB

I'm not really shure but I think the issue was with my "old" settings files.

Thanks alot for your recommendations. I'm really happy now (and my translators too :-))

Andreas

[andreas_5547]

In the way described above, I found out that exporting XLIFF with XREF-formats works fine too.

[FrameMaker-dk]

Excellent!  I guess the Adobe user is probably meant for directly reporting the errors to the developer team. 

[Stefan Gentz]

Hi Andreas, could you please send the corrupt XTS file (the 1 kb one) to tcssup@adobe.com with me on CC (I'll send you a PM with my email) if you still have it? Then we can check what was wrong with it and check if we can build in a user-friendly warning message or so for corrupt XTS files 🙂

[andreas_5547]

@Stefan Gentz 

Hi Stefan, I have a new finding regarding the corrupt XTS file:

When I create a new XTS file --> it works (file size = 74 kB)

XTS file created

When I change some settings and save these settings in the same XTS file (overwrite file) --> file size = 1 kB

XTS file overwritten 

I got the same results for saving/overwriting in local folder and in company network folder.

I hope that my finding could be helpful for your research.

Best regards,
Andreas