From: Asher Gordon <AsDaGo@posteo.net>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: Remove license modules
Date: Sun, 17 May 2020 16:12:29 -0400 [thread overview]
Message-ID: <87eeriqq1e.fsf@posteo.net> (raw)
In-Reply-To: <87lflqqqo1.fsf@posteo.net> (Asher Gordon's message of "Sun, 17 May 2020 15:58:54 -0400")
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Asher Gordon <AsDaGo@posteo.net> writes:
> Perhaps Texinfo should change its heuristics so that a '.' preceding a
> capital letter always starts a sentence, even when it is preceded by a
> capital letter.
I just realized that this would treat names such as "J. Random Hacker"
incorrectly. That would then have to be written as "J.@ Random
Hacker". I still think that the new heuristics I described would do the
right thing more often, but perhaps it shouldn't be changed, since many
manuals have names in that format.
So I decided not to proposed the change to the Texinfo maintainers after
all.
Asher
--
<knghtbrd> eek, not another one...
<knghtbrd> Seems ever developer and their mother now has a random
signature using irc quotes ...
<knghtbrd> WHAT HAVE I STARTED HERE??
GPG fingerprint: 38F3 975C D173 4037 B397 8095 D4C9 C4FC 5460 8E68
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-17 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:51 Remove license modules Asher Gordon
2020-05-15 23:17 ` Bruno Haible
2020-05-16 18:03 ` Asher Gordon
2020-05-17 17:39 ` Bruno Haible
2020-05-17 19:58 ` Asher Gordon
2020-05-17 20:12 ` Asher Gordon [this message]
2020-06-01 18:00 ` Bruno Haible
2020-06-01 18:09 ` Paul Eggert
2020-06-01 19:06 ` Typographical errors in Texinfo format licenses Asher Gordon
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeriqq1e.fsf@posteo.net \
--to=asdago@posteo.net \
--cc=bruno@clisp.org \
--cc=bug-gnulib@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.
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).