All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Bruno Haible <bruno@clisp.org>, Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org,
	Helge Kreutzmann <debian@helgefjell.de>,
	Mario Blaettermann <mario.blaettermann@gmail.com>
Subject: Re: names of ISO 8859 encodings
Date: Fri, 13 Dec 2024 18:56:54 -0600	[thread overview]
Message-ID: <20241214005654.vhpp4c46p7sw4zjr@illithid> (raw)
In-Reply-To: <20241214003716.gnockyne6qh7jpml@devuan>

[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]

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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-12-14  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14  0:23 names of ISO 8859 encodings Bruno Haible
2024-12-14  0:37 ` Alejandro Colomar
2024-12-14  0:56   ` G. Branden Robinson [this message]
2024-12-14  6:12     ` Helge Kreutzmann
2024-12-14 15:47       ` G. Branden Robinson
2024-12-14 17:27         ` Alejandro Colomar
2024-12-14 18:01           ` on the need for better quotation in man(7) (was: names of ISO 8859 encodings) G. Branden Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241214005654.vhpp4c46p7sw4zjr@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --cc=bruno@clisp.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.