FrameMaker 2022 Translate does not produce XLIFF file
Copy link to clipboard
Copied
Since recently we have been using FrameMaker 2022 to create prepress files of the user manuals we receive from the client - the original English FrameMaker files together with the XML files. Our job is to localize them to the Serbian language, which seems quite simple if you use File > Translate > Export to XLIFF 1.2 and on the end File > Translate > Import (the whole process is described in detail on the Adobe YouTube channel). However, we have problem:
File > Translate > Export to XLIFF 1.2 produces a zip file with nothing in it, it's completely empty! XLIFF Conversion Report does not report any error. So we can't even get a XLIFF file to give to the translators. This happens with all the files we received, there are several very large books.
Can anyone share any experience with this issue?
Copy link to clipboard
Copied
That's a new one. Have you tried exporting a very simple document, like a single page with some english text? Might be useful to figure out whether the function is - completely - misbehaving or whether it is this particular job that it won't process.
Bjørn Smalbro - FrameMaker.dk
Copy link to clipboard
Copied
We tried everything - both half pages, and two pages, and the full document... several books. And we don't have any others to try with them.
Copy link to clipboard
Copied
Hm, never heard this one before. What does the console/report panel of the XLIFF export say? Also, are you talking here about trying to produces XLIFF from the FrameMaker, or from the XML files?
Your related (almost identical) discussion: https://community.adobe.com/t5/framemaker-discussions/framemaker-2022-translate-with-xml-file/m-p/14...
Copy link to clipboard
Copied
We try directly from the framemaker file (Translation...) and the report is in the screenshot as well as what we get.
Copy link to clipboard
Copied
You have probably already tried but...
- Have you tried exporting from a location closer to the drive letter? Like c:\test ? Windows can't handle really long paths but by the look of it, yours isn't too long.
- Tried stripping the + signs and and whatever out of the oardinary from the file names?
- Done the export with all files open
- Long cross reference texts can be an issue in my experience.
- Checked whether all your fonts are compatible. No type 1 fonts lurking?
Bjørn Smalbro - FrameMaker.dk
Copy link to clipboard
Copied
Thank you for advices but none of this is a problem.
![](/skins/images/EAF9F7E131C5D03B206D7C6CFC7D852B/responsive_peak/images/icon_anonymous_message.png)
![](/skins/images/EAF9F7E131C5D03B206D7C6CFC7D852B/responsive_peak/images/icon_anonymous_message.png)