Link one ditamap to another?
I'm currently working on two products. Product A will become a component in Product B. I created a project for Product A with its own ditamap and so on. For Product B, I created a reference to the project for Product A (I'm using the Eclipse plugin version of oxygen) and linked from Product B's ditamap to Product A's ditamap. While oxygen appears to let me do this, it's not generating the topics for Product A's project. Wendy Loreti Senior Technical Writer Vocollect, Inc. 703 Rodi Rd. Pittsburgh, PA 15235 www.vocollect.com <http://www.vocollect.com/> CONFIDENTIALITY NOTICE This message, together with any attachments, may be legally privileged and is confidential information intended only for the use of the individual or entity to which it is addressed. It is exempt from disclosure under applicable law including court orders. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender and delete this message, along with any attachments, from your computer.
Hello Wendy, There are some limitations in the DITA Open Toolkit used to publish DITA Maps in Oxygen regarding the references between different topics or maps. Basically if the two DITA Maps are in the same folder and one links to another using something like: <topicref href="hierarchy.ditamap" format="ditamap"/> the output should work but if the maps are in different folder hierarchies the DITA Open Toolkit transformation will complain with warnings like: [pipeline] [DOTJ036W][WARN] The file "D:\oxygen\samples\dita\flowers\topics\introduction.xml" referenced by "D:\oxygen\samples\dita\flowers\flowers.ditamap" is outside the scope of the input dita/map directory. If you do not want to see the warning message,please use the Ant parameter 'outer.control', and set the value as "quiet".Or,you can move the referenced file "D:\oxygen\samples\dita\flowers\topics\introduction.xml" into the the input dita/map directory. I think the DITA Map which refers must be either in the same directory as the referenced map or the referenced map must be in a folder structure below the master DITA Map. You can try to register on the DITA Users List and maybe they will give you more details about this limitation. See this link for more DITA resources: http://www.oxygenxml.com/forum/post11407.html Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Loreti, Wendy wrote:
I'm currently working on two products. Product A will become a component in Product B. I created a project for Product A with its own ditamap and so on. For Product B, I created a reference to the project for Product A (I'm using the Eclipse plugin version of oxygen) and linked from Product B's ditamap to Product A's ditamap. While oxygen appears to let me do this, it's not generating the topics for Product A's project.
*Wendy Loreti* Senior Technical Writer Vocollect, Inc. 703 Rodi Rd. Pittsburgh, PA 15235
www.vocollect.com <http://www.vocollect.com/>
_CONFIDENTIALITY NOTICE _
This message, together with any attachments, may be legally privileged and is confidential information intended only for the use of the individual or entity to which it is addressed. It is exempt from disclosure under applicable law including court orders. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender and delete this message, along with any attachments, from your computer.
------------------------------------------------------------------------
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
There are several options that control what happens when a map includes resources that are not below the map's directory. In particular, you need to set generate.copy.outer to "2" and outer.control "quiet". The generate.copy.outer value of "2" means "copy all resources to the output. This will generate any result directories in their relative locations as in the source. This means that you need to set as your initial output directory a directory that has enough ancestory directories to accommodate any sideways relative references. For example, if you have a map with a reference like href="../../../somedir/anotherdir/sometopic.dita", the output will include a directory "somedir" three levels above the initial output directory. Cheers, Eliot On 7/14/09 2:04 AM, "Radu Coravu" <radu_coravu@sync.ro> wrote:
Hello Wendy,
There are some limitations in the DITA Open Toolkit used to publish DITA Maps in Oxygen regarding the references between different topics or maps. Basically if the two DITA Maps are in the same folder and one links to another using something like:
<topicref href="hierarchy.ditamap" format="ditamap"/>
the output should work but if the maps are in different folder hierarchies the DITA Open Toolkit transformation will complain with warnings like: [pipeline] [DOTJ036W][WARN] The file "D:\oxygen\samples\dita\flowers\topics\introduction.xml" referenced by "D:\oxygen\samples\dita\flowers\flowers.ditamap" is outside the scope of the input dita/map directory. If you do not want to see the warning message,please use the Ant parameter 'outer.control', and set the value as "quiet".Or,you can move the referenced file "D:\oxygen\samples\dita\flowers\topics\introduction.xml" into the the input dita/map directory.
I think the DITA Map which refers must be either in the same directory as the referenced map or the referenced map must be in a folder structure below the master DITA Map. You can try to register on the DITA Users List and maybe they will give you more details about this limitation. See this link for more DITA resources: http://www.oxygenxml.com/forum/post11407.html
Regards, Radu
---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
participants (3)
-
Eliot Kimber -
Loreti, Wendy -
Radu Coravu