> Do you think it's worth bothering about the user browser capability? > UTF8 is supported by most browsers. > I think it's definitely worth bothering for user input, if the user has set their browser encoding to Big5 and the app is trying to decode using UTF-8 then the input probably won't make much sense. > I specify (force) my pages encoding and hope that it will be accepted > (and I think it is...) > I'd rather not gamble with that, and it's easy enough to implement so that it is likely to work (see my previous message). My view is that if for some reason the browser doesn't accept UTF-8 (not likely, but given the number of buggy browsers out there still possible) then the user is not likely to complain, they will just go to another site. > The setdefaultencoding method is the simplest. I don't need portability > (it is enough portable for me...) > I think you will regret that decision one day, but it's up to you!
Cheers Peter ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
