* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' [not found] ` <<83k0vef5j9.fsf@gnu.org> @ 2020-10-25 20:11 ` Drew Adams 0 siblings, 0 replies; 6+ messages in thread From: Drew Adams @ 2020-10-25 20:11 UTC (permalink / raw) To: Eli Zaretskii, Stefan Kangas; +Cc: 44211 > > But the markup seems correct. Is this a bug in makeinfo perhaps? > > It is not a bug. That's what @example does. OK, not a bug. Does that mean that this is what we want users to see, as the final rendering of this particular text? If so, I wonder what the reason for that is. Here's an occurrence of ``...'' that I think is understandable, in (emacs) `Inserting Text': In addition, in some contexts, if you type a quotation using grave accent and apostrophe '`like this'', it is converted to a form 'like this' using single quotation marks, even without 'C-x 8' commands. Similarly, typing a quotation '``like this''' using double grave accent and apostrophe converts it to a form "like this" using double quotation marks. *Note Quotation Marks::. And this one, in (emacs) `Org Authoring': #+begin_quote ``This is a quote.'' #+end_quote And this, in (emacs) `TeX Editing': In TeX, the character '"' is not normally used; instead, quotations begin with '``' and end with ''''. TeX mode therefore binds the '"' key to the 'tex-insert-quote' command. This inserts '``' after whitespace or an open brace, '"' after a backslash, and '''' after any other character. As a special exception, if you type '"' when the text before point is either '``' or '''', Emacs replaces that preceding text with a single '"' character. You can therefore type '""' to insert '"', should you ever need to do so. (You can also use 'C-q "' to insert this character.) But I don't understand the reported case, unless "in a document" means only some particular kind of source document that will be handled in a way that transforms ``...'' into something else. ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' @ 2020-10-25 14:41 Drew Adams 2020-10-25 18:53 ` Stefan Kangas 0 siblings, 1 reply; 6+ messages in thread From: Drew Adams @ 2020-10-25 14:41 UTC (permalink / raw) To: 44211 Dunno whether this is actually a bug, but it seems odd. In this node you find this text: Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''. Should the `` and '' perhaps be rendered differently - perhaps as curly double quotes? In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32) of 2019-08-29 Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd Windowing system distributor `Microsoft Corp.', version 10.0.18362 Configured using: `configure --without-dbus --host=x86_64-w64-mingw32 --without-compress-install 'CFLAGS=-O2 -static -g3'' ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' 2020-10-25 14:41 Drew Adams @ 2020-10-25 18:53 ` Stefan Kangas 2020-10-25 19:51 ` Eli Zaretskii 0 siblings, 1 reply; 6+ messages in thread From: Stefan Kangas @ 2020-10-25 18:53 UTC (permalink / raw) To: Drew Adams, 44211 Drew Adams <drew.adams@oracle.com> writes: > Dunno whether this is actually a bug, but it seems odd. > > In this node you find this text: > > Texts. A copy of the license is included in the section entitled ``GNU > Free Documentation License''. > > Should the `` and '' perhaps be rendered differently - perhaps as curly > double quotes? Agreed, they should probably be marked as the other instances of ``text quoted like this''. But the markup seems correct. Is this a bug in makeinfo perhaps? ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' 2020-10-25 18:53 ` Stefan Kangas @ 2020-10-25 19:51 ` Eli Zaretskii 2021-03-12 1:07 ` Stefan Kangas 0 siblings, 1 reply; 6+ messages in thread From: Eli Zaretskii @ 2020-10-25 19:51 UTC (permalink / raw) To: Stefan Kangas; +Cc: 44211 > From: Stefan Kangas <stefankangas@gmail.com> > Date: Sun, 25 Oct 2020 11:53:02 -0700 > > But the markup seems correct. Is this a bug in makeinfo perhaps? It is not a bug. That's what @example does. ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' 2020-10-25 19:51 ` Eli Zaretskii @ 2021-03-12 1:07 ` Stefan Kangas 2021-03-12 8:03 ` Eli Zaretskii 0 siblings, 1 reply; 6+ messages in thread From: Stefan Kangas @ 2021-03-12 1:07 UTC (permalink / raw) To: Eli Zaretskii; +Cc: 44211 Stefan Kangas <stefankangas@gmail.com> writes: > Drew Adams <drew.adams@oracle.com> writes: > >> Dunno whether this is actually a bug, but it seems odd. >> >> In this node you find this text: >> >> Texts. A copy of the license is included in the section entitled ``GNU >> Free Documentation License''. >> >> Should the `` and '' perhaps be rendered differently - perhaps as curly >> double quotes? > > Agreed, they should probably be marked as the other instances of ``text > quoted like this''. > > But the markup seems correct. Is this a bug in makeinfo perhaps? Eli Zaretskii <eliz@gnu.org> writes: > It is not a bug. That's what @example does. So should we replace this with “ and ” or should we close this as wontfix? ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' 2021-03-12 1:07 ` Stefan Kangas @ 2021-03-12 8:03 ` Eli Zaretskii 0 siblings, 0 replies; 6+ messages in thread From: Eli Zaretskii @ 2021-03-12 8:03 UTC (permalink / raw) To: Stefan Kangas; +Cc: 44211 > From: Stefan Kangas <stefan@marxist.se> > Date: Thu, 11 Mar 2021 19:07:28 -0600 > Cc: 44211@debbugs.gnu.org, drew.adams@oracle.com > > > But the markup seems correct. Is this a bug in makeinfo perhaps? > > Eli Zaretskii <eliz@gnu.org> writes: > > > It is not a bug. That's what @example does. > > So should we replace this with “ and ” or should we close this as > wontfix? This is a legal blurb we have in all our manuals, so the format there should be identical and coordinated with the FSF. But wait a minute: I don't think I understand the bug report anymore, because of 2 reasons: . the Texinfo source uses @quotation, not @example, so I'm unsure why I mentioned @example in my response, likely a mistake on my part; . 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-03-12 8:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <<76db0515-b5b0-4c7a-91d6-5c11b03696f2@default>
[not found] ` <<CADwFkmmLw+t=J_28kW5MnWL8U33YgaLHrdTcF7Waz2TkO3GyBw@mail.gmail.com>
[not found] ` <<83k0vef5j9.fsf@gnu.org>
2020-10-25 20:11 ` bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License' Drew Adams
2020-10-25 14:41 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
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).