Auto translation option

[OnkarRuikar]

We can integrate third party translation libraries to provide auto translation of:

• entire file (while copying or in right click menu)
• selected text (select text and in right click menu)

For example we can use LibreTranslate:

// make a request to locally hosted server or well known public instance or Mozilla can host it for us
const res = await fetch("https://localhost:5000/translate", {
	method: "POST",
	body: JSON.stringify({
		q: "text to translate",
		source: "en",
		target: "es"
	}),
	headers: { "Content-Type": "application/json" }
});

console.log(await res.json());
/* { "translatedText": "¡Hola!" } */

The HTTP based API can be used with any language .py, .js, .java etc. so we can use it in plugins for VSCode, Eclipse, IDEA etc.

The auto translation will increase the translation speed.

[Jalkhov]

Hi @OnkarRuikar Yes, at some point in the team I mentioned the use of translators to work on the documents. However, in a few words, they do not promote the use of translators and at some point I understand why, and is that translators sometimes change the essence of what is being discussed, however, I personally use DeepL for my translations, BUT, I always check the output of this, to verify that everything goes accordingly.

Personally I would say that you can use translators as long as it is a support and not the one that does all the work.

Back to the topic of discussion. Some time ago I had the opportunity to work with LibreTranslate, and although I think it is a spectacular project, it still has a long way to go to provide quality translations, specifically of the kind we are looking for in MDN. Also, the api has certain problems when it comes to translating documents that have more than just text, when it comes to code (both source and Markdown) for example, it tends to translate them (tags, etc...), and when translating an entire document, in short... let's say it can be a disaster, which can lead to a waste of time. Even DeepL translates things "it should not".

I do like the idea, but LibreTranslate would have to be tested a few times to see if it is up to the task, and in any case, it is recommended to use it only on a small scale, small selected texts, AND by hand, checking that everything is OK.

[OnkarRuikar]

Personally I would say that you can use translators as long as it is a support and not the one that does all the work.

I totally agree.

[Jalkhov]

I think that, in summary, for now we have to wait for several things:

1. That the project is more stable.
2. That LibreTranslate offers a little more quality in terms of your translations.

However, with the second point you can do a little research and see how much the quality of translations has progressed, make comparisons with other translators, use cases where texts are tested with code, etc... Personally for now I do not plan to get into it, but if you want to dabble in it, welcome, and post the results here.