Hi Jeremy, Thanks for the response.
On Fri, Apr 29, 2011 at 9:45 PM, Jeremy Geerdes <[email protected]> wrote: > To my knowledge, Google does not offer permission for access to the TTS API > except for their own application purposes. At the very least, I have not > heard of anyone getting such permission. I guess I'd like someone from Google to clarify what constitutes "using Google's interface" of http://translate.google.com. It seems to me (at least arguably) that I am using their interface, just with a highly stripped-down "browser" (wget), and perhaps a touch of "deep linking". The following is what an ordinary human user does, basically: >$ firefox "http://translate.google.com/translate_tts?tl=en&q=Hello+World"; People don't usually type the target url in on the command line when invoking the browser, but I don't think anyone would argue that a website ought to be able to disallow it. Whereas what I want to do is: >$ wget -q -U firefox -O "Hello+World" >http://translate.google.com/translate_tts?tl=en&q=Hello+World >From a programming standpoint, they sure don't seem much different, and it seems strange that one would be permitted but not the other. Of course, I would have wget be invoked by TuxType, which perhaps would fall under the "no robots" clause of the Google consumer TOS. Anyway, it would cost Google nothing and would generate goodwill to allow this. Google already has supported our project via a couple dozen Summer of Code internships - it seems they could find it in their hearts to authorize Tux Typing to make use of this service. Thanks, David Bruce -- 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.
