All the bugs you have reported are fixed in ditac v2.5.3 (to be released this month).

On 08/26/2014 06:28 PM, Francisco Soler wrote:
Hi,
Thanks for your attention.
I have seen another problem that can be related with the bug reported
previously.

When there is a task with the conref (like the task of the example) when
transforming to webhelp the toc will appear as it would has nested
topics inside. This is happening because the toc.js has this content:

    ["\n         <span class=\"webhelp-toc-section1-entry\">Parent
    Task</span>\n      ","myTopic.html#myTask",[
    ["\n            <span class=\"webhelp-toc-section2-entry\"></span>\n
             ","myTopic.html#conrefTask",null]
    ]]


As you recommended in the documentation I can put an entry in the
map.ditamap setting the toc="no":

    <topicref id="conrefTask" href="conrefTask.dita" toc="no"/>


but this is not working in this case. And the TOC will appear as follows
in the image:


​
The command line used to process the use case is:
$ ditac -f webhelp5 out/_.html map.ditamap

I attach the source code (is similar to the previous example, but with
the toc="no" change in the ditamap).

Br.
     Fran



On Fri, Aug 22, 2014 at 11:46 AM, Hussein Shafie <[email protected]
<mailto:[email protected]>> wrote:

    On 08/20/2014 01:59 PM, Francisco Soler wrote:

        Hi,
        I'm using XMLMind Dita Converter and I'm compiling a dita
        document that
        has some conref attributes pointing to other dita files and I
        realized
        that the .ditac files does not have the inclusions specified in the
        conref attribute.

        Environment:
        - ditac: INFO: ditac version is 2.5.2
        - Mac OS X 10.6.8
        - java version "1.6.0_65" (Apple VM)

        This is a reduced example of what I am doing:

        map.ditamap
        ---------------------
        <?xml version="1.0" encoding="UTF-8"?>
        <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
        <map>
             <title>DITA Topic Map</title>
             <topicref id="myTopic" href="myTopic.dita"/>
        </map>

        myTopic.dita
        ---------------------
        <?xml version="1.0" encoding="UTF-8"?>
        <!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
        <task id="myTask">
              <title>Parent Task</title>
              ...
              <task id="conrefTask" conref="conrefTask.dita">
                  <title/>
              </task>
        </task>

        conrefTask.dita
        ---------------------
        <?xml version="1.0" encoding="UTF-8"?>
        <!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
        <task id="conrefTask">
              <title>Transclusion</title>
              ...
        </task>

        myTopic.ditac (output)
        ---------------------
        <?xml version="1.0" encoding="UTF-8"?>
        <ditac:chunk
        xmlns:ditac="http://www.__xmlmind.com/ditac/schema/ditac
        <http://www.xmlmind.com/ditac/schema/ditac>__"
        xml:lang="en-gb">
        ...
        <task class="- topic/topic task/task "
        
conref="file:/Users/fsoler/__Development/testCode/__xmlMindExample/conrefTask.__dita"
        id="conrefTask">
        <title class="- topic/title "/>
        </task>
        </ditac:chunk>

        I have debugged the code and I have found that in the preprocess
        phase
        the Transclusion is being doing well. But after in the chunking
        phase
        the topics do not have the included code. This could happen
        because the
        transclusion is doing over the LoadedDocuments and the chunk do
        it over
        the LoadedTopics that are created before the first transclusion
        phase
        and refer to different memory addresses.

        The command line used to process the file is:
        $ ditac -preprocess out/_.html map.ditamap


        Thank you for your attention.


    Thanks for your detailed bug report. We'll try to reproduce it using
    the sample files you send us. If we succeed in doing so, you should
    find the bug fix in the next release of ditac which is planned for
    September. In all cases, we'll get back to you by sending you an email.

    Note that we have no doubt that we'll succeed in reproducing this
    bug because your sample contains this:

    <task>

        ...
        <task id="conrefTask" conref="conrefTask.dita">
          <title/>
        </task>
    </task>

    A nested task pulling by the means of conref the actual task. This
    is valid of course, but not that common. We didn't have this use
    case in our hundreds of test cases, hence the bug.



--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support

Reply via email to