Copy link to clipboard
Copied
I have a deadline coming up and run into a problem with FrameMaker when saving to XML. Non-breaking spaces - which are put into the XML before opening the file, using the   character code - are handled correctly when reading the XML file into Frame, but when I save the XML, all of those spaces are replaced with simple (breakable) spaces. Not what would be expected.
Looking for a global setting or an entry in the read-write rules to keep Frame from corrupting my XML. Any pointers are welcome, as long as I get them asap.
Thanks
Copy link to clipboard
Copied
Hi Jang, What version of FrameMaker are you using and how are you doing the save? Thanks. -Rick
Copy link to clipboard
Copied
Hi Rick, I am using FM 17 (i.e. 2022).
I believe it was a false alarm. I created a bunch of non-breaking spaces in an XML and saved it, then opened in oXygen. It looks like a regular space but in reality it seems to be a non-breaking one. I was expecting the &#A0; code to appear in the XML in oXygen, but apparently oXygen automatically renders it as a space. I will run some more tests to see if the hex code in the XML is correctly translated to a non-breaking space in FM and then kept when round-tripping.
Thanks.
Copy link to clipboard
Copied
Hello
Please refer to the frame manual below.
Copy link to clipboard
Copied
Thanks, but that page does not say anything about non-breaking whitespace. I did find out that FM keeps the non-breaking spaces, though.