I wrote something about translation and Bash scripting:

https://cameracode.coffee/argos-translate-script/

#translation #argostranslate #bash #linux

agros-translate (https://github.com/argosopentech/argos-translate) is really a great tool. I use the CLI version with the argostranslategui

Comes handy when imporving translations for #rstats and other tasks.

#argostranslate

@publicvoit If the doc is in my mother tongue I simply OCR & store as #DjVu with a scan of the postmarked envelope as the last page. But what if it comes in another language? That’s not covered in your process. I sometimes feed the OCRd txt into a LaTeX doc, format it similar to the original but add a 2nd column for my 1st language & use #ArgosTranslate to fill it in.

I have been using Firefox Translations (aka #bergamot) for some time. It enables client side (local, no web server) in-page translations. It is quite useful and the results are good. What is the experience among #fediverse users? #Argos translate (local) and #LibreTranslate (web) are subjectively better IMHO (not tested) but not well integrated in the browser.

https://github.com/mozilla/firefox-translations/

https://github.com/argosopentech

https://libretranslate.com/

#mozilla #firefox #argostranslate #nlp #machinetranslation

I have been using Firefox Translations (aka #bergamot) for some time. It enables client side (local, no web server) in-page translations. It is quite useful and the results are good. What is the experience among #fediverse users? #Argos translate (local) and #LibreTranslate (web) are subjectively better IMHO (not tested) but not well integrated in the browser.

https://github.com/mozilla/firefox-translations/

https://github.com/argosopentech

https://libretranslate.com/

#mozilla #firefox #argostranslate

@simonblackley Got to the b1 level in both which is still far from fluent. Both French & Dutch put the adjective after the noun, but then Dutch has other structuring that orders words like Yoda. Yet Yoda is still quite understandable. The very different ordering may be what screws up #ArgosTranslate to the point of choosing the wrong words which is perhaps a consequence of Argos’ neural nets.

I’ve been telling the Belgians to send me correspondance in #Dutch instead of #French thinking that because Dutch is closer to English, it probably also auto-translates better. That choice was an absolute failure. #ArgosTranslate from nl to en is an absolute disaster. I don’t care about perfection but nl to en is often totally incomprehensible.

@argosopentech @mousebot I think it’s rare for a website to lack a privacy policy. Perhaps more common with non-profit sites, but when a site handles high volumes of users’ potentially quite sensitive info it’s reckless not to have a privacy policy. You cannot prove to the public that LT runs #ArgosTranslate unmodified, but even if you could it’s unreasonable to assume all users are coders.

@mousebot yeah iirc #apertium’s language support is sparse and obscure. #ArgosTranslate uses neural networks and Apertium does not, FWIW.

@popolon @strawberryfieldsforever@koyu.space #DeepL shares every translation with a tech giant & deceives users about it. Creating a DeepL frontend would not bypass #Cloudflare, just as #Lingva does not bypass Google seeing the query text. The best privacy-respecting option is to run #ArgosTranslate locally. https://infosec.exchange/@bojkotiMalbona/108271072631878382

me: What is “javascript disabled” in Dutch? #argostranslate: “javascript gehandicapt” #badTranslation

me: What is “text browsers” in Dutch? #argostranslate: “SMS-browsers” #badTranslation

Update:
❌ #GoogleTranslate (#PRISM)
❌ #YandexTranslate [tax(profits) →Putin’s war]
❌ #DeepL (shares sensitive txt w/tech giant; misleads ppl about it)
❌ #LibreTranslate.com (shares sensitive txt w/tech giant; no privacy policy; solicits trust w/buzz phrases “libre”, “free & open”)
🤷 #lingva.ml (FOSS frontend; still Google)
🤷 translate.fedilab.app (no privacy policy but no evidence of mishandling data either)

Running locally:
✅ #ArgosTranslate
✅ #Apertium.org
✅ #translatelocally.com (EU funded)

Trustworthy translation tools:

❌ #GoogleTranslate (#PRISM corp)
❌ #YandexTranslate (tech giant)
❌ #DeepL (shares sensitive queries w/tech giant & goes to great lengths to mislead users about it)
❌ #LibreTranslate.com (shares sensitive text w/tech giant; no privacy policy; solicits trust using buzz phrases like “libre”, “free & open”)
🤷 translate.fedilab.app (no privacy policy but no evidence of mishandling data either)
✅ #ArgosTranslate running locally on your own PC inside #Firejail

@Beowulf @novichan @tetrapyloctomist @argosopentech #ArgosTranslate should be ppls 1st choice b/c it’s the only way to avoid snooping. When reading a doc, if a sentence is sufficiently botched then Yandex or DeepL could be used just for small pieces of the whole. When /producing/ a doc, I always include the original text along with the translation so if the translation is bad the reader isn’t stuffed.

@novichan @tetrapyloctomist (update) #DeepL shares your sensitive translations with #Cloudflare, so privacy is in the shitter w/them. I suggest installing #ArgosTranslate and running it locally.

@Tutanota @Mixtape @VikingKong@distrotoot.com Actually I just discovered #DeepL is a #Cloudflare site, so that explains the privacy issue. Indeed DeepL should be avoided. And note that #LibreTranslate.com is also a CF site. Better to use https://translate.fedilab.app/ which is a non-CF instance of #ArgosTranslate.

I've been working on translation-cli 🈶 🈳 🈹 tool as my sideproject for some time. I'm currently using a #bash script that works by making requests to pons.com api. However I've only now found out about #libretranslate that's a web interface to #argostranslate. I'm very hyped about both of the projects and I'd like to include #libretranslate into the next iteration of my project.

https://community.libretranslate.com/

#cli 💪