From: Gregory Heytings <gregory@heytings.org>
To: Sean Whitton <spwhitton@spwhitton.name>
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 23:00:56 +0000 [thread overview]
Message-ID: <9f70d95aac6cec78b167@heytings.org> (raw)
In-Reply-To: <87y1u1ls37.fsf@melete.silentflame.com>
>> 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):
1. Capitalize the first and last words in titles and subtitles, and
capitalize all other major words (nouns, pronouns, verbs, adjectives,
adverbs, and some conjunctions---but see rule 4) .
2. Lowercase the articles _the_, _a_, and _an_.
3. Lowercase prepositions, regardless of length, except when they are used
adverbially or adjectivally (_up_ in _Look Up_, _down_ in _Turn Down_,
_on_ in _The On Button_, _to_ in _Come To_, etc.).
4. Lowercase the common coordinating conjunctions _and_, _but_, _for_,
_or_, and _nor_.
5. Lowercase _to_ not only as a preposition (rule 3) but also as part of
an infinitive (_to Run_, _to Hide_, etc.), and lowercase _as_ in any
grammatical function.
next prev parent reply other threads:[~2022-09-29 23:00 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 [this message]
2022-09-29 23:09 ` Sean Whitton
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=9f70d95aac6cec78b167@heytings.org \
--to=gregory@heytings.org \
--cc=58150@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=spwhitton@spwhitton.name \
/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).