Re: Bug of the ComponentContent UTF-8

2008-03-13 Thread Yoshihiko Mori
Thank you for your helpful information. I will try removing the encoding detection. Thanks, Mori On 2008/03/13, at 3:12, Mr. Pierre Frisch wrote: Ok I have had a look at it and what is broken is not the encoding but the encoding detection. Remove the encoding detection and all works correc

Re: Bug of the ComponentContent UTF-8

2008-03-12 Thread Mr. Pierre Frisch
Ok I have had a look at it and what is broken is not the encoding but the encoding detection. Remove the encoding detection and all works correctly. The default encoding for Wo 5.4.x is UTF-8 anyway. Pierre -- Pierre Frisch [EMAIL PROTECTED] On Mar 12, 2008, at 8:40, Yoshihiko Mori wrote:

Re: Bug of the ComponentContent UTF-8

2008-03-12 Thread Yoshihiko Mori
Hi Pierre, 1. version of Java: $java -version java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13- b05-237) Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing) 2. version of WebObjects: 5.4.1 3. version of MacOS X: 10.5.2 4. problems: I

Re: Bug of the ComponentContent UTF-8

2008-03-11 Thread Mike Schrag
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" i

Re: Bug of the ComponentContent UTF-8

2008-03-11 Thread Mr. Pierre Frisch
What is the problem exactly? The name should be "UTF-8" with a dash. In Java 1.4 the API changed from encoding names to charset names. The charset name use the same convention as the Web. The encoding names are considered legacy by Sun but should still work for String conversion. Could give

Re: Bug of the ComponentContent UTF-8

2008-03-11 Thread Yoshihiko Mori
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 tak

Re: Bug of the ComponentContent UTF-8

2008-03-11 Thread Chuck Hill
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: 2. I sent a String of UTF-8 in the WOTextField in the WOForm in the WOComponentCont

Bug of the ComponentContent UTF-8

2008-03-11 Thread Yoshihiko Mori
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: 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 fol