Missing support for fallback translations about gotext HOT 3 CLOSED

Hey @m-horky, this sounds like a good improvement.

So, how would the implementation look like? Would you extend the support for this syntax (en:es) in the Config.language field? So current users don't have to modify anything, but after this change, if anyone wants to add the : option to it, it would work? Or maybe a different field?
I prefer the former, but gettext docs doesn't mention anything about the en_EN syntax support for that env var, so it seems you can't do something like en_EN:en_US:es_ES:es_AR:br, or at least it's not clear how would it work?

I'm up to support this kind of definitions, they seem appropriate, unless there are specific docs in gettext suggesting otherwise.

What do you think?

from gotext.

I started writing my ideas here, but then I went to check whether they were possible to do and I managed to create a proof of concept. I'm not totally happy with it, especially the functionality of Locale.GetActualLanguage() may be better of somewhere else, but I'd call it a start.

I opened draft PR #73

from gotext.

Hi @leonelquinteros, when you have the time, could you look at the mentioned PR and do some fast review? It is still draft as there surely are things to improve, but I'd like to know if its ideas were something that would fit into the library.

from gotext.