November has passed uneventfully in Budapest, and in gearing up for the holiday season, the Translation Proxy team has put out a few new features working behind the scenes. The system is now more stable when handling ASP.NET pages, able to handle UTF-16/32 pages without a hitch, and in a little housekeeping, you can now request Support to remove pages of a given status code from the project. See the details after the jump!
The Easyling team kept busy during most of October on household chores and bugfixes. Our Content Connector framework/In-Context preview capabilities underwent significant improvements, and New Content Detection is gearing up for full-feature status with some awesome optimizations now complete. Pretty much all of the improvements this month were of the invisible but indispensable variety that improve system stability in all corners. Stay tuned for more features and fixes, Christmas is a-coming!
Building upon the foundations laid down in previous releases, September brings you a brand new feature in Easyling: Direct Translation API. This allows content providers to integrate a fast translation service for various reusable content, such as newsletters. See the details after the jump! Direct Translation API (BETA) The aim of this feature is to receive and translate texts or HTML fragments (e.g. parts of an HTML newsletter) without the need of visiting the translated website via the proxy, leveraging only existing translations in Easyling’s dictionary.
How was your summer, dear reader? Over here, the team was busy taking turns going for a swim in the heat on one hand, and on the other, sticking to development, where the incremental improvement of Easyling doesn’t stop. We have rolled out some invisible and some visible changes to augment Easyling throughout August. Here’s our tally for the month. JS IIFEs Our readers who are well-versed in web technologies will agree that translation of text in JavaScript is a gold mine of edge cases.
Summer is in full swing, and there was no shortage of various convenience fixes, visible and invisible improvements in Easyling this July. Here’s what kept us busy these past few weeks. Subdirectory publishing protection Reverse proxies sometimes lack configuration to armor them against recursion in the page source. These are the cases where we end up with URLs collecting path segments infinitely, such as /en/en/en/en/contac-us. We have rolled out a little something on the backend that will detect these problematic structures.
The sweltering weather in Budapest would have ground all work to a standstill if not for our air conditioning. This way, fortunately, we could stay out of the blazing heat and focus on bringing you new features and fixes to make website translation easier. This month, we added integration with Google Neural Machine Translation, as well as a more robust memory-powered pre-translation system. See the details after the jump! Google NMT Integration We have been offering integration with Google NMT for quite some time now, and we’ve also been following the development of Google neural net-powered MT system with great interest and the occasional internal prototype.
If I had to point out one feature from May that is the most important, it would be the new crawl statistics UI (part of the Dashboard II initiative). There were a number of stability and efficiency fixes as well, but those pale in comparison to the Dashboard II’s newest member. See the full details after the jump! New Crawl Statistics UI After the Complexity Matrix, the next addition to the Dashboard II’s capabilities was the new Crawl Statistics UI.
April saw few new features, but those few were quite important. As Microsoft shuttered the Data Market and Bing Translator, we migrated our code to support its successor Microsoft Translate API. Also, we rolled out a new project feature that lets us handle new HTTP methods (such as DELETE or OPTIONS) where needed and previously unavailable. See the full details after the jump! Microsoft Translate API Integration Microsoft has long publicized its decision to shut down the Data Market service and with it, its Bing Translator API.