Whipping a Startup Idea

xaker12011-10-22 13:43:47

Machine translation from one language to another

xaker1, 2011-10-22 13:43:47

Hello habralyudi.

After the localization of the next open source software, the idea arose to help in this hard work.

A database of phrases is created in various languages, for example, English-Russian-Bel-German: accept-accept-jump-akzeptieren.
Next, software developers are offered an interface for translating their software. Those. the developer uploads a language file in a certain format (xml, plain text, or some other), the service parses the phrases and produces similar language files in the selected languages. Naturally, the software must support these language files.

If the phrase is not found, offer the developer (or users, for example, as in LibreOffice) to translate the phrases themselves.

With this scheme, the developer gets the opportunity to work out the software in more detail without translating into different languages. Benefits

of this project:
Developers they do not need to do translation, or to do much less translation into different languages.
Users , because they have the opportunity to use the software in their native language.

What do you think about this idea? Perhaps there are already similar implementations, or the idea is worth implementing and you want to leave your wishes?

Answer the question

In order to leave comments, you need to log in

9 answer(s)

Fastto, 2011-10-22
@Fastto

Look at the internationalization of the YII framework, for example, the link
Translation->Message Translation Section One of the types of translation sources is
CGettextMessageSource, which allows you to translate messages stored in the GNU Gettext
format. developers

admin4eg, 2011-10-22
@admin4eg

It's long overdue, but the trouble is that we need a certain standard for the design of software localization, how to graft it onto existing applications?

LastDragon, 2011-10-22
@LastDragon

> What do you think about this idea?
There was an idea for a somewhat more global project, everything is practically the same, but only the possibility of self-translation by users should have been mandatory.
Add. functionality:
1) Tracking the software and its versions, with the ability to migrate old strings to the new version
2) API for unloading the translation so that the software can pick it up itself
, etc. the idea is actually useful, but for developers in the first place, I doubt that users will translate something themselves.
Monetization - after accumulating a sufficient database of words, you can offer automatic translation of software to various companies (if you wish, you can translate entirely by involving translators). The only problem is that, as a rule, the matter is not limited to one translation.
> Perhaps there are already similar implementations of
glotpress, somewhere about half a year ago I asked a similar question, but only its code……………………… it’s faster and easier to write a new one than to find and / or fix something in it

Wott, 2011-10-22
@Wott

bullshit
The problem with automatic translation is that phrases are context-sensitive and the translation must take into account the terminology and sometimes just invent or select words / phrases. Sometimes one word in one language has to be translated differently in different places and you have to be smart.
Simply translating from one language to another for the interface is catastrophically insufficient.
By the way, automatic translators (Google, MS) have the ability to translate within the context - for example, the entire page - it turns out better.

Sergey Volkov, 2011-10-22
@format1981

The service will be in demand.
And if there are several translation options for a word, then show it to the user of the service, and give all the options to choose from.
And add the option: "Show translation options" - if the option is not enabled, then everything is translated automatically, by default.

Alexey Sundukov, 2011-10-22
@alekciy

The idea to implement this as a service (I would say in the form of a convenient service) is not bad in principle. But you need to understand that in this "market" his long-term technical developments are already ready. All you need to do is just cook them right. An example of such cooking: git and github.
I recommend working through gettext .

Stanislav Agarkov, 2011-10-22
@stas_agarkov

Fine. But the problem is that in different contexts the same English terms mean different things.

draf_grakula, 2011-10-24
@draf_grakula

The idea is certainly interesting, a base with popular phrases for software would be in demand.
But it seems to me that people, especially native speakers, translate better.
Check out this site:
www.transifex.net/start/

egorinsk, 2011-10-24
@egorinsk

translations.launchpad.net/ - isn't that right?