Whether you approve of translation or not, you need to know where they live. Found this one recently:
130.193.62.87 - - [29/Dec/2012:08:17:41 -0800] "GET / HTTP/1.1" 200 5537 "-" "Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.12 Yandex.Translate"
185.8.cc.dd - - [29/Dec/2012:08:17:42 -0800] "GET /piwik/piwik.js HTTP/1.1" 200 21928 "http:/ /translate.yandex.net/tr-url/en-ru.ru/www.example.com/" "Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.12"
185.8.cc.dd - - [29/Dec/2012:08:17:42 -0800] "GET /images/lion.gif HTTP/1.1" 200 2885 "{as above}" "{as above}"
{et cetera}
The IP was a new one on me; looks like
130.193.32.0/19
belongs to Yandex. The other one is the human, in one of those newly settled RIPE regions. Came through as Russia, as it should.
In logs it's pretty much the same pattern as google translate: Page request comes from search engine IP, blank referer, "Translate" at end of human UA. (For Russia I am fully prepared to believe Opera 9.80. Heck, I've met humans from northern Canada using every edition of Firefox back to 3.0.) All subsidiary pages come from the human IP and UA, with "translate" as part of the referer.
:: now back to irritable grumbling because G### Preview started running from 66.249 some time last month when I wasn't paying attention, and this appears to have some connection with all those referer-less iPad image hits ::
