You are misapplying @conref on topicref. The @conref attribute is only supposed to be used to include elements of the same type or more specialized types. Thus, you can conref from one topicref to another topicref, but conrefing from a topicref to a topic is both invalid (pre the DITA spec) and meaningless (a topic may not occur literally in a DITA map). In advance of a built-in way to preview maps as resolved docs, you can use the preview XSLT I've added to the DITA4Publishers project (available from the source tree here: http://dita4publishers.svn.sourceforge.net/viewvc/dita4publishers/trunk/xslt /) This preview style sheet is designed to provide a single-file rendering of a map and its topics. It's not 100% complete with respect to DITA features but it's good enough and it's easy to use from Oxygen--just set up an XSLT scenario that applies the transform to your map and there you go. This code is still under active development, so I'm not ready to fully support it (which is why there's no download package or documentation for it) but we're definitely using it and testing it so I can certify that it works reasonably well. Once I've gotten it to the point where I can package and document it, I will. Cheers, Eliot On 10/15/09 8:28 AM, "Mario Madunic" <Mario_Madunic@newflyer.com> wrote:
All the examples of topicrefs I¹ve seen use @href when referencing topics. When viewed in author mode all I see is ³topicref² with a grey background. But when I change the @href to @conref in 10.2 and 10.3 the topicrefs are resolved and I can see basically what the output will look like. In 11 the following error appears:
Error - recursion detected when expanding reference: topics/task_task123.dita#topic123!
Should the topicrefs only contain @href?
The above behaviour is a really nice to have. Also tried having both @href and @conref and found that the PDF plug-in in the OT does not output the content that is referenced. Only when @href exists (no @conref) does the PDF plug-in resolve all the references.
We like the behaviour of seeing the map resolved in author mode, as it will show what the output will basically look like and very quickly. We prefer this over continually parsing the map into PDF as our manuals are 1000+ pages and image intensive and does take quite a bit of time.
Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries
(204) 934 8815
mario_madunic@newflyer.com
-------------------------------------------------------------------- Please consider the environment before printing this e-mail.
CONFIDENTIALITY STATEMENT: This communication (and any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
---- 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>