i18n: use gettext to allow translation of plugins

[Exirel]

The problem

Sopel is in English only. I'd love to see it speaks in French, and I'm sure other people would like to see Spanish, German, Dutch, and so many more!

The solution

In Python, there is gettext (see the Python documentation for i18n), so the first step is probably to have a look and see how to use it in Sopel. Then, ensure that plugins can be translated too. After that, we can open Sopel for translation by the community, maybe by using Transifex which has an open-source free plan.

[half-duplex]

I've also seen https://crowdin.com/ around, which also has a free option for open source, but that's the extent of my familiarity.

[dgw]

I already have to maintain localization files through Crowdin for another project, and am not interested in doing so for Sopel. If there was a way to let others maintain and release translations for that project separately, I would.

Let's take inspiration from YOURLS: make translations installable as packages, just like plugins, so they don't have to be maintained in lockstep with core, and so anyone can release any language they want with or without our blessings.

[RhinosF1]

What about translatewiki ?

They automate the import and export. You could still build config that could allow it to be updated seperately to Sopel.

[Exirel]

make translations installable as packages, just like plugins

100% agree.

[dgw]

Calling it a wishlist item.