New Google Translate languages
techcrunch.com
techcrunch.com
https://translate.google.com/#en/ja/six%20hundred%20sixty-si...
https://translate.google.com/#en/ja/eleven%20thousand%20one%...
Interestingly I wasn't able to reproduce it with English/Russian translation, maybe they hardcoded it somehow, or maybe neural network for Russian hasn't rolled out yet.
Translation is hard.
Alternatively, is there some open/published work with comparable performance?
Dumb question (maybe?). How is it learning since it's not getting any feedback on what is the right and wrong answer?
For Gmail and stuff I get it, but translate and maps are data projects, not software projects, which take hard work by thousands of people to build. It's extremely hard to build a competitor, and so I refuse to contribute to the existing de facto monopoly.
I was trying to point out that if you're in Cambridge, MA and you voice search for "transit directions to Harvard Square", you should get directions to the well-known public square and commercial hub, not a mall parking lot in Charlestown.
After I tried to convey this through an interface that had no option for "you're failing to give directions to this extremely relevant place", they testily told me that the mall data was 100% correct. A team of people who had probably not been to the Boston area questioned who I was to tell them what is or isn't named Harvard Square.
Eventually I got it fixed by Google's real bug report process: bringing it up in conversation around people who worked at Google.
Well, that wouldn't really help anyone. They would need to publish all translation data to help anyone make a competitor, which is not in Google's interest.
So "is still learning" just means that it's still adding to its corpus of examples over time.