Copy link to clipboard
Copied
Problem Description: Hi all, One of my clients has a problem with FM 2019. They recently upgraded from FM12 to FM2019. They are using a custom application, based on DITA 1.1. The application itself works fine in FM2019, except for one thing.
Their workflow is to generate a FM book from a XML file. The book has generated chapters from the XML as fm files. The chapters contain text insets, that point to XML files (not FM files). When generating the chapters, the XML-insets are included in the FM file. In FM12, the insets are formatted ok. In FM2019 however, there is an issue with 'white space' that is added between XML elements.
Attached two examples (png files) to illustrate this: screenshot of the structure in FM12 and in FM2019.
Do you have any idea what can be the reason? Updating the text inset doesn’t help. It looks like FM 2019 can not properly update and format the nested (linked) XML. When opening the XML directly in FM, formatting is ok and no white spaces are added.
This error is with any FM version after FM12, starting with FM 2015.
Thanks,
Wim.
Copy link to clipboard
Copied
To add: same error is with FM2020.
Copy link to clipboard
Copied
Not sure if I completely understand the architecture and process.
Are the <p> elements individual insets? Does the additional whitespace only come at inset boundaries? Or between all <p> elements in general? (In your FM2019 screenshot, the whitespace seems to be only there between p elements, but not between other elements.
Can you post the XML code of the specific section?
Copy link to clipboard
Copied
Hi Stefan,
the inset is a complete topic. I can send the XML code, but if you open that in FM there's no problem. The problem is only when the FM file is generated and the linked XML is added as textinset.
It's a bit complex to share everything, because you'll need to install the custom applcation as well. We could do a remote session to show you what happens.
Main question is: why is there a difference between FM12 and newer versions.
Thanks,
Wim
Copy link to clipboard
Copied
Sure, we can jump on a screen-sharing session with the support team. Can you send a mail to tcssup@adobe.com and put me on CC?
Meanwhile, can you check the maker.ini for this setting:
RemoveExtraWhiteSpacesOnXMLImport
Is it set to TRUE or FALSE?
Copy link to clipboard
Copied
Hi Stefaan,
RemoveExtraWhiteSpacesOnXMLImport=On
Copy link to clipboard
Copied
And regarding the question of why there is a difference between FM 12 and newer versions: If I remember right, standard-compliant whitespace handling was introduced in FM 2015. Before that Fm had some proprietary white space handling.
Copy link to clipboard
Copied