[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Clarrification of @chunk="to-content" combined with topic reuse
Hi, This is my first email to the group after I joined OASIS DITA a month ago. I hope this is the right group to ask DITA spec related questions. Our writers have been using chunk=”to-content” to group topics together into one html page for the output, and it had created some questions/issues for us. My question - what is the expected behavior for @chunk=”to-content” combined with topic reuse? Scenario1 – the position of the reuse (of chunked topic) is later in the map than the chunking topic. Map - P1 (@chunk=”to-content”) o C1 o C2 - C1 (reused) In this case, OT (1.7.5) seem to generate the P1.html and C1.html nicely. Scenario2 – the position of the reused topic is before the chunking topic Map - C1 - P1 (@chunk=”to-content”) o C1 o C2 In this case, OT did not generate the C1.html, instead, it creates an anchor to P1#C1. Scenario3 – P1 is reused, and the structure of P1 is exactly the same Map - P1(@chunk=”to-content”) o C1 o C2 - P1(@chunk=”to-content”) o C1 o C2 I expect OT to generate just one P1.html. Instead, it creates a chunk########.html for the second P1 with exact same content. (###### is a large random number, which is bad for consistency, SEO, and output management.) There is no guarantee when either Scenario1 or Scenario2 will happen, as the Map is fairly large and it has sub-maps that are controlled by different groups of people. I’ve asked the question on both Yahoo user group and GitHub, and I haven’t got any reply yet. http://tech.groups.yahoo.com/group/dita-users/message/31511 https://github.com/dita-ot/dita-ot/issues/1505 Thanks,
Get the latest news and updates on BlackBerry 10 at www.BlackBerry.com/blackberry10 |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]