Feature request: making gettext more robust

2023-06-15 Thread Gergely Kalmár
Hello all, It seems that gettext is currently quite permissive – it falls back to the default language whenever a translation file is missing or if the requested message ID is missing from the translation file. This can lead to errors slipping through easily. Consider this example from the doc

Re: Feature request: making gettext more robust

2023-06-15 Thread Tobias Kunze
On 23-06-15 04:29:59, Gergely Kalmár wrote: >It seems that gettext is currently quite permissive – it falls back to the >default language whenever a translation file is missing or if the requested >message ID is missing from the translation file. This can lead to errors >slipping through easily.

Re: Feature request: making gettext more robust

2023-06-15 Thread Jure Erznožnik
The behaviour is the same on Android. iOS makes it more straight-forward because you HAVE TO have all translations in all languages you support. LP, Jure On 15. 06. 23 16:15, Tobias Kunze wrote: On 23-06-15 04:29:59, Gergely Kalmár wrote: It seems that gettext is currently quite permissive –

Re: Feature request: making gettext more robust

2023-06-15 Thread Michiel Beijen
> On 15 Jun 2023, at 16:15, Tobias Kunze wrote: > > On 23-06-15 04:29:59, Gergely Kalmár wrote: >> It seems that gettext is currently quite permissive – it falls back to the >> default language whenever a translation file is missing or if the requested >> message ID is missing from the translat