unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: 44211@debbugs.gnu.org
Subject: bug#44211: 26.3; Repeated `` and '' in Info (eintr)`GNU Free Documentation License'
Date: Sun, 25 Oct 2020 13:11:03 -0700 (PDT)	[thread overview]
Message-ID: <6a4718dd-5a49-4d3d-bb1f-bdb4ba37206e@default> (raw)
In-Reply-To: <<83k0vef5j9.fsf@gnu.org>>

> > 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.









       reply	other threads:[~2020-10-25 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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     ` Drew Adams [this message]
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

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=6a4718dd-5a49-4d3d-bb1f-bdb4ba37206e@default \
    --to=drew.adams@oracle.com \
    --cc=44211@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefankangas@gmail.com \
    /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).