Re: Bug of the ComponentContent UTF-8
Re: Bug of the ComponentContent UTF-8
- Subject: Re: Bug of the ComponentContent UTF-8
- From: Mike Schrag <email@hidden>
- Date: Tue, 11 Mar 2008 13:08:01 -0400
If you're using Project Wonder, you should be setting it with the
system property ... Not sure if you are or not, though.
ms
On Mar 11, 2008, at 11:59 AM, Yoshihiko Mori wrote:
Hi Chuck,
Thank you for your advice.
This was not a bug.
I changed the character set name from "UTF-8" to "UTF8" in the
parent Component code as follows and it seems that it went well.
In the past the "UTF-8" was not a problem but it does not go well now.
/** for UTF-8 **/
public void takeValuesFromRequest(WORequest aRequest,WOContext
aContext)
{
aRequest.setFormValueEncodingDetectionEnabled(true);
aRequest.setDefaultFormValueEncoding("UTF8");
super.takeValuesFromRequest(aRequest,aContext);
}
public void appendToResponse(WOResponse aResponse,WOContext
aContext)
{
aResponse.setContentEncoding("UTF8");
super.appendToResponse(aResponse,aContext);
}
/** **/
Thanks.
Mori
On 2008/03/12, at 0:05, Chuck Hill wrote:
Hello Mori,
On Mar 11, 2008, at 12:31 AM, Yoshihiko Mori wrote:
Dear all,
Dear developers.
I found a bug in the WOComponentContent.
It is as follows:
1. I set the Meta header in the Component as follows:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
2. I sent a String of UTF-8 in the WOTextField in the WOForm in
the WOComponentContent in the Component.
3. I got unexpected code and I found the following log include the
context().request() log:
content-type=[application/x-www-form-urlencoded]
4. If the WOForm is not included in the WOComponentContent, I got
expected code and the log of context().request() is as follows:
content-type=[application/x-www-form-urlencoded; charset:UTF-8]
I think this behavior that the Component in the WOComponentContent
does not get the charset of the Meta header is a bug.
I am developing with the MacOS X 10.5 + WebObjects 5.4.1 + WOLips
3.3.4984.
Could you fix it and give me any workaround?
Thanks.
Mori.
You can't just set the meta header, you need to tell WebObjects to
use the UTF-8 encoding everywhere. This should help:
http://wiki.objectstyle.org/confluence/display/WO/Web+Applications-Development-Localization+and+Internationalization
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden