On 31.10.2004 18:16, Marc Portier wrote:
So assuming all this reasoning is ok, what could never work is this:
- change your form-encoding (and matching setting of serialization)
to anything else then UTF-8, cos then request-params in forms and
pre-built ones in url's get encoded differently and
, Philip, EMP-UK
Subject: Re: Encoding problems, still!
In mozilla Firefox, when you open the right-click menu and choose View page Info
what is the value for Encoding there?
The serializer still seems to use ISO-8859 (e.g. not UTF-8)(according to the link
problem)?
The serializer add's the encoding
[EMAIL PROTECTED] wrote:
I have just recently resolved a problem with fragment identifiers in URLs for pages
that are served-up by Cocoon in UTF-8 to IE 6 on the PC.
My sitemap was set-up to deliver XHTML in UTF-8 and IE understood this. However, if I
sent a request that had a fragment
and commented out the reference to ISO-8859-1
Any ideas any one?
Regards
Phil Fennell
-Original Message-
From: Leszek Gawron [mailto:[EMAIL PROTECTED]
Sent: 01 November 2004 13:18
To: [EMAIL PROTECTED]
Subject: Re: Encoding problems, still!
[EMAIL PROTECTED] wrote:
I have just recently
taking one step at the time (what am I not seeing?):
- suppose a sax stream (producing xhtml) before serialization has a @href
holding an eurosign (\u20AC unicode char)
- I hear you guys saying that xalan will recognize the uri-type attribute and
serialize this character out as %E2%82%AC
On Fri, 29 Oct 2004, Kees van Dieren wrote:
In mozilla Firefox, when you open the right-click menu and choose View
page Info what is the value for Encoding there?
The same than used in serializer configuration. No problem here.
The serializer still seems to use ISO-8859 (e.g. not
On 30.10.2004 02:42, Marc Portier wrote:
That late? ;-)
But then in the bug report for Xalan (someone having this same
problem) it says:
According to section 16.2 of the XSLT Recommendation [1], non-ASCII
characters in URI attribute values should be escaped using the method
recommended in
Joerg Heinicke wrote:
On 30.10.2004 02:42, Marc Portier wrote:
That late? ;-)
ugh
But then in the bug report for Xalan (someone having this same
problem) it says:
According to section 16.2 of the XSLT Recommendation [1], non-ASCII
characters in URI attribute values should be escaped using the
In mozilla Firefox, when you open the right-click menu and choose View
page Info what is the value for Encoding there?
The serializer still seems to use ISO-8859 (e.g. not UTF-8)(according to
the link problem)?
The serializer add's the encoding type to the resulting html page, just
behind the
...adding to my latest post
The URL-encoding is done wrong when serializing to HTML. According to
specs äö should become %E4%F6 when encoded, not %C3%A4%C3%B6. This
seems to be the problem. So far I've noticed this problem with the
HREF-attribute only.
For a test I made a styslesheet that
just scanning through this issue fast it seems to me like more evidence
of things expressed here:
http://marc.theaimsgroup.com/?t=10923117717r=1w=2
rehashing what I read from Tuomo's setup:
- cocoon-servlet init params are set to have container-encoding
unchanged (thus iso_8859_1) like we
Ok, now I'm really confused.
In Bruno's excellent paper about Cocoon encoding, there's a section that
says:
For Java-insiders: what Cocoon actually does internally is apply the
following trick to get a parameter correctly decoded: suppose value is a
string containing a request parameter, then
Tuomo L wrote:
Ok, now I'm really confused.
In Bruno's excellent paper about Cocoon encoding, there's a section that
says:
For Java-insiders: what Cocoon actually does internally is apply the
following trick to get a parameter correctly decoded: suppose value is
a string containing a request
Hi,
We're having some serious encoding problems. This happens only with the
@href attributes in html, when using characters like å, ä and ö (in
Finnish alphabet). Form encoding works just fine. I've gone through
all the threads concerning encoding (other people having encoding problems
too).
On 28.10.2004 21:35, Tuomo L wrote:
We're having some serious encoding problems. This happens only with the
@href attributes in html, when using characters like å, ä and ö (in
Finnish alphabet). Form encoding works just fine. I've gone through all
the threads concerning encoding (other people
15 matches
Mail list logo
