In this case, you're running into a limitation inherent in machine
translation. The Translation API was designed to translate blocks of
text, not single words. It is not the same as the dictionary which
translate.google.com offers, so it cannot be relied on to translate
single words or even small phrases. In fact, in my experience, it
struggles with anything less than three words. And even then, it can
still have a tough time.
On Nov 10, 2009, at 7:17 AM, mihoo wrote:
>
> I understand that API doesn't return all translations. I would be
> satisfied with the first translation from the list.
> But in some cases the translations exist and API doest'n return any of
> them. It returns the same word I've asked to translate, in original
> language.
> Like it does in cases when there are no translations available. I ask
> for "nag" and it returns "nag" (no such word in polish). I'd like to
> see "konik" instead (the first translation) .
> Michal
>
> On 10 Lis, 13:33, Jeremy Geerdes <
jrgeer...@gmail.com> wrote:
>> Unfortunately, the API only returns the first result for translation,
>> and doesn't include all the other or alternate definition
>> information.
>>
>> Jeremy R. Geerdes
>> Effective website design & development
>> Des Moines, IA
>>
>> For more information or a project quote:
http://jgeerdes.home.mchsi.comhttp
>> ://jgeerdes.blogspot.comhttp://
jgeerdes.wordpress.com
>>
jgeer...@mchsi.com
>>
>> 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, athttp://
jgeerdes.blogspot.com