paths.xml 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. This file is part of the DITA Open Toolkit project hosted on
  4. Sourceforge.net. See the accompanying license.txt file for
  5. applicable licenses.
  6. (C) Copyright Shawn McKenzie, 2007. All Rights Reserved.
  7. *-->
  8. <?xml-stylesheet href="../../../../xsl/ditaview_shell.xsl" type="text/xsl"?>
  9. <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
  10. "../../../../dtd/concept.dtd">
  11. <concept id="tocjs_paths" xml:lang="en-us">
  12. <title>Resolving path issues</title>
  13. <conbody>
  14. <p>The sample documents and related ant tasks work for a relatively simple directory structure.
  15. They
  16. assume that your content and output directory structure will be something like:
  17. <screen>
  18. sample/
  19. |-- basefiles
  20. |-- concepts
  21. `-- tasks
  22. </screen>However, if your ditamap refers to content in other parallel project directories, your output
  23. will have a deeper path to the same files. For instance, imagine your ditamap file is in the root of
  24. the <filepath>sample</filepath> directory, but it includes a reference to a topic in
  25. <filepath>other</filepath> such as:
  26. <codeblock>
  27. &lt;topicref href=&quot;concepts/foo.xml&quot;&gt;
  28. &lt;topicref href=&quot;concepts/bar.xml&quot;/&gt;
  29. &lt;topicref href=&quot;../other/concepts/baz.xml&quot;/&gt;
  30. &lt;/topicref&gt;
  31. </codeblock>
  32. Referencing content in this way will force a deeper nesting to the output directory. The
  33. directory structure of your content in the output directory would now be:
  34. <screen>
  35. sample/
  36. |-- other
  37. | `-- concepts
  38. `-- sample
  39. |-- concepts
  40. `-- tasks
  41. </screen>
  42. Note that there are now two <filepath>sample</filepath> directories in the output, the main one and one that is a
  43. sibling to the <filepath>other</filepath> directory. The files are generated by the
  44. Open Toolkit for the sample project now wind up in the deeper nested <filepath>sample</filepath>
  45. directory.</p>
  46. </conbody>
  47. </concept>