> Date: Sun, 06 Nov 2022 16:09:59 +0000 (UTC) > Cc: arn...@skeeve.com, bug-texinfo@gnu.org > From: Werner LEMBERG <w...@gnu.org> > > * I think it would be OK if the documentation says that i18n support > for sorting only works with awk programs that understand `LANG`.
Gawk understands and uses any LC_* and LANG variables that Posix requires, if Gawk uses glibc. Otherwise you depend on the particular library, and no one says that all of them use the same collation order that glibc does, for the same locale. > * Let's assume that GNU awk behaves similar to, say, GNU sort. The > collation order and input encoding gets controlled with `LANG` – > looking into the awk info manual this seems like a reasonable > assumption. > > As far as I can see, my two issues could be resolved by a shell > wrapper around the awk program that analyzes the (yet to be added) > `@documentencoding` and `@documentlanguage` settings in an unsorted > index file. From those two settings it synthesizes a proper `LANG` > argument that gets passed to GNU awk, et voilà. > > Am I missing something? You assume that for every encoding in an Info document every user will have the corresponding locale installed and supported by the local libc? (And it isn't only the language, it's also the codeset -- which I'm sure you know.)
