unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Gregory Heytings <gregory@heytings.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 58150@debbugs.gnu.org
Subject: bug#58150: 29.0.50; parse_tool_bar_item should not usually upcase "and"
Date: Thu, 29 Sep 2022 16:09:37 -0700	[thread overview]
Message-ID: <87k05llqvi.fsf@melete.silentflame.com> (raw)
In-Reply-To: <9f70d95aac6cec78b167@heytings.org> (Gregory Heytings's message of "Thu, 29 Sep 2022 23:00:56 +0000")

Hello,

On Thu 29 Sep 2022 at 11:00PM GMT, Gregory Heytings wrote:

>>> Otherwise somebody could, of course, just write a function that capitalises
>>> titles correctly according to one or other of the English title
>>> capitalisation standards -- which isn't difficult, and would be generally
>>> useful.
>>
>> I'm not sure it's so simple, actually, and I think your first suggestion is
>> preferable.  For example, "Go To Node" in the Info toolbar is probably
>> correct, because it's a whole phrasal verb, but in other contexts, "to" in
>> titles isn't capitalised.
>>
>
> Indeed, it's not easy, and can probably not be mechanized, because whether a
> word should be capitalized or not may depend on its semantics.  The CMOS gives
> the following rules (I removed some parts that are not important in the
> context of Emacs):

The way they are written, they're more like guidelines, not rules, which
only proves the point, I suppose.  Thanks for sharing these.

-- 
Sean Whitton





      reply	other threads:[~2022-09-29 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 20:02 bug#58150: 29.0.50; parse_tool_bar_item should not usually upcase "and" Sean Whitton
2022-09-28 20:38 ` Sean Whitton
2022-09-29 11:02   ` Lars Ingebrigtsen
2022-09-29 12:58     ` Eli Zaretskii
2022-09-30 12:34       ` Lars Ingebrigtsen
2022-09-29 22:43     ` Sean Whitton
2022-09-29 23:00       ` Gregory Heytings
2022-09-29 23:09         ` Sean Whitton [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

  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=87k05llqvi.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=58150@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.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 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).