Does anybody know if this search issue at all related with the one below
reported (to the email list) by Martin Kofoed?
On January 31, 2006 Martin Kofoed said:
"Hi,
I've experienced a possible bug/issue with the handling of international
characters in the sample form template.
Description: when entering national characters and submitting, the result looks
wrong (character conversion error) when ending up in the recipients in-box.
Tested characters are ÆØÅæøå.
I've downloaded the 2.1.3 code in order to do some experiments, but could
anyone please point me in the direction of the right servlet?
Which servlet handles POST requests from the sample form template?
I also built a test servlet in order to reproduce the issue, and indeed,
anytime I hit doPost() and extraxt parameters from a UTF8-encoded page, I get
garbage in when doing a normal getParameter("propertyName") and the parameter
contains national characters. I think this is because the servlet container
always treats incoming strings as ISO8859-1 (can anyone clarify?). This means
that you have to manually do charset conversion every time a parameter is read:
String result = new
String(req.getParameter(propName).getBytes("8859_1"),"utf-8"));
After doing this, input from my test-servlet looks fine again.
Not sure if this is necessary somewhere in the Magnolia code, though?
Kind Regards,
Martin Kofoed"
Cheers,
Jay Moskos
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 08, 2006 6:12 PM
To: [email protected]
Subject: Re: [magnolia-user] Searching and character encoding [Anothertry]
Thomas Ferris Nicolaisen wrote:
> Experiencing the same problem with Norwegian special characters (æ ø å).
> It appears that the request converts the search string to an ASCII
> string, thereby replacing special characters with their ASCII
> representation. Upon being used for searching, thereafter being
> displayed in the search form again, the ASCII representation is used.
>
> I'm not able to try it out on the latest source (some problems with
> bootstrapping those versionable nodes). If it isn't fixed (which I don't
> think it is), this should reported as a bug in the issue tracker. Give
> it a try:
>
> http://jira.magnolia.info
>
Added the issue plus possible fix to JIRA:
<http://jira.magnolia.info/browse/MAGNOLIA-630>
-markus
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
