Hi Bruno & Alex, At 2024-12-14T01:37:16+0100, Alejandro Colomar wrote: > On Sat, Dec 14, 2024 at 01:23:09AM +0100, Bruno Haible wrote: > > Commit 3ed1de0ddccb42bae4151c7225d3fddeab04ff43 should better > > be reverted, IMO. The ISO organization or their *standards* can > > be renamed to whatever names; what matters here is what the > > *encoding* is commonly referred to. > > > > The *encoding* names are standardized by IANA: > > https://www.iana.org/assignments/character-sets/character-sets.xhtml > > The first ISO 8859 encoding there has the name > > ISO-8859-1 > > or > > ISO_8859-1 > > and the first among these is the preferred MIME name. So, please, > > in encoding names: > > * revert the ISO -> ISO/IEC change, > > * change the space after ISO to a dash/hyphen-minus. > > > > Likewise (partially) for commit d5e5db91ece5955b21ae1aedc03ba1d56d3cf423. Oy vey. Helge Kreutzmann submitted a similar bug report to groff and I was planning to make the ISO -> ISO/IEC change to its man pages. Also your point seems more strident than clear to me as regards the encoding name. If I want to refer to character encoding _not_ in the context of a machine-parsed MIME datum, I trust you're not going to tell me I need to spell with an obnoxious hyphen-minus or underscore before the standard number ("8859")...? I would then wonder why I am not equally compelled to write "ISO-9000". Or, to name a standard that comes up in documents to which I contribute, "ISO-6429" (better known to some as ECMA-48, and yes, ECMA standards routinely get the hyphen-minus). > I'm okay with reverting those if there's consensus. Would you mind > CCing the interested parties (e.g., the people that requested that > change, and anybody that participated in the discussion)? > > (I've CCed them now, anyway.) Thanks for looping Helge in. Regards, Branden
Attachment:
signature.asc
Description: PGP signature
