Slight correction…
The results are the same when saving as a book with components or as a composite book. The difference is when I change my ditafm-output.ini file to a flat file. That is when I get the topics to run together properly but have all of the other issues. Sorry about the confusion.
Marsha
______________________________________
Frame 11
DITA 1.2
We are having a heck of a time getting our books to behave in DITA 1.2.
If we save our ditamap:
- As Book 11.0 with frame components, each topic is on its own page. Everything else works fine.
- As a Composite Document 11.0, the topics run together properly, but the figure captions and table captions end up using our AnchorFig and AnchorTable tags. (AnchorTable is in the EDD to force a table into its own paragraph of only 6pt type. AnchorFig is a holdover that can be deleted. It is also 6pt.)
In addition, our <stepsection> element is now the first numbered step in a task and the <context> is now formatted as bold italic the way <stepsection> should be.
Task Examples:
Correct
<context>blah blah blah</context>
<steps><stepsection>To fram the wuzzle:</stepsection> <-- Notice the bold italic here. That is as designed.
<step><cmd>1. Do something.</cmd></step>
...</steps>
What DITA 1.2 is doing:
<context>blah blah blah</context> <-- Notice the bold italic here! That is the way <stepsection> s/b formatted.
<steps><stepsection>1. To fram the wuzzle.</stepsection> <-- Notice the number here!
<step><cmd>2. Do something.</cmd></step>
...</steps>
There are other issues, such as some graphics being cut off, and some table cell <entry> elements not behaving consistently.
Like I said, is anyone else using DITA 1.2? Are you having these issues?
Marsha