Localization API: I need your help

In January 2014, a localization request came to us from Habr asking whether we have an API. Unfortunately, we have no API (and our translators, too, we asked), but we have long thought about developing a service that would allow developers to localize their applications painlessly into several languages ​​without sending files by mail, etc. Now we are in the process of ERP implementation, we plan to remake the site, and still use the server TM program . Surely now is a good time to combine these efforts and create a service that is useful to our customers.

We know how to improve the quality of translation and service, and that's what application developers need from a localization service, we represent very roughly, and therefore asked the letter's author about this. Below is his answer (spelling and punctuation preserved).

Hello, Denis!
')
I studied the API of several services, it speaklike , translated . net and translationcloud . I can make some comments - the wishes of which were not enough:

1. Ability to specify a comment in the element being translated - context to avoid clumsy translations off topic

2. Ability to translate short pieces.

3. The presence of a callback system , so that the transfer is sent to us as soon as it is completed.

4. The possibility of prioritizing the request. Urgent bugfix release for example, no time to wait, we will pay more but the translation is needed yesterday =))

5. I would like the translators to have some kind of story on the translated phrase, since it is often necessary to change some elements in the phrase and by and large it will remain the same. For this, it is necessary that your ERP be linked to unique client codes and the history of localization is stored.

In general, I would like the localization of the same android to be performed simply from the IDE by clicking on the xml files and selecting the menu item “Localize”, because now we have localized the same android through a request for templates from the server and the subsequent build of apk .

We want to make the service as useful as possible to the largest number of mobile application developers, and therefore we are happy to hear your opinion on this matter.

To do this, we have prepared 3 questions, the answers to which will allow us to understand which way to go:

1. What features do you expect from the localization service?
2. What functions are critical, what are desirable?
3. Some information about you - who are you, what are you doing, what company do you represent, what is the company doing?

You can also comment on the need to create such a service, not limited to our questions.