Re: [xslt] What encoding attribute values use (1.0.15 vs. 1

[Philipp Dunkel <philipp dunkel org>]

Hi everyone,
is it an error?
According to Section B.2.1
(http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.1) of the
HTML 4 specification there are 2 correct ways to deal with this:
UTF-8 or URL encoding of characters in the Charset of the page.
UTF-8 would not work for Peter as it seems (and experiennce with
browsers tells me that it wouldn't work for a lot of cases).
The second method hoever would work, since the URL is URL-encoded
ISO-8859-2. It might make sense to think about the implementation again,
and make the recomended sollution with URL-encoding possible as well.

A quick solution for Peter could be (I don't know what you specific
needs are, but anyhow) to do the entire page in UTF-8. This might be
preferable, since as I remember we got ourselves into a lot of triouble
way back when with ISO-8859-2 when doing the Slowenian paage simobil.si.

If the discussion of whether to optionally implement the suggested
URL-encoding method, I volunteer to code it, should the decision be made
that it makes sense.

There are of courde a lot of pros and cons: How to switch for instance),
but I think since there are 2 recomended possibilities by the W3C this
might be worth another round of thinking, especially in terms of
compatibility with different browsers.

Til then everybody,
TTY Philipp

On Mon, 2002-08-12 at 15:39, Daniel Veillard wrote:
> On Mon, Aug 12, 2002 at 02:32:14PM +0200, Petr Vandrovec wrote:
> > On 12 Aug 02 at 8:10, Daniel Veillard wrote:
> > > 
> > > >   Is this change intentional, and I have to convert attribute values to
> > > > iso-8859-2 after XSLT pass (yes, I really need iso-8859-2 in attribute
> > > > values - for example default values for INPUT boxes), or is this
> > > > unintentional change?
> > > 
> > >   Well, that's an error to encode URI's content in iso-8859-2, UTF8
> > > it the right way to do this as far as I understand. This was discussed
> > > last month in the xml@gnome.org list.
> > > 
> > >   It's not a bug it's a compliance to the standards feature !
> > 
> > OK. In that case can I rely on <xsl:attribute name="HREF"> generating
> > iso-8859-2 values (i.e. not being specially handled), while 
> > <xsl:attribute name="href"> generating utf8 (when using xsl:output 
> > method="html"), or is this bug which will be fixed in the future?
> 
>   Again it's not a bug, and I think in both cases the href will be
> escaped as it's UTF8 string value, as expected.
> 
> Daniel
> 
> -- 
> Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
> veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
> http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
> _______________________________________________
> xslt mailing list, project page http://xmlsoft.org/XSLT/
> xslt@gnome.org
> http://mail.gnome.org/mailman/listinfo/xslt