lingohub is celebrating Xmas a little early this year with our feature roundup and our brand-new translation UI.

We received lots of feedback on our user interface (UI). While nearly everyone liked the look, there were some problems with the workflow and usability. Based on your input, we designed a whole new interface for translations overview and the editor. You now have the choice between using a QuickPanel for, well, quick translations, or the full-featured translation editor.
One of the most requested features is included as well: performing actions on multiple translations. You can now select multiple translation texst and change the status, machine translate them and so on.

This release contains other important changes as well. Here is the full changelog:

Translation Overview and Quickpanel

Previously this view showed all available language texts including additional information. This used a lot of space and required a lot of scrolling. Projects with 4 or more languages suffered from it. Furthermore, this view made it hard to allow multiple changes at once.
The new view shows only two languages horizontally, not vertically. Translators are much more accustomed to such a presentation. It helps to quickly scan both, source and target language, and review them. The left side shows the source language for information and the right side shows the target language for editing.
With this kind of review process a common use case is to do small changes (e.g. correcting spelling mistakes). Such small changes don’t require a fully fletched editor, hence, we introduced a so-called QuickPanel. Simply click on the target language and the QuickPanel opens. Within the QuickPanel you see context information, can change the status, and do text changes – no page reloads required.

old translation overview

vs

new translation overview

Translation Editor

The editor follows the same left side – right side principle as in the Translation Overview. The only exception here is that you can show multiple languages at once. In some cases translators like to see an additional language next to the master language. A Russian translation may help a Bulgarian translator to better understand the translation texts. Also, with the new view it is now possible to edit multiple languages at once.

Of course previous functionality such as machine translation, review process (status), comments and so on are included.

old editor

vs

new editor

Github Hook Integration

We had a Github integration from the beginning. When you authenticate your Github account with lingohub, a Web-Hook was automatically created and your repository will be synchronized. With the Github Web-Hook you can create the hook manually at Github without connecting your Github Account. One caveat though: this works only with public repositories, for private repositories lingohub needs the connection to access the resource files.

Windows 8 ready

Windows 8 introduced new format types: .resw (previously .resx) for C# applications and .resjson (JSON) for Windows Store apps using JavaScript and HTML. A lot of things have changed in detail to previous formats that you should be familiar with as a developer. You should definitely stay on top of the documentation at MSDN . Read our blog post on Windows 8.

Subscription Plans announced

In November we went out of Beta and announced our subscription plans. You can find information about Mini, Basic, Business, and Plus plans in a separate blog post. Of course, translators use lingohub for free.

Language Selection and Japanese

We live our motto “Go Global, Be Local!” that is why we are constantly adding new languages to lingohub. The old language selector was quite boring. Since we think languages are fun, the selector has to be fun as well, and now it is. Japanese is one of the new languages our service is available in.

Footer

One of our focus in the future is to provide you more and better documentation of lingohub’s features. The new footer is a first step to a better structure of our documentation.

OAuth fixes

There were some bugs with some OAuth providers. The bugs are now fixed and we added extra behavior that considers if on the provider side goes something wrong.

What’s next?

• Translator profiles: we want to help translators to show off their skills – and more.
• Better indication of the “health” of a translation including missing placeholder, too long texts, …
• Improving file upload and handling of comments
• more! Let us know what we think, we are looking forward to your thoughts.