Hi. I'm sorry, but don't have any solutions for you.
I also don't know if there's been an issue filed on this. What my response to that posting was about, was to check the actual HTML generated by Tapestry. Doug posted that it seemed the browsers were posting bad data; but certain things in the HTML spec allow surprising behaviors. --- And so, if you do check the HTML, and see what Tapestry is getting back, it might be that the browser is sending something legal, given the exact headers and markup it is in fact receiving. Especially since Tapestry 5's HTML generation is still in a bit of limbo. Good luck. Ciao. -Steev Coco. On Mon July 16 2007 9:31:49 am you wrote: > I'm terribly sorry this was already asked by Doug Hauge. > > Actually, I could not really get the point in the answer from Steven. > Do I need to specify some additional meta tags? Plus an informal > parameter to the form component? > > Doug, is it working for you now? > > On Mon, 2007-07-16 at 15:11 +0200, Sandor Irlanda wrote: > > Hi, > > > > We are using T5.0.5. > > According to the infos found in this list we managed to use UTF8 > > encoding in our pages. But since we added the first Upload component to > > the form the submitted values are scrambled again. > > Is it a known bug? > > > > Do you know a workaround? > > > > Thanx in advance > > > > Sandor Irlanda > > > > > > > > --------------------------------------------------------------------- > > 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]
