Dear Team,

Following is my XSLT converter where I use to convert short tag files to Vaild-XML

XSLT

<xsl:template match="node()|@*">
   <xsl:copy>
   <xsl:apply-templates select="@*"/>
   <xsl:apply-templates/>
   </xsl:copy>
 </xsl:template>

<xsl:template match="bk">
<book>
  <xsl:apply-template select="@*"/>
  <xsl:apply-template/>
</book>
</xsl:template>

<xsl:template match="au">
<author>
  <xsl:apply-template select="@*"/>
  <xsl:apply-template/>
</author>
</xsl:template>


Input File:
<bk>Book Name</bk>
<au>author name</au>

Output File:
<book>Book Name</book>
<author>author name</author>

Now the problem is generating element for plain text inside unknown tag sequence. And I want all this to named as <unknown> element

For example:
------------

Input File:
<book>Book Name</book>
Volume-I
<author>author name</author>
Only @ £450

Required Output File:
<book>Book Name</book>
<unknow>Volume-I</unknow>
<author>author name</author>
<unknow>Only @ £450</unknow>

Any help would be great full.

Thanks,
ROCXY

__________________
Thanks,
Rocxy.

You're problem is that the text isn't inside a tag at all, its a text node which is a sibling of the bk and au elements.

Something like this might work:

<xsl:template match="bk/text() | au/text()">
  <xsl:value-of select="."/>
</xsl:template>

<xsl:template match="text()">
  <unknown>
    <xsl:value-of select="."/>
  </unknown>
</xsl:template>


/- Sam Judson : Wrox Technical Editor -/

I haven't tested the above, but it very much depends on what other text nodes you have, and especially how your parser is handling whitespace.

/- Sam Judson : Wrox Technical Editor -/

Your input file isn't well-formed XML, so it can't be processed using XSLT. If you add a <wrapper> element around it, to make it well-formed, then you can do

<xsl:template match="wrapper/text()">
<unknown><xsl:value-of select="."/></unknown>
</xsl:template>

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

Unfortunately there's no way in standard XSLT to generate an internal DTD like the one you describe, without using the horrible disable-output-escaping mechanism (you can do it in Saxon using the saxon:doctype extension, but that doesn't help all that much - it has the same architectural problems).

There's no reason why the text that you generate has to be fixed, you can compute it using xsl:value-of in the same way as any other text.

However, there's no obvious way of reading it from the source document, unless you are prepared to use XSLT 2.0's unparsed-text() function to read the document in unparsed form and extract the DOCTYPE definition "by hand".

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference