From: Stefan Kangas <stefankangas@gmail.com>
To: rms@gnu.org, Xavier Noria <fxn@hashref.com>
Cc: 73265@debbugs.gnu.org, eliz@gnu.org
Subject: bug#73265: Spelling of macOS
Date: Wed, 18 Sep 2024 16:11:02 -0700 [thread overview]
Message-ID: <CADwFkmnsp+_kD7fjGgv13VS_-teCG10vOZkV36Xipb6NKOcy=A@mail.gmail.com> (raw)
In-Reply-To: <E1sqlkm-00066n-1N@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> The only proposed reason to write "macOS" is that Apple asks for it.
The main reason is actually because the old way of writing it is
"Mac OS" (1984-2000) or "Mac OS X"/"OS X" (2000-2016) and writing it
like that suggests that we only support those older versions. It opens
the door to an easily avoided confusion. We also have no real reason
not to use the official spelling; it's completely harmless.
I don't intend to man the barricades, but I do think that we should just
use the official spelling and be done with this.
prev parent reply other threads:[~2024-09-18 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 7:11 bug#73265: Spelling of macOS Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 7:55 ` Eli Zaretskii
2024-09-15 8:04 ` Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 8:43 ` Eli Zaretskii
2024-09-15 8:49 ` Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 9:02 ` Eli Zaretskii
2024-09-15 11:50 ` Stefan Kangas
2024-09-15 12:02 ` Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 12:05 ` Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-18 3:53 ` Richard Stallman
2024-09-18 4:09 ` Xavier Noria via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-18 23:11 ` Stefan Kangas [this message]
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='CADwFkmnsp+_kD7fjGgv13VS_-teCG10vOZkV36Xipb6NKOcy=A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=73265@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fxn@hashref.com \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.