Return-Path: 
 <embperl-return-4961-apmail-perl-embperl-archive=perl.apache.org@perl.apache.org>
Delivered-To: apmail-perl-embperl-archive@perl.apache.org
Received: (qmail 80873 invoked by uid 500); 19 Nov 2002 16:19:52 -0000
Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:embperl-help@perl.apache.org>
list-unsubscribe: <mailto:embperl-unsubscribe@perl.apache.org>
list-post: <mailto:embperl@perl.apache.org>
Delivered-To: mailing list embperl@perl.apache.org
Received: (qmail 80860 invoked from network); 19 Nov 2002 16:19:52 -0000
Message-ID: <20021119161955.96022.qmail@web14806.mail.yahoo.com>
Date: Tue, 19 Nov 2002 08:19:55 -0800 (PST)
From: Jarrod Stenberg <slonob@yahoo.com>
Subject: Re: HTML mangling and XML
To: Jochen Topf <jochen@remote.org>, Embperl list <embperl@perl.apache.org>
In-Reply-To: <20021119101627.A29564@eldorado.remote.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> 
> I am using Embperl-2.0b8. I am feeding
> (X)HTML/Emberl-Code through a XSLT
> stylesheet. This works well until I have some forms
> in my HTML code and
> Embperl mangels for instance <option> tags by adding
> a "selected" attribute.
> The "selected" is not valid XML so the XSLT parses
> complains. I tried
> setting the optDisable* flags, but it didn't work.
> Looking at the Changes
> file this seems to be normal behaviour for some
> reason.

This is not really an Embperl problem.  Your XML,
whether it's straight up XML, XHTML, XSL or whatever
must be compliant.  Adjusting the processor to
accomodate the operator defeats a main objective of
the XML recommendation.  

This should be changed to either:
<option selected="1"/>
Or:
<option>
<xsl:attribute name="selected">1</xsl:attribute>
</option>

> btw: A very similar problem. In some
> non-reproducable cases Embperl modified
> a URL in a link which contained something like
> "http://www.example.org/foo.html?x=y" to
> "http://www.example.org/foo.html?x=y&" at which
> point the XSLT parser
> complained because of the unescaped & in there.

Use &amp; instead of just &.  When it finds a &, it
expects it to be an entity: &somevalue;  

-Jarrod

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org