Loading ...
Sorry, an error occurred while loading the content.

Re: Are you using chapter or topic files with the DITA EDD?

Expand Messages
  • wrabkin
    Hi, Hedley -- Our Idiom WorldServer OpenTopic users are employing your approach #1. That is, they use FrameMaker to write individual topics (topic, concept,
    Message 1 of 2 , Jul 1, 2005
    • 0 Attachment
      Hi, Hedley --

      Our Idiom WorldServer OpenTopic users are employing your approach #1.
      That is, they use FrameMaker to write individual topics (topic,
      concept, task, etc.). They then construct ditamaps or bookmaps to
      assemble these topics into a final deliverable. Our XSL transforms
      start each chapter on a new, right-hand page, but within a chapter
      text flows continuously.

      Regards,
      Bill Rabkin
      WorldServer Evangelist
      Idiom Technologies, Inc.

      --- In dita-users@yahoogroups.com, hedley.finger@m... wrote:
      > All:
      >
      > A problem with FrameMaker is that book components always start on a new
      > page when you print a book (or generate a PDF). If a publication
      consists
      > of topic files, how are you getting a new "section" to run into the last
      > page of the previous "section" that only occupies a few lines on the
      page.
      > That is, if the new section does not run on but starts a new page, then
      > almost an entire page is wasted at the end of the previous section.
      >
      > So how are readers of this list solving the problem:
      >
      > 1 Use FrameMaker as an editor only of single topics, i.e. not using
      > book files to assemble topics and generate PDFs. Instead, in this
      > approach, you would use the DITA toolchain with map files (as
      > equivalents of FM *.book files) to generate PDFs and HTML Help.
      >
      > 2 Hack the ditabase DTD to create an Uber container, i.e. a
      > higher-level <chapter> or <appendix> element which contains
      > <topic>, <task>, <concept> or <reference> elements as children.
      > That is, all <topic>, etc. sections are contained within a single
      > chapter
      > or appendix file, itself a component of a book file, so you
      can then
      > use FrameMaker in the normal way to generate PDFs, but the DITA
      > toolchain to generate HTML Help.
      >
      > 3 Same as (2), but using text insets to insert the <topic>, <task>,
      > <concept> or <reference> elements within a <chapter> or
      > <appendix> element which is itself a book component.
      >
      > There are problems with all of these approaches but (2) and (3) would
      > appear to create problems with cross-references. Any comments? Is
      anyone
      > using a content management system for managing versions and topics? Do
      > files stored in the CMS = chapters, etc. or topics?
      >
      > Regards,
      > Hedley
      >
      > --
      > Hedley Finger
      > Technical Communications Support Specialist
      > MYOB Australia <http://www.myob.com/>
      > P.O. box 371 Blackburn VIC 3130 Australia
      > 12 Wesley Court Tally Ho Business Park East Burwood VIC 3151
      > Australia
      > <mailto:hedleyDOTfingerATmyobDOTcom>
      > Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558
      >
      > (c) MYOB Technology Pty Ltd 2005
    Your message has been successfully submitted and would be delivered to recipients shortly.