Show xi:include content in WYSIWYG view mode

Post by **SSC** » Tue Jan 13, 2015 3:52 pm

Hello,

I am currently using the lastest 16.1 Eclipse verison of the oXygen XML editor.

And I want to include a file by using xi:include like this:

Code: Select all

		

<para>This may look like that:</para>

   <para>

	<programlisting language="java">

	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text" href="./examples/LabeledTextWidget.java"/>

	</programlisting>

   </para>

Unfortunately instead of seeing the Java code I get this in WYSIWYG view mode of the editor.

Am I doing something wrong. Does the xi:include have to look different or do I have to change the settings or is this feature simply not implemented?

Best regards,

Simon

Post by **SSC** » Tue Jan 13, 2015 4:09 pm

Hello,

I just figured out that it works in case I add the Doctype declaration:

Code: Select all


<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"

                         "http://docbook.org/xml/4.5/docbookx.dtd">

It seems that the document type association already recognizes that it is DocBook, even without the Doctype declaration, but the xi:includes do not work.

Could you deliver a patch for this, because sadly I cannot guarantee that the Doctype is set properly in those XML documents, which are opened.
But when the document type association is able to find out that this is DocBook it should be easy to implement the default xi:include functionality for those documents too, isn't it?

Best regards,

Simon

Post by **Radu** » Tue Jan 13, 2015 4:57 pm

Hi Simon,

I managed to reproduce this on my side with a simple document like:

Code: Select all

<chapter>

    <title>Chapter Template Title</title>

    <para>Text</para>

    <para>

        <programlisting language="java">

   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text" href="./examples/LabeledTextWidget.java"/>

   </programlisting>

    </para>

</chapter>

I'm not yet sure why this happens but I will look into this. Ideally you would specify the Docbook 4 document type on all Docbook 4 XML documents.
I will update this forum post when I have a fix for this.
Oxygen 17 is scheduled in April-May this year, do you need this fixed sooner?

Regards,
Radu

Post by **SSC** » Tue Jan 13, 2015 5:34 pm

Hi Radu,

Thank you for your fast reply.
We do not need this earlier and look forward to the next oXygen release.

Best regards,

Simon

Post by **Radu** » Wed Jan 14, 2015 9:14 am

Hi Simon,

I took a look at the problem, it's a bug on our side and it will be fixed in Oxygen 17.0.

Regards,
Radu

Post by **Radu** » Tue May 19, 2015 10:52 am

Hi,

Just to update this thread, the issue is fixed in Oxygen 17.0.

Regards,
Radu