I have done some work to ensure that accented characters are passed
back to my application by adding that ENCTYPE to forms. Adding that
attribute will allow it to pass through to the generated <form> element
just fine. I'm not sure if this should be the default though. What
are the cons to doing so?
Erik
On Apr 5, 2005, at 11:19 PM, 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]
