XInclude warnings in version 9.2
I just updated to version 9.2 build 2008050821. I have many XInclude tags in by Docbook document that include plain text code samples like the following: <programlisting><xi:include href='../code/output/actionmailer/generator_example.txt' parse='text' xmlns:xi='http://www.w3.org/2001/XInclude'/></programlisting> With the new version I'm receiving a large red warning in the author view like: Error parsing external reference: file:/Users/cody/writing/oreilly/book/code/output/actionmailer/generator_example.txt. Cause: The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain characters. Is there any way to prevent this behavior? It is very visually distracting and fills some pages of my document almost entirely with the red warnings. -- Cody Fauser http://shopify.com - e-commerce done right http://www.codyfauser.com - blog http://peepcode.com/products/activemerchant-pdf - ActiveMerchant PeepCode http://www.oreilly.com/catalog/rjsrails - RJS Templates for Rails
On 10 mai 08, at 16:00, Cody Fauser wrote:
Error parsing external reference: file:/Users/cody/writing/oreilly/book/code/output/actionmailer/ generator_example.txt. Cause: The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain characters.
I have the same behaviors in author mode put when generating the PDF (using XEP) it works perfectly. Jacques
Hello, The text fragments (parse='text') included in the current document are not handled correctly in the Author mode. Thank you for reporting this problem. You can avoid the red error messages by disabling the included content with the option "Display referred content" available from Options -> Preferences -> Editor -> Author. After disabling the included content only the xi:include tags will be displayed. If you want to hide these tags too in the Author mode you should set the following CSS stylesheet in the DocBook document type from Options -> Preferences -> Document Type Association -- DocBook 4 (or DocBook 5) -- Edit -- The Author tab -- CSS: @import "docbook.css"; @namespace xi "http://www.w3.org/2001/XInclude"; xi|include { display:none !important; } where "docbook.css" is the location of the default DocBook CSS. I assumed in the above CSS stylehseet that the custom CSS stylesheet is saved in the same folder with the default DocBook one. The included content is handled correctly in XSLT transformations and this is why Jacques did not have this problem in the PDF output. Regards, Sorin Jacques Foucry wrote:
On 10 mai 08, at 16:00, Cody Fauser wrote:
Error parsing external reference: file:/Users/cody/writing/oreilly/book/code/output/actionmailer/generator_example.txt.
Cause: The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain characters.
I have the same behaviors in author mode put when generating the PDF (using XEP) it works perfectly.
Jacques
Thanks for the information. Do you plan to correctly handle the parse="text" case with XInclude in a future release? On Mon, May 12, 2008 at 5:53 AM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
The text fragments (parse='text') included in the current document are not handled correctly in the Author mode. Thank you for reporting this problem.
You can avoid the red error messages by disabling the included content with the option "Display referred content" available from Options -> Preferences -> Editor -> Author. After disabling the included content only the xi:include tags will be displayed. If you want to hide these tags too in the Author mode you should set the following CSS stylesheet in the DocBook document type from Options -> Preferences -> Document Type Association -- DocBook 4 (or DocBook 5) -- Edit -- The Author tab -- CSS:
@import "docbook.css";
@namespace xi "http://www.w3.org/2001/XInclude";
xi|include { display:none !important; }
where "docbook.css" is the location of the default DocBook CSS. I assumed in the above CSS stylehseet that the custom CSS stylesheet is saved in the same folder with the default DocBook one.
The included content is handled correctly in XSLT transformations and this is why Jacques did not have this problem in the PDF output.
Regards, Sorin
Jacques Foucry wrote:
On 10 mai 08, at 16:00, Cody Fauser wrote:
Error parsing external reference:
file:/Users/cody/writing/oreilly/book/code/output/actionmailer/generator_example.txt. Cause: The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain characters.
I have the same behaviors in author mode put when generating the PDF (using XEP) it works perfectly.
Jacques
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Cody Fauser http://shopify.com - e-commerce done right http://www.codyfauser.com - blog http://peepcode.com/products/activemerchant-pdf - ActiveMerchant PeepCode http://www.oreilly.com/catalog/rjsrails - RJS Templates for Rails
participants (3)
-
Cody Fauser -
Jacques Foucry -
Sorin Ristache