Hi.
I've been developing Tapestry apps involving Japanese content using default settings (UTF-8), and have experienced no problems. (Well, except OSX IE5 not displaying Japanese UTF-8 in drop downs!)
The apps so far have been for intranets - a good proving ground for me, and restricted to just a few browsers for acceptance testing. But my next app will be wide open to the net. If you run into any issues, I'd sure like to hear about them. Likewise, I'll post if I see any.
Summary: Win IE6 Firefox NN7, OSX Safari Firefox NN7 ok so far. OSX IE5 ok bar above.
Do you recall the problems you've seen in the past?
Cheers, Nick.
Random Tapestry User wrote:
I'm very new to Tapesty, but not so new to fully localized apps for display AND for posting back.
I notice the default Form component creates a form of the following syntax :
<form method="post" name="Form0" action="/some/app">
I've worked on many applications that submit form data back in a variety of encodings, but using UTF-8 across the board has proven to be the most reliable and most all browsers
seem to have no problem.
However, I always had problems with some browsers if I did not use the ENCTYPE="multipart/form-data" on every form irrespective if there's a file upload or not to get all the UTF-8 back correctly.
Anyone out there creating apps using double byte, etc, and having no problems with Tapestry's default form implementation ?
Thanks, tappapp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
