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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
