This is an interesting issue. The <col> element is being produced
by an extension function. So the output method of the extension
function is "xml" but the output of the transformation is "html".
To correct this problem, I would have to changed the output for
the whole transformation, which may produce invalid html.
Is this a bug or feature ??
JohnG
Erwin Bolwidt wrote:
> On Thu, 19 Jul 2001, John Gentilin wrote:
>
> I think he means that this applies only if you specified HTML output with:
> <xsl:output method="html"/>
>
> (section 16.2 applies to HTML output) <col> is special in HTML4 because it
> must not have a close tag.
>
> But if you use XML output, <col> should work like any other element.
> So try changing your output method to XML or file a bug report if it
> already is..
>
> Erwin Bolwidt
>
> > So are you saying that <col> is a reserved element name and can not
> > be used in the document ?? Is this behavior across namespaces or
> > contained within the default namespace.
> >
> > [EMAIL PROTECTED] wrote:
> >
> > > >I would get the correct tree except that the <col> node was only an
> > > >open tag, there was no corresponding close tag. While trying to debug
> > > >the problem, I changed the depth to make col at the same level as
> > > >column-header and it was still broken, then I changed the name and it
> > > >worked just fine.
> > > >A grep through the source shows that the xsltc code defines "col" along
> > > >with a few other strings. Is it true ??
> > >
> > > That's probably the list of elements specified in section 16.2 of the
> > > XSLT spec.
> > > .................David Marston
> >
> >
> >
