Thanks for the heads up on this. Here is a possible workaround: If you submit a string to the translation side with no source language specified, but only a destination language, there will be a detectedSourceLanguage property in the response.
Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com http://jgeerdes.blogspot.com http://jgeerdes.wordpress.com [email protected] Unless otherwise noted, any price quotes contained within this communication are given in US dollars. If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! And check out my blog, Adventures in Web Development, at http://jgeerdes.blogspot.com ! On Mar 24, 2009, at 5:18 AM, Fitzchev wrote: > > I just issue a bug here : > http://code.google.com/p/google-ajax-apis/issues/detail?id=217 > > As mentioned by the devs, the char limit has been raised to 5000 chars > but you need to do a POST request instead of a GET (which limits is > 2000 chars). It's working fine with translate but not with detect > which is not accepting POST request. So I'm asking the devs to allow > POST on detect too because right now I'm only interested in detecting > languages. > > Please vote for that issue, thanks! :-) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX APIs" 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/Google-AJAX-Search-API?hl=en -~----------~----~----~----~------~----~------~--~---
