Build 306 – custom API key for Google Translate service
Google Translate and Microsoft Translator are external services and we can’t make an impact on changes implemented by Google and Microsoft to their translation services. However, we try hard to have one’s finger on the pulse and update appropriated API features in Sisulizer after changes in Google Translate and Microsoft Translator services. Recently, Google implemented some limitations for avoiding overloading their service by users, and this cause locking service after exceeding translations limit. Solution is personal API key for Google Translate service. In build 306 our developers implemented possibility of adding custom Google API key. You can generate your Google Translate API key on this Google site. Next paste this key to “Tools” menu -> “Translation Engines” -> “Google” -> “API key” field (indicated on below screenshot by red rectangle). If you don’t want to use your own Googel Translate API key, leave this field empty – in this case Sisulizer uses its own key, however we recommend to use your own key generated on Google website.
Our developers updated in build 306 also Microsoft Translator (MS Bing) API from 1.0 to 2.2. This new API comes with new languages. Similar as for Google we recommend using a personal API key. You can get this key on this Microsoft website. Next paste this key to “Tools” menu -> “Translation Engines” -> “Microsoft” -> “Application id” field (indicated on below screenshot by red rectangle).
So, if you have Sisulizer Enterprise and use Google Translate / Microsoft Translator translation engines, we highly recommend upgrade your Sisulizer to build 306.
Janusz
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
Comments
Further to my earlier post, the Microsoft free translator seems a bit more lenient and has got to about 25% so far without complaining.
If the free services do lock you out, Sisuliser also allows you to integrate with a paid service from WorldLingo.
We had good experience with the test localization of our German website http://www.sisulizer.de. After using an own API key it reached easily 100%. If you use the public key you share the daily amount with others. Needless to say that there is no official info about a quota. But using an own key is definitely needed to use it successfully.
In anyway machine translation is just a nice solution to get a rough preview on how a translated output might look like. We use machine translation to preview http://www.sisulizer.com in German language. Since our sales department is located in Germany we have native German speakers and we could judge the results. Parts of the machine translations had been nearly usable but most parts are simply hilarious. So everything had to be localized using a human translator (what was clear from the beginning). The machine translation was excellent to see if the localization process of the web works in general. We could see if every string was translated, scripts and program logic was still working and fine tune the paragraphs flow (since German strings are somewhat longer than the original). For this task machine translation does an incredible good and fast job. Much better than any pseudo translation can do.
But for the published web the machine translation was no option. There is no other option than a human translator – or even precise – a native speaker with localization experience.
Nice concept, but don’t expect this to work for applications of any size. Google locked me out with error message saying suspected terms of use violation after translating just 1% of my application!