eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

225
active users

#libretranslate

0 posts0 participants0 posts today

L'expression "Intelligence artificielle" n'a été publiée dans cette langue cible que sur papier, à ce jour.

Du coup voici le dernier (27500 pas) incluant cette expression: tu peux dire "prems".

La particularité de celui-ci, c'est que j'ai fait de la "traduction inversée" pour près de 57000 sous-titres de films, d'où l'appellation OS : OpenSubtitles.

Lien : huggingface.co/spaces/axxam/Li

Set up LibreTranslate for my Mastodon instance. It was pretty quick and easy with the only difficulty being the short wait when it downloads the initial data for the various languages. Quite happy with it. A simple Translate link appears under properly tagged posts that I just click on. Cool beans and does not rely on any sort of external service. Two thumbs way up. #mastoadmin #mastodon #libretranslate

Replied in thread

@Tutanota I have high hopes for #LibreTranslate and have played around with it a bit. Sadly, at least for Japanese to English, the results are not quite at a quality level where I would use it as my main translation engine.

Really looking forward to what that project might become a few years from now.

You might know that #Fedilab runs its own translation server (using #LibreTranslate).
But did you know that the app also supports two other translators?

- #Lingva: you won't need extra steps though you can change the default instance.

- #DeepL: A more powerful translator. It's a paid service but you can get 500,000 characters per month for free.

Everything is configurable in settings Have a look to media descriptions).

More about getting a free DeepL api key: support.deepl.com/hc/en-us/art

Так, официальный клиент #Mastodon умеет переводить посты через #LibreTranslate, который указан в настройках сервера мастодона (перевод не супер, но есть).

А какие клиенты ещё так умеют? В #Husky я не нашёл заветную кнопочку.

Petit bilan après avoir utilisé @Tusky de nombreuses années et #Moshidon depuis 2 mois.

Ce que j'aime bien chez #Tusky :
-la sobriété, les raccourcis # et @,
- l'historique des modifications sur les publications (facile à consulter).

Ce que j'aime bien chez #MoshidonApp :
- la traduction avec #LibreTranslate,
- l'ergonomie + switch avec Accueil-Local-Fédéré,
- les suggestions dans "Search".

Mais crash lors de l'écriture.

I've been experimenting with enabling translation on my instance and since I've seen zero documentation about how to configure LibreTranslate with a purchased api key, I'm going to share my findings here.

Pretty much every guide out there for enabling translation on a Mastodon instance using LibreTranslate assumes that you are going to be setting up the LibreTranslate server yourself. That's admirable, but translation is pretty resource-intensive. When I tested this on my instance, it was taking about 2 seconds to translate a post, and even longer for longer posts. Plus there were some languages that weren't working at all. That was probably on me for not setting up the language packs correctly. Maybe I'll give it another try, but somewhere in the middle of wrestling with the translation server, I realized that I'm here to run a Mastodon instance, not a LibreTranslate instance, so I went and purchased an api key from LibreTranslate for their lower tier of $29 a month (good for 80 translations per minute). Based on the average donations we get each month, that seemed a reasonable cost that we could afford. The trouble was, configuring the instance to use the api key didn't seem to be working at all.

Now if you go to libretranslate.com it lets you play around with the api and shows what the post request and the subsequent response looks like. In the post request and in the api documentation, the endpoint for the translation service is:

libretranslate.com/translate

but if you set LIBRE_TRANSLATE_ENDPOINT to that value in your .env.production file, it won't work. After a bunch of googling and experimentation, I finally went and looked at the pull request for this feature on GitHub. And that's where I saw that in the code for the post request it takes the configured LIBRE_TRANSLATE_ENDPOINT value and then adds the "/translate" at the end of it.

Even though I was sure I had tried this before, I set LIBRE_TRANSLATE_ENDPOINT to:

libretranslate.com

Without the "/translate" on the end. I restarted the web service and cleared the cache and it started working perfectly.

It'd be nice if any of this was actually documented somewhere.