Follow-up Comment #6, bug #34530 (project make):
The strings are the keys to the translation lookup table, yes. So changing
the string changes the lookup key. I don't know what you mean by "change the
hashes at our end"? The hashes are generated at runtime by the gettext
library when you ask for the translation of a string.
As for updating the translation files with the new key values, we do not store
the translations ourselves (if you check CVS you'll see there are no
translation files there). They are stored by the GNU Translation project and
when we build GNU make for distribution we download the latest versions from
there. If you wanted to update the translations yourself you'd need to modify
the translation files and send them up to the translation teams so those
changes could be incorporated by them.
In any event, as I've said, I'm not going to make this change without a
consensus of the GNU project, regardless of how much effort that will be. For
good or bad this is the standard behavior for the GNU project and GNU make is
part of the GNU project. This is just as if someone wanted to change the
coding standard for GNU make: you have to change the GNU coding standard,
which GNU make uses. That's the only way this will happen.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34530>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
