[PATCH v4 1/5] posix: allow getopt_long to match translated option names

Florian Weimer fweimer@redhat.com
Wed Jun 4 08:37:41 GMT 2025


* Vivien Kraus:

> It is possible to support translated long option names in a program by
> adding new option records with the translated names in the options
> array. However, it is significant work for all packages.
>
> The discussion was started on bug-standards and support in glibc may
> be desirable [1].
>
> With this change, getopt will try and match the untranslated options
> names, then the translated option names if not found.  Abbreviations
> will only match the untranslated names.
>
> [1]: https://lists.gnu.org/archive/html/bug-standards/2025-05/msg00000.html

I don't think this is a good idea.  It can make cross-cultural
collaboration more difficult.  Office applications (particularly
spreadsheets) already use translated names for their programming
languages.  It makes it more difficult to find appropriate guides and
apply them to your own environment.  The proposed approach for
getopt_long mitigates some of the problems because the untranslated
option names always work, but there will be considerable friction once
this feature gets significant traction.

Thanks,
Florian



More information about the Libc-alpha mailing list