December 16th, 2004
It was good to discover that "preserve line breaks" now works in FrameMaker 7.1. In version 7.0, adding this to the read/write rules:
element "literallayout"
{
is fm element "LiteralLayout";
preserve line breaks;
}
didn't work.
Here's the rant I discovered in my read/write rules file from FrameMaker 7.0:
/*** Don't use "preserve line breaks;".
It doesn't work, because it inserts 'xml:space = "preserve"' in the XML, which is invalid DocBook. Also, it adds this attribute to any child elements, but, despite this, doesn't actually preserve the line breaks into the XML unless you add "preserve line breaks" to every element that might come within LiteralLayout (most elements). This would result in almost every tag in your XML having 'xml:space = "preserve"', which is nonsense!!! It also doesn't preserve FM carriage returns (which you'll have if you've copied text into an element within LiteralLayout. It only preserves forced line breaks (i.e. those you've added manually using Shift+Return). All in all, it's totally useless!!! ***/
It all now seems to work fine in 7.1. The comment about adding "preserve line breaks" to every element that might come within LiteralLayout was a red herring because LiteralLayout can only contain inline elements, and will rarely contain any of those anyway.
The only thing you need to remember is to use a line break (Shift+Return) not a new paragraph (Return) to start a new line, and if you want multiple spaces you should switch off smart spaces (Format > Document > Text Options) or use en spaces (Alt+Ctrl+space).
Potentially similar posts