From: Xavier Noria via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 73265@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#73265: Spelling of macOS
Date: Sun, 15 Sep 2024 14:05:37 +0200 [thread overview]
Message-ID: <CAM=Ycdh4Kqgb=o5nBo0iEe4qYiGbPKThxdkzt0jyCFqxbBRyxw@mail.gmail.com> (raw)
In-Reply-To: <CAM=YcdgwSYv7p1Xg=oFzZuAwFFMTmAGwMX3aw5JZJBb2h-PBMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Please, disregard my previous email, I misinterpreted the commit reference
as a patch for this one.
On Sun, Sep 15, 2024, 14:02 Xavier Noria <fxn@hashref.com> wrote:
> Fixed!
>
> On Sun, Sep 15, 2024, 13:50 Stefan Kangas <stefankangas@gmail.com> wrote:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Thanks. We don't necessarily follow the Apple's marketing spin, so
>> > I'm not sure we should fix these.
>>
>> We already spell it macOS in our tree, so we might as well do it on the
>> website too, to avoid confusion. Marketing spin or not, I think this
>> spelling is harmless, FWIW.
>>
>> commit dc152c54f4e44f5f2040883b03f71ff6aa66c893
>> Author: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Sun Nov 6 00:33:43 2016 -0700
>>
>> Modernize usage of 'macOS' in doc and comments
>>
>> Apple changed the spelling of its operating system again, to "macOS",
>> effective with macOS 10.12 Sierra (2016-09-20). Change Emacs
>> documentation and comments to match this. Stick with older OS
>> spellings ("OS X", "Mac OS X") when talking about older releases where
>> the older names are more correct.
>>
>
[-- Attachment #2: Type: text/html, Size: 2004 bytes --]
next prev parent reply other threads:[~2024-09-15 12:05 UTC|newest]
Thread overview: 17+ 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-21 10:16 ` Eli Zaretskii
2024-09-21 13:14 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-21 13:28 ` Eli Zaretskii
2024-09-21 13:53 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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 [this message]
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
2024-09-20 4:56 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM=Ycdh4Kqgb=o5nBo0iEe4qYiGbPKThxdkzt0jyCFqxbBRyxw@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=73265@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fxn@hashref.com \
--cc=stefankangas@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).