0) I noticed an obvious typo in the manual. Some grepping also showed the same typo in some translation strings. 1) Entirely untested patch to be attached shortly.
Created attachment 4998 [details] Fix typo (LC_TYPE -> LC_CTYPE)
Created attachment 4999 [details] Fix typo (LC_TYPE -> LC_CTYPE) Just the commit messages was exciting enough, but people probably want the patch itself too.
Thanks, I've committed the manual patch. You'll need to send the translation fixes to the respective translation teams; we only import translations unmodified from the Translation Project, not change them locally in glibc.
(In reply to comment #3) > Thanks, I've committed the manual patch. 0) Thanks. > You'll need to send the translation > fixes to the respective translation teams; we only import translations > unmodified from the Translation Project, not change them locally in glibc. 1) Looking at my patch again it seems these are just outdated translations (ie, the typo in the original string was corrected but the translations aren't yet based on the corrected string). So once these translations are redone they will use the correct string. There's little point in sending these fixes to the translations teams. These are probably aware that their translations aren't up to date. 2) It looks like I have an excuse to do nothing about the translations!