Re: [Tacos-devel] The Ajax components have encoding problems

[Paul Cantrell]

I had the template-encoding setting already, and added the output-encoding setting to my tapestry.application -- but it didn't help. Is there somewhere these need to be set for Tacos, too...? Passing -Dorg.apache.tapestry.607-patch=true on the Tomcat command line, apparently the workaround for TAPESTRY-607, does not help either. Leonardo: You aren't encountering the bug because it does not affect many extended Latin characters (presumably because they're supported by iso-8859-1), including the ones used in Spanish (áéíóúñ). Try dropping this in your page template, and watch it break when it's passed back via Ajax: —π™…♣♬☂參 Cheers, Paul On Dec 18, 2005, at 10:33 PM, Leonardo Quijano Vincenzi wrote: How's your template / response encoding set in Tacos? Specifically:    <meta key="org.apache.tapestry.template-encoding"          value="utf-8" />    <meta key="org.apache.tapestry.output-encoding"          value="utf-8"/> And your pages stored in UTF-8 of course... I'm actually using UTF-8 a lot in my application's pages (it's in Spanish.. .so) and I'm not having these kind of problems. Now, Tapestry has a known issue with Tomcat due to a unresolved Tomcat bug. Check this: http://issues.apache.org/jira/browse/TAPESTRY-607 That might help too. If not... then we'd have to see a test page to check what's wrong. --  Ing. Leonardo Quijano Vincenzi DTQ Software Paul Cantrell wrote: It looks like the Ajax components don't support Unicode. I have an AjaxForm that's updating a div containing a non-ASCII character. (Nothing unusual -- just our friend the em dash (that's "—", which may or may not come through on the list)). My pages are encoded in UTF-8, and the em dash shows up fine when the page is loaded normally. But when updated by the AjaxForm, the dash becomes a question mark. I saw some inconclusive discussions about this on the list archives, but no definitive answers. Apparently it's been a problem for a while. My guess is that Tacos is writing its response XML to a stream whose encoding has not been set properly...? Any suggestions? I'm on Tapestry 4.0rc2, Tomcat 5.5.12, and a Tacos CVS snapshot from just a couple of days ago. Cheers, Paul _________________________________________________________________ Piano music podcast: http://inthehands.com Other interesting stuff: http://innig.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems?  Stop!  Download the new AJAX search engine that makes searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems?  Stop!  Download the new AJAX search engine that makes searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel _________________________________________________________________ Piano music podcast: http://inthehands.com Other interesting stuff: http://innig.net