Hi On Mon, 2019-03-11 at 08:05 +0100, Jean-Baptiste wrote: > I decided to come here as I'm unsure to understand the translation > memory server options we have with Weblate. > > this page describe the basics, and it says translation memory is > active > by default: > https://docs.weblate.org/en/latest/admin/memory.html > > But in the example settings.py, it looks like desactivated: > https://github.com/WeblateOrg/weblate/blob/weblate-3.5.1/weblate/settings_example.py#L544
It's enabled by default, the example config lists all possible backends, the default value is here: https://github.com/WeblateOrg/weblate/blob/55a5db337c09b9a6374f3db240a9eb9585a95e3b/weblate/machinery/models.py#L81-L85 > I'm also a little bit confused with the MT_TMSERVER variables. > > Here is some more documentation about machine translation: > https://docs.weblate.org/en/latest/admin/machine.html > > There two titles related to weblate: "Weblate" and "Weblate > Translation > Memory". Weblate gives suggestions based on current content of translations, Weblate Translation Memory remembers past translations and can import external translation memory. > In addition, it looks like we could use three more open-source > options: > "tmserver", "Apertium" and "Amagama". Yes, all these can be used with Weblate. Apertium is machine translation service, the other two are translation memories. Apertium might be useful companion for Weblate, especially for some languages. Amagama was written as a replacement for tmserver, but neither of them is AFAIK currently actively developed. Unless you have existing server, using built in Weblate Translation Memory is better choice that these two. -- Michal Čihař | https://cihar.com/ | https://weblate.org/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
