Hi Dave,
This is definitely an interesting problem.
I'll have a look into how we might be able to improve the embedded
Element to work better out of the box for more dynamic pages like
yours, but in the mean time, here's a couple ideas:
1. Create a hidden element with the text that you change the button
text to, and pull it from there when you change it. That way, we
should translate that hidden element as well (I'm not 100% sure this
will work, but it may be worth a try).
2. Alternatively, you could use our translation API:
http://code.google.com/apis/ajaxlanguage/ to dynamically translate the
new text for your user yourself. However it may be tricky to find
what the appropriate target language is.
On my end I'll see if we can make this work better for you out of the
box, and if you find a nice workaround to fix this, please let me
know.
Cheers,
Josh
On Feb 11, 8:40 am, Dave Miller wrote:
> I have been testing the embedded Google translation function and had
> trouble with text in the update panel (I use an asp:button to change
> an asp:label text property). The text is not translated for a button
> click after the initial translation. If I click the button to display
> the new text and then change the translation, the text is translated
> properly. Is this because the asp:button produces a partial page
> postback, which does not trigger the url to indicate a translation is
> necessary? Is there anyway around this without redesigning the pages
> to cause a full postback to update the text?
