> I've attached the map I was converting. The topics contain some information > that I don't want to disclose. > I hope it will be possible to identify the problem without them. If it is > not, I could try to reproduce the problem with other files. >
I cannot reproduce the problem with your map. I'll send you the results I got in a private email. I've slightly modified your map: [1] Slightly reformed <addressdetails> because this element is whitespace preserving. [2] Added chunk="to-content" to one of your topicref. However, it also worked fine, as expected, before the above modifications. --> I would say that ditac has no bug here. Please double-check your topics. My guess is that you have two topics having the same ID. <-- > Another remark on my conversion results: My topics include very complicated > tables (they have column and row headings, each table is several pages long > and needs the entire width of the page, there are cell spans and numerous > table footnotes). In sum, ditac handled these tables very well. There were > just two minor cosmetic glitches with the default configuration. > > > * If a table spans several pages, column headings are repeated on every > page which is perfectly fine. But in this case, the repeated headings do not > have a top border which looks a bit weird. There is nothing we can do to fix that. It's the XSL-FO processor (e.g. FOP, XEP or XFC) which generates the repeated headings. (On a second thought, may be the table border is not thick enough?) > * Column and row headings are rendered in bold character style which is > fine too. But if there are table footnotes in these cells, the footnote > number in the cell and the entire footnote text below the table inherit the > bold formatting which probably isn't what you usually want. We'll fix this in next release. > > I could fix this easily in a custom styleheet so I don't need any help on > this. Just thought I let you know ... Thank you very much for your feedback!
