What about passing all the text to Google translate in one go? You can parse through the html generated, grab the blocks and add each as an element to an array. using implode() you can create string delimited array (csv style) to then send off to Google translate, get the results back and stick them back (using sprintf() for example) into the relevant blocks.
One query and all your content has had a rough translation done bypassing Google Translates limitations. On Wed, Sep 30, 2009 at 6:04 PM, Frank He <[email protected]> wrote: > They mentioned that translation speed is depending on google, blabla, so > maybe they embeded the google service in their code. > > > On Wed, Sep 30, 2009 at 11:58 AM, Eno <[email protected]> wrote: > >> >> On Wed, 30 Sep 2009, Frank He wrote: >> >> > Just found the problem is Google is only allowing a max of 64 results, >> and >> > that is why if you try to translate a whole web page by using google >> ajax >> > translate api, it won't do that. >> > >> > any good idea to overcome this? >> >> Actually I went at looked at the .tv site you mentioned and it seems to >> reload the entire page with a different language parameter so its not AJAX >> at all. That being the case, probably the I18N features in symfony would >> suffice. The only downside is that you would have to translate your site >> features into othe languages. >> >> >> -- >> >> >> >> >> > > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
