all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: van@scratch.space, 31614@debbugs.gnu.org
Subject: bug#31614: (texinfo) dfn - the double quotes around ``deleting'' are inconsistent with (eintr) Complications ``variables''
Date: Mon, 28 May 2018 19:17:40 +0300	[thread overview]
Message-ID: <83tvqr7o0r.fsf@gnu.org> (raw)
In-Reply-To: <mvma7sknjbt.fsf@suse.de> (message from Andreas Schwab on Mon, 28 May 2018 12:52:22 +0200)

> From: Andreas Schwab <schwab@suse.de>
> Date: Mon, 28 May 2018 12:52:22 +0200
> Cc: 31614@debbugs.gnu.org
> 
> On Mai 28 2018, Van L <van@scratch.space> wrote:
> 
> >   1. (eintr) Complications ``variables''
> >   2. (texinfo) dfn ''deleting''
> 
> The manuals are created with different makeinfo versions.

Actually, the Texinfo manual is traditionally produced using the same
version of Texinfo as the one described in the manual.  In the case of
the latest version, it's Texinfo 6.5, the latest version.

AFAIK, the cause of the difference in quoting style is that the
Texinfo manual doesn't use any @documentencoding directive, so the
output is plain-ASCII.





  reply	other threads:[~2018-05-28 16:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28  3:56 bug#31614: (texinfo) dfn - the double quotes around ``deleting'' are inconsistent with (eintr) Complications ``variables'' Van L
2018-05-28  8:55 ` Eli Zaretskii
2018-05-28 11:05   ` bug#31614: Off Topic (was: bug#31614) Van L
2018-05-28 11:30     ` bug#31614: Off Topic Noam Postavsky
2018-05-28 13:04       ` Van L
2018-05-28 15:18       ` Eli Zaretskii
2018-05-28 15:37         ` Noam Postavsky
2018-05-28 15:15     ` bug#31614: Off Topic (was: bug#31614) Eli Zaretskii
2018-05-28 10:52 ` bug#31614: (texinfo) dfn - the double quotes around ``deleting'' are inconsistent with (eintr) Complications ``variables'' Andreas Schwab
2018-05-28 16:17   ` Eli Zaretskii [this message]
2022-02-07 10:06     ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83tvqr7o0r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31614@debbugs.gnu.org \
    --cc=schwab@suse.de \
    --cc=van@scratch.space \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.