unofficial mirror of bug-gnu-emacs@gnu.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: Sun, 11 Jun 2017 19:49:08 -0700 (PDT)	[thread overview]
Message-ID: <2ee7f2fb-2d2e-4c1b-8c0f-4700330d967c@default> (raw)
In-Reply-To: <474e169d-6f2e-440b-b968-22d091e59600@default>


[-- Attachment #1.1: Type: text/plain, Size: 2362 bytes --]

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

 

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

[-- Attachment #1.2: Type: text/html, Size: 7939 bytes --]

[-- Attachment #2: throw-emacs-bug-26299.png --]
[-- Type: image/png, Size: 23055 bytes --]

  reply	other threads:[~2017-06-12  2:49 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
2017-06-12  2:49         ` Drew Adams [this message]
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

  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=2ee7f2fb-2d2e-4c1b-8c0f-4700330d967c@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 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).