I think it work properly with AjaxForm .
but there are encoding problem in Autocompleter because of using different js library( prototype and dojo).
I actually not sure how to solved it.
maybe you should take a look at tacos's demo page AjaxFormsExample to find out what is the problem.
-Felix
On 12/18/05,
Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote:
Ok, I guess we are going to check this one later (maybe Felix can help
over there in China ;)), but, by the way, did you file the bug report?
Just that we don't forget about it.
I have a killer headache... going to bed ;).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Paul Cantrell wrote:
> 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
>
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
encoding.png
Description: PNG image
