On Sun, Oct 23, 2022 at 03:03:27PM +0300, Eli Zaretskii wrote: > If you mean the message strings (as in error messages etc.), I'm not > sure I understand.
No, strings for documents. For example, "Next: " in a navigation header in an HTML file, which should be translated appropriately if the @documentlanguage is not English. > The translations should depend on the current > locale, not on a locale the code sets forcibly. The code where I made > the change sets the locale to en_US.UTF-8, and if that fails, to just > en_US. If the locale is not an English one, but, say, French or > German, how can that code produce the expected translations to French > or German? What am I missing here? The translation is done by setting the LANGUAGE environment variable but this does not work if the locale is C. All it needs is LC_MESSAGES to not be "C" (or "POSIX") for LANGUAGE to work properly.
