all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 26299@debbugs.gnu.org
Subject: bug#26299: 24.5; Use of `…' in Info
Date: Thu, 30 Mar 2017 07:56:18 -0700 (PDT)	[thread overview]
Message-ID: <474e169d-6f2e-440b-b968-22d091e59600@default> (raw)
In-Reply-To: <CAM-tV-9yz5GSYeVd+_ZR=ZXCkLjcnW=LaG4SrFwPdvNSc3SSeg@mail.gmail.com>

> > Maybe Emacs needs to work around the problem (if it can't be
> > fixed).  Maybe if Emacs uses `. . .' instead of `...' that
> > will stop Texinfo from messing with it.
> >
> > (Why would Texinfo have a blanket treatment of ... as …?
> > That makes no sense at all.  What if the occurrence of ...
> > is part of code, and NEEDS to be 3 period chars?)
> 
> Emacs' .texi files use @dots{} in these cases, as (strongly)
> recommended by the texinfo manual:
> 
>     An ellipsis (a sequence of dots) would be spaced wrong when typeset as
>     a string of periods, so a special command is used in Texinfo: use the
>     @dots{} command to generate a normal ellipsis, which is three dots in
>     a row, appropriately spaced … like so. To emphasize: do not simply
>     write three periods in the input file; that would work for the Info
>     file output, but would produce the wrong amount of space between the
>     periods in the printed manual.
> 
> I found this thread [1] requesting plain "..." for @dots{} in makeinfo
> output; there seemed to be no opposition, but I guess it didn't
> happen. Perhaps try pinging bug-texinfo@gnu.org?

Thanks for checking on this, Noam.  I will leave it to Emacs
maintainers to decide whether to ping bug-texinfo.  I reported
the complaint as one Emacs user.  Dunno what Emacs Dev will
decide is the desired behavior.  I know what I prefer.





  reply	other threads:[~2017-03-30 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 14:44 bug#26299: 24.5; Use of `…' in Info Drew Adams
2017-03-30  3:40 ` npostavs
2017-03-30 13:49   ` Drew Adams
2017-03-30 14:34     ` Noam Postavsky
2017-03-30 14:56       ` Drew Adams [this message]
2017-06-12  2:49         ` Drew Adams
2017-06-12 14:24           ` Eli Zaretskii
2017-06-12 14:52             ` Drew Adams
2017-06-12 15:09               ` Eli Zaretskii
2017-06-12 15:18                 ` Drew Adams
2017-06-12 16:56                   ` Eli Zaretskii
2017-06-12 17:13                     ` Drew Adams
2019-09-29  3:21 ` Stefan Kangas

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=474e169d-6f2e-440b-b968-22d091e59600@default \
    --to=drew.adams@oracle.com \
    --cc=26299@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.