Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Subject: Re: CForms stylesheets - use of xsl:param and xhtml
From: Bruno Dumon <bruno@outerthought.org>
To: dev@cocoon.apache.org
In-Reply-To: <m3d63i70jk.fsf@colina.demon.co.uk>
References: <m3r7ry74rb.fsf@colina.demon.co.uk>
	 <1088525394.18849.4.camel@yum> <m3hdsu7306.fsf@colina.demon.co.uk>
	 <1088528130.18847.47.camel@yum>  <m3d63i70jk.fsf@colina.demon.co.uk>
Content-Type: text/plain
Organization: Outerthought
Message-Id: <1088531330.18847.65.camel@yum>
Mime-Version: 1.0
Date: Tue, 29 Jun 2004 19:48:50 +0200
Content-Transfer-Encoding: 7bit

On Tue, 2004-06-29 at 19:10, Colin Paul Adams wrote:
> >>>>> "Bruno" == Bruno Dumon <bruno@outerthought.org> writes:
> 
>     >>  Yes.  At least, only those whose parent is not an html/xhtml
>     >> element.
> 
>     Bruno> So the namespace of an element made using xsl:element is
>     Bruno> inherited by literally-defined elements?
> 
> Afraid not - as I realised two minutes ago :-)
> 
>     Bruno> Let's hope so :-)
> 
> Well, on what I've coded so far - definitely not (when I hit the
> reload button - I have to look twice - generation is zero time to my perceptions).

yeah, you'd have to be fast to see the difference between 50 en 75
milliseconds, but it sure would be noticeable if you have dozens of
concurrent requests to handle. But I'm still not implying there is such
degration in performance -- in fact, likely not.

> 
> However, the existing stylesheets are not valid anything, so it is
> defeating my purpose (of generating valid xhtml) from proceeding as I
> have been - at least without further changes.

BTW, what's the advantage of using XHTML? What browser does support it?

> 
> I had just got as far as changing a span into an xsl:element - and
> then looked at it's child.
> It was at that point I realised what you have just pointed out
> (above), and sighed.
> But I then positively groaned as i realised the contents of the span
> was a table - illegal - span can only contain inline elements - html
> 4.01 or any xhtml (I don't bother to check earlier DTDs).
> 
> So what do I do?

fix it ;-)

> 
> The span concerned is just apparently surrounding the table with core
> attributes - which can equally go on the table itself - so the obvious
> solution is to just transfer these attributes to the table element. No
> difference as far as (x)html is concerned.
> But maybe there is a knock-on effect somewhere? Perhaps there is java
> code somewhere that expects this structure? I don't know. Can someone
> advise me please?

It might help if you mention where this is done (stylesheet/template).

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org