GNU bug report logs -
#26299
24.5; Use of `…' in Info
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Wed, 29 Mar 2017 14:45:01 UTC
Severity: wishlist
Tags: notabug
Found in version 24.5
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
> > > 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 <at> 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.
Dunno whether you want a separate bug report for this, but here
is a related problem that is even worse, IMO: The character
RIGHTWARDS ARROW FROM BAR (#x421) is no good in Info, at least
in some fonts. It is too narrow. Previously Emacs used `==>'
instead of that char. See attached screenshot, where the font
is (for some reason):
-outline-MS Gothic-normal-normal-normal-mono-14-*-*-*-c-*-jisx0208*-*
The font for the rest of the chars in that screenshot is:
-outline-Lucida Console-normal-normal-normal-mono-14-*-*-*-c-*-iso8859-1.
Don't ask me why Emacs uses that font for that char - I have no
idea. (And yes, to Eli's typical response to questions about
fonts for odd chars, I do have Symbola installed. But Emacs
doesn't seem to use it, here.)
[Message part 2 (text/html, inline)]
[throw-emacs-bug-26299.png (image/png, attachment)]
This bug report was last modified 5 years and 243 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.