FM 11 XML View corrupts DITA source files

[Guest]

This behavior is observed in DITA on FrameMaker 11.0.1.382 on Windows 7.

If I am editing a file that contains the <codeblock> element, make any change to that file in the XML View, and then save the file, FrameMaker adds 4 tab characters to the beginning of every line in the file and also deletes any leading spaces that exist inside <codeblock>. In effect, it is saving pretty printing from the XML View, corrupting my DITA source in the process. It does not matter whether I make the save in the XML View or return to WYSWIG View before doing so.

If the file does not contain a specialization of <pre>, no corruption occurs (evidenced by no proliferation of tab characters).

Please tell me I have missed a setting that would eliminate this problem.

[ScottPrentice]

Hi Larry...

Yes .. this is a known problem with FM11's XML code view. Pretty much makes it unusable for some people (anyone with code samples). Adobe is aware of this, and I hope they are working on a solution.

To make things worse, even if you don't switch to code view, your codeblock elements will still lose a leading whitespace character each time you open and save a file. Take a careful look at the file before and after, and you'll likely see missing whitespace just from doing an open and save. Of course, you'll need to have codeblocks that are indented with space to see this. There is a "fix" for this problem. Just apply the following setting in maker.ini ..

     RemoveExtraWhiteSpacesOnXMLImport=Off

Nice, eh?

...scott

[Guest]

Scott,

I was aware of the leading whitespace issue and was hoping there would be a workaround for this one as well. This is unfortunate because it renders an otherwise useful feature somewhat dangerous to use.

However, it is helpful to know that Adobe is at least aware of the problem.

Thank you,

--larry0