From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: "44211@debbugs.gnu.org" <44211@debbugs.gnu.org>
Subject: bug#44211: [External] : Re: bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License'
Date: Fri, 12 Mar 2021 15:41:55 +0000 [thread overview]
Message-ID: <SA2PR10MB44740FA7C9F022F10B6D45E2F36F9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83o8folrx2.fsf@gnu.org>
> . more importantly, the text in the Info file uses “..” quoting
>
> So I now tend to think that Drew was looking at an old version of Info
> manuals, which were produced by makeinfo before we started using UTF-8
> encoding as the default output encoding of our manuals, and that is
> the reason for the original issue.
>
> If I'm right, the bug should be closed as being fixed long ago.
I just checked, with emacs -Q, in 27.1.
Go to node GNU Free Documentation License.
Scroll to the bottom of the node, or search
for Addendum.
The indented block of text after "just after
the title page" has this as its last sentence:
A copy of the license is included in the section
entitled ``GNU Free Documentation License''.
As that block is a quotation, perhaps this is
intended and needed, which is why I said in the
bug report that I don't know whether there's a
bug here.
next prev parent reply other threads:[~2021-03-12 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 14:41 bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' Drew Adams
2020-10-25 18:53 ` Stefan Kangas
2020-10-25 19:51 ` Eli Zaretskii
2021-03-12 1:07 ` Stefan Kangas
2021-03-12 8:03 ` Eli Zaretskii
2021-03-12 15:41 ` Drew Adams [this message]
2021-03-12 16:12 ` bug#44211: [External] : " Eli Zaretskii
2021-03-12 19:18 ` Stefan Kangas
2021-03-12 19:53 ` Drew Adams
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=SA2PR10MB44740FA7C9F022F10B6D45E2F36F9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=44211@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).