You can cache translations for up to 15 days, as long as the caching is the result of user action. I.e., the user must initiate the translation.
Honestly, I think this is actually good because google is constantly tweaking theur machune translation matrix. In other words, you may get a better translation the next time you cache it. On May 15, 2011 9:07 PM, "Shakya, Subodh" <sha...@gmail.com> wrote: > I didn't realize that we're not allowed to store the results of > translations. This would mean that the API is mostly meant for real- > time client side scripting. For example, if I write a blog post in > English and want to store the translation when say a Russian visitor > visits it would not be allowed with these terms. I do not think its a > scalable solution for a user to do the translation on the fly every > single time. Nor is it good for Google since users will just be doing > the same translations over and over again! > > Can someone really shed some light on this? > > -- > You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. > To post to this group, send email to google-ajax-search-api@googlegroups.com. > To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to google-ajax-search-api@googlegroups.com. To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
