[PATCH v3 0/6] Support translated long option names in getopt and argp
Joseph Myers
josmyers@redhat.com
Mon Jun 2 17:09:36 GMT 2025
On Sat, 31 May 2025, Vivien Kraus wrote:
> Le vendredi 30 mai 2025 à 16:05 +0000, Joseph Myers a écrit :
> > I think if would be best if translated option names were only supported
> > when a context is specified, to avoid translations of a word also used
> > (and marked for translation) other than as an option name quietly
> > changing
> > how a program behaves.
>
> For getopt, I believe developers can enforce this rule by setting opttextdomain.
I think it should be the default. That is, if an application has
translated messages, but has not done anything specific to enable
translation of option names, it should *not* start accepting a translated
version of a single option name simply because that happens to be a word
that's also translated in a different context.
--
Joseph S. Myers
josmyers@redhat.com
More information about the Libc-alpha
mailing list