| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849 |
- <?xml version="1.0" encoding="utf-8"?>
- <!--
- This file is part of the DITA Open Toolkit project hosted on
- Sourceforge.net. See the accompanying license.txt file for
- applicable licenses.
-
- (C) Copyright Shawn McKenzie, 2007. All Rights Reserved.
- *-->
- <?xml-stylesheet href="../../../../xsl/ditaview_shell.xsl" type="text/xsl"?>
- <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "../../../../dtd/concept.dtd">
- <concept id="tocjs_paths" xml:lang="en-us">
- <title>Resolving path issues</title>
- <conbody>
- <p>The sample documents and related ant tasks work for a relatively simple directory structure.
- They
- assume that your content and output directory structure will be something like:
- <screen>
- sample/
- |-- basefiles
- |-- concepts
- `-- tasks
- </screen>However, if your ditamap refers to content in other parallel project directories, your output
- will have a deeper path to the same files. For instance, imagine your ditamap file is in the root of
- the <filepath>sample</filepath> directory, but it includes a reference to a topic in
- <filepath>other</filepath> such as:
- <codeblock>
- <topicref href="concepts/foo.xml">
- <topicref href="concepts/bar.xml"/>
- <topicref href="../other/concepts/baz.xml"/>
- </topicref>
- </codeblock>
- Referencing content in this way will force a deeper nesting to the output directory. The
- directory structure of your content in the output directory would now be:
- <screen>
- sample/
- |-- other
- | `-- concepts
- `-- sample
- |-- concepts
- `-- tasks
- </screen>
- Note that there are now two <filepath>sample</filepath> directories in the output, the main one and one that is a
- sibling to the <filepath>other</filepath> directory. The files are generated by the
- Open Toolkit for the sample project now wind up in the deeper nested <filepath>sample</filepath>
- directory.</p>
-
- </conbody>
- </concept>
|