Too many of us have thrown up our arms, stopped being belligerent and surrendered. They will most likely think that we are happy GOOD campers and will most likely do no such thing with transliteration.
The closer that I am looking at GOOG and their API the more I am starting to develop an attitude of "oh what a sorry and unfortunate situation" and here is just a couple of reasons that only scratch the surface. Over in the YouTube camp, where I have been doing tons of work, one of the very frequent issues revolves around some form of "custom" or what they call "developer" categories. The sad part is that most of us are reinventing THE BIG WHEEL, you know the one that brought GOOG to the top of the search and indexing hill. Often, we are ourselves forced to make our own mess of something that GOOG itself is so good at. There is tons of room in that area - even for paid GAE based offerings that everyone could leverage. Now, lets swing back to this issue of Translation API. While some desperate folks are willing to pay for the service, let's face it, most sites will not be abel to afford it for dynamic content, beyond translating field labels and such. However, what everyone could afford to do is to cover their costs and perhaps even make some money by showcasing AdWords, that are in proximity of the content that is being translated. But even then, we all know how mostly lousy job gmail does in terms of placing ads based on email content. Most of our sites have tons of other vidal non-user identifying user profile information. However, in most of these cases, it is very difficult to use those widgets gizmos that they are building because they work in only predefined manner. In my ethnic community use case, I could have content that is written in multiple languages and where it's not all or nothing at the page level. So, what would be wrong if GOOG did what Facebook and others do with their apps - where we submit them and somebody takes a look and approves them. Heck, I would even spend some money to cover costs of somebody doing so. Nahhh, personally, I am no longer disgusted nor will I be belligerent any more - because I have thrown in my towel ! Thansk GOOG, not for your free services because you got free QA services from all of us - not to mention insight into what real world needs. Rather, thanks GOOG for teaching me a valuable lesson about ethics and trust. On Wed, Jun 8, 2011 at 3:31 PM, urukay <[email protected]> wrote: > :) nojust my NB got little bit crazy and sent the message earlier, or > maybe it was me :) > > Yes,we can't be sure rightnow about Language APIs, but about translate > API we whogan update here > http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our-apis.html?showComment=1306492113152 > and maybe google willalso do something abot transliteration also. > > > > On 8. Jún, 18:19 h., Zdravko Gligic <[email protected]> wrote: >> > Looks like google will chargethe the use of Translate API, they're >> > working on it. So after the December it >> >> Did some 100 character GOOG limit cut off this message ;?) > > -- > 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. > > -- 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.
