Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8360383
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T11:27:05+00:00 2026-06-09T11:27:05+00:00

This is similar to a previous question that I asked, with one variation. I

  • 0

This is similar to a previous question that I asked, with one variation. I would like to know how to merge multiple topics into one (using @chunk) and then have other child topics that can be navigated to in the HTML output:

Real-world example: http://docs.autodesk.com/3DSMAX/15/ENU/3ds-Max-Help/files/GUID-484B095B-1229-4CB9-BC53-952AC40F67C2.htm

  • At the top of the document you will notice that multiple topics have been combined into one. These topics include concept and task types.
  • Towards the bottom of the document you will see that you can navigate to child topics.

Despite many efforts I cannot get the nested topics to remain individual. They either merge with topic1+topic2+topic3 or they disappear from TOC altogether.

Given that there are 7 individual topics of assorted types, I would like to write a map that produces the following HTML output:

  • topic1+topic2+topic3
    • topic4
    • topic5
      • topic6
  • topic 7
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T11:27:07+00:00Added an answer on June 9, 2026 at 11:27 am

    Okay, after a lot of tinkering I have found that the following generates the desired output:

    <!-- chapter.ditamap -->
    <topicref href="objects/overview.dita" type="concept" chunk="to-content">
        <!-- topics to combine with parent -->
        <topicref href="objects/visualising-objects.dita" type="concept"/>
    
        <!-- changing-the-object-size.dita = nested topic -->
        <topicref href="changing-the-object-size.dita" type="task" chunk="to-content"/>
    </topicref>
    

    or another slightly cleaner markup (imo):

    <!-- chapter.ditamap -->
    <topicref href="objects/overview.dita" type="concept" chunk="to-content">
        <!-- topics to combine with parent -->
        <topicref href="objects/visualising-objects.dita" type="concept"/>
    
        <!-- changing-the-object-size.dita = nested topic -->
        <topicgroup>
            <topicref href="changing-the-object-size.dita" type="task" chunk="to-content"/>
        </topicgroup>
    </topicref>
    

    This generates 2 HTML files, one for “Overview + Visualising Objects” and another for “Changing the Object Size” which is nested within “Overview + Visualising Objects”.

    Unfortunately I cannot place the combined topic into its own separate map:

    <!-- chapter.ditamap -->
    <!-- objects.ditamap = combined topic -->
    <topicref href="objects.ditamap" type="dita">
        <!-- changing-the-object-size.dita = nested topic -->
        <topicref href="changing-the-object-size.dita" type="task"/>
    </topicref>
    

    (any ideas guys?)

    But, at least I have found a solution!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I know this question is similar to several previous ones, but I can't find
I asked a similar question like this yesterday but after waiting for ever I
I currently had a problem similar to this previous question: Why would our Java
I realize that there was a similar question asked here , but this is
This is similar to my previous question, but that solution did not solve this
I asked a question similar to this one a couple of weeks ago, but
This is Similar to a previous question I asked about the Cubic Bezier. I've
This is similar to my previous question but it didnt work with the Kindle
This is very similar to a previous question (and may be the exact same
This post is very similar to my previous one, but the data structures are

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.