|
| | | Altova Mailing List Archives>Archive Index >comp.text.xml Archive Home >Recent entries >Thread Prev - Re: Allowing mis-matched tags (non-well-formed XML) >Thread Next - Re: Allowing mis-matched tags (non-well-formed XML) Re: Allowing mis-matched tags (non-well-formed XML)To: NULL Date: 4/17/2007 5:43:00 AM
Yes, my attributes are class, title, and such like.
I had given an instance of a bigger problem I face. My overall problem
is that I want malformed HTML to be output as a result of my XSL
transformation. But the XSL style-sheet doesn't allow it. I tried
stuffing all my malformed HTML into CDATA so that XSL treats it like
data and not XML/HTML. That doesn't work because XALAN later escapes
CDATA and browsers don't render the escaped HTML.
Any help? If I am being too vague, I can mail some XSL snippets.
-woolee_master.
On Apr 3, 7:18 pm, "Andy Dingley" <ding...@codesmiths.com> wrote:
> On 3 Apr, 14:03, nadaha...@gmail.com wrote:
>
> > Is there a simple workaround without
> > duplicating the entire body contents across both condition bodies.
>
> You need to keep your XSL source well-formed and valid.
>
> Duplicate the <body> start tag
>
> Use <xsl:attribute name="..." value="..." /> within your tests.
>
> You might even use <xsl:attribute name="..." > before your tests and
> then just return the values for these attributes from within the tests
> (check the whitespace though). I assume that you#re generating HTML
> here and your "attributes" are something like "class" or "title" where
> you're using the same attribute each time, but with diffferent values.
>
> Perhaps best of all though is to set up a variable simply and cleanly
> beforehand, then use it in the start tag:
>
> <body class="{$classNames}" >
| |
| | ||||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
