Thanks for the swift response, as always. Yes, for XHTML output, a link to the file text is fine, and what one would expect.
For PDF, yes, the 'execute target' behavior is questionable - it just happened that I picked a Ruby script, rather than a source file. I was actually thinking of targeting XML configuration files - although the real ones are probably too big to display in-line. I wouldn't expect the target content to be displayed in XXE - after all, it could be anything in any language (in contrast to conref, of course). regards /Roy MacLean Dovetail Roy MacLean| Technical Writer | T: +44 20 7562 7777 | M: +44 7956 474 911 | Dovetail | 51 Moorgate, London, EC2R 6BH, UK | The information in this email is for the sole use of the intended recipients(s). It may be confidential and/or legally privileged. Any review, disclosure, copying, distribution, retention, or any other use by others is prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. We reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. ________________________________________ From: Hussein Shafie [[email protected]] Sent: 23 February 2012 09:43 To: Roy MacLean Cc: [email protected]; [email protected] Subject: Re: [XXE] Processing of coderef element On 02/23/2012 09:52 AM, Roy MacLean wrote: > I've just been trying out the <coderef> element: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" > "topic.dtd"> > <topic id="codefreftest"> > <title>Coderef Test</title> > <body> > <p>Here's a codeblock with a coderef: > <codeblock> > <coderef href="../../../../../Ruby/script/download.rb"/> > </codeblock> > </p> > <p>How did that come out?</p> > </body> > </topic> > > So: > > * The DITA 1.2 spec says: "When evaluated, the <coderef> element > should cause the target code to be displayed inline". We simply missed this point when reading the DITA spec. > * XHTML output has a hyperlink to the file as text Seems reasonable, given the fact that ditac generates an hyperlink to the text file. > * PDF and Word outputs have a hyperlink that attempts to run the > script (which could be useful, I suppose) It's Acrobat Reader (or the clone you use) which has this --in our opinion, not reasonable-- behavior. > > Could you clarify the situation , please. > Next release of ditac (expected in about 2 weeks) should contain a fix for this bug. (But XXE will *not* display the target code inline.) -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
