[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Newline problems


Subject: RE: [xsl] Newline problems
From: "Vishwajit Pantvaidya" <pantvaidya@xxxxxxxxxxx>
Date: Fri, 02 May 2003 16:13:34 -0700

> Thanks for your reply, Lars.
>
> Actually, my entire output xml is empty, meaning most element
> tags exist
> without any values in the output xml.

Hmm, so there is output, but it consists of empty elements.
I understand better now... that fits exactly with what you thought,
that the values of the text nodes in your input document
differ from what you expected by having newlines on them.

> Here is the source xml and the xsl in more detail:
>
...(deleted for brevity)

Yes, it makes sense that this element would not have a value in the output,
because as you suspected, the contents of attr/name is not 'ponumber' but '
ponumber'. This can be cured with
<xsl:value-of select="attr/atomicValue[normalize-space(../name)='ponumber']"/>



> </xsl:element> > ... > </xsl:template> > ... > </xsl:transform> > > > About your query about xsl-output doctype-public, our source > xml has an > inline DTD. I understand that doctype-public or system are to > be used if we > have an external DTD. Is that correct?

Yes, for the *output* document.
Sounds like your output document has an inline DTD too, in which
case never mind.

Lars


Thanks for you help, Lars. Sorry for the faux paus - in my hurry I talked about the source xml. Actually, the output xml has no DTD, just a dummy DOCTYPE declaration, just because the target system needs that.


Vish.


_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail



XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list




Current Thread
Keywords