Mention that Locales and Translations section is specific to glibc

[grtcdr]

This pull request closes issue #821.

[abenson]

I'd explain that musl doesn't support locales.

[grtcdr]

I'll do that right away.

[grtcdr]

Would you consider https://wiki.gnome.org/Initiatives(2f)Wayland(2f)Applications.html a reasonable replacement for the currently broken GNOME link?

Here's an archived version of that URL for comparison: https://web.archive.org/web/20240620195313/https://wiki.gnome.org/Initiatives/Wayland/GTK%2B

[classabbyamp]

setting LANG should still work on musl for applications, iirc

[grtcdr]

Does that environment variable have any effect though? https://wiki.musl-libc.org/environment-variables doesn't list it.

EDIT: It seems that it does, https://wiki.musl-libc.org/functional-differences-from-glibc.html says under the "Default locale" section, "In the absence of the LANG and LC_* environment variables, POSIX leaves the default locale (used when "" is passed to setlocale) implementation-defined.".

[grtcdr]

@classabbyamp: I phrased things differently to take into account the fact that musl does indeed support LANG. It would be great if the musl documentation had anchors for the different headings because then we could reference that section.

[classabbyamp]

musl itself doesn't support LANG, but most applications will use LANG to set the language, even in the absence of system locale support (like on musl)

[classabbyamp]

/etc/locale.conf is just sourced by a profile.d snippet (/etc/profile.d/locale.sh) so it should apply regardless

[grtcdr]

I understand, I said it wasn't required because it apparently isn't. That statement does not negate yours, though.

[classabbyamp]

please squash your commits into 1 with all these changes, then this should be good to go

[grtcdr]

Okay, all set :)