Continued thread
GitLabButterflyOfFire / Apertium occitan français · GitLabGitLab.com
Recent searches
Search options
#apertium
0 posts0 participants0 posts today
GitHubGitHub - LibreTranslate/dixtools: Toolset to convert Apertium dictionariesToolset to convert Apertium dictionaries. Contribute to LibreTranslate/dixtools development by creating an account on GitHub.
Replied in thread
@jerry This seems like a good thread for my security concern.
I noticed a “translate” link on my post. Clicked it to see what would be used. Was disturbed to find that it’s #DeepL. This is a Tor-hostile #Cloudflare site that misleads people into thinking security is taken seriously. Which is the same thing that happends with libretranslate.com.
In principle it’d be most secure to run Argos Translate on the server. But that’s also a heavy process. If translation must be outsourced, I suggest translate.fedilab.app. It’s the same engine as #libretranslate, but without sharing translations with CF.
(edit) guess it’s a good time to republish this:
#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)
Replied in thread
@luis_in_brief We've been using machine translation in #MediaWiki for more than a decade now... (Including #Apertium for a large part of the time.)
Replied in thread
@Ashki_Faux just found this toot. https://infosec.exchange/@bojkotiMalbona/108271072631878382
There are some other tools I did not know off.
#Apertium
https://apertium.org/
#translatelocally
https://translatelocally.com/
Infosec ExchangebojkotiMalbona (@bojkotiMalbona@infosec.exchange)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)
@mousebot yeah iirc #apertium’s language support is sparse and obscure. #ArgosTranslate uses neural networks and Apertium does not, FWIW.
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)
#Apertium stream parser and generator written in Common #Lisp
https://github.com/veer66/cl-apertium-stream
https://github.com/veer66/cl-apertium-stream
GitHubGitHub - veer66/cl-apertium-stream: Apertium stream parser written in Common LispApertium stream parser written in Common Lisp. Contribute to veer66/cl-apertium-stream development by creating an account on GitHub.
Me acabo de comer un patrón oscuro #DarkPatterns de DeepL https://www.deepl.com/ y me ha hecho reflexionar…
Yo usaba mucho #Apertium pero como, a veces, no me chutaba bien pues me acostumbré a usar DeepL.
Pero me gusta más la GPLv3 que la MIT y, además, parte de mis impuestos van al desarrollo de Apertium. Conclusión: volveré a priorizarlo.
Lo que no pillo es por qué no es AGPLv3 si se está dando un servicio web…
barcelona.socialBarcelona social
Apertium stream parser written in Common Lisp
It is not yet in Quicklisp.
https://github.com/veer66/cl-apertium-stream-parser #commonlisp #nlp #mt
github.comGitHub - veer66/cl-apertium-stream-parser: Apertium stream parser written in Common LispApertium stream parser written in Common Lisp. Contribute to veer66/cl-apertium-stream-parser development by creating an account on GitHub.
Continued thread
What do you think of Apertium?
#Apertium is web based language translator that is #FreeSoftware #OpenSource -- think of Google Translate except it's libre.
I removed a few enums and structs from stream type family. Now ReinaRS support partially an ambiguous lexical unit. #apertium #streamparser #nlp
vec![StreamUnit::LexicalUnit(vec![Analysis {
ling_form: String::from("ab"),
tags: vec![]
}])]https://github.com/veer66/reinars/commit/3a54fa5b28dbe2a199b9375e1e352f6475475299
norze.worldNorze World
Est-ce que vous connaissez/utilisez/améliorez #apertium ?
#question
------
Une #plateforme #libre #opensource de #traduction automatique
https://www.apertium.org/index.fra.html
www.apertium.orgApertium | A free/open-source machine translation platform
Great news, everyone! Meet #Apertium and #DeepL: new translation plugins in #ONLYOFFICE
https://www.onlyoffice.com/blog/2021/06/meet-apertium-and-deepl-new-translation-plugins/
I hope GCC 8.5.0 is not to new to install on CentOS 7 and new enough to compile #Apertium’s lttoolbox.
pleroma.in.thSoapbox
Replied in thread
@lealternative noto con piacere che sia stato menzionato #Apertium.
Se non l'aveste menzionato, ve l'avrei suggerito, soprattutto perché è uno dei pochi che traduce in #sardo standard. Fa ancora degli errori ricorrenti, ma è qualcosa.
I use bordeaux-threads and external-program just for calling lt-proc. #commonlisp
norze.worldNorze World
#Apertium moved from Sourceforge SVN to GitHub already, but I didn't know.
libranet.deLIBRANET.de | Search