From: Stepan Kasal <kasal@ucw.cz>
Cc: bug-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: Double hyphens in variable names.
Date: Sun, 5 Oct 2003 12:36:12 +0200 [thread overview]
Message-ID: <20031005123612.A17768@math.cas.cz> (raw)
In-Reply-To: <87znggzeqs.fsf@tc-1-100.kawasaki.gol.ne.jp>; from miles@gnu.org on Sun, Oct 05, 2003 at 09:53:47AM +0900
Hello,
> Richard Stallman <rms@gnu.org> writes:
> > One other alternative is to use a fixed width font but slightly
> > smaller than the roman font now used. That might use little or no
> > extra space. It would have a drawback too, in reducing the visibility
> > of the function name, but it still could be better overall than using
> > a fixed width font of the same size.
The current implementation uses bxshape, which is pretty wide. Replacing
cmbx10 by cmtt10 means getting _narrower_ results in average, I guess.
Observe the following excerpt from a .log file:
\bxshape:
> 48.07613pt. l.1 \setbox0\hbox{\bf megabyte} \showthe\wd0
> 39.3956pt. l.2 \setbox0\hbox{\bf variable} \showthe\wd0
\ttshape:
> 41.99963pt. l.3 \setbox0\hbox{\tt megabyte} \showthe\wd0
> 41.99963pt. l.4 \setbox0\hbox{\tt variable} \showthe\wd0
Two more notes:
On Sun, Oct 05, 2003 at 09:53:47AM +0900, Miles Bader wrote:
> Mixing smaller font sizes in this way usually looks quite bad too.
Sure.
current texinfo.tex contains:
| \setfont\defbf\bxshape{10}{\magstep1} %was 1314
| [...]
| \def\setdeffont#1 {\csname DEF#1\endcsname}
I don't know whether we prefer \defbf or \DEFbf (Karl?).
Have a nice day,
Stepan Kasal
next prev parent reply other threads:[~2003-10-05 10:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 1:03 Double hyphens in variable names Karl Berry
2003-10-04 22:35 ` Richard Stallman
2003-10-05 0:53 ` Miles Bader
2003-10-05 10:36 ` Stepan Kasal [this message]
2003-10-05 8:34 ` Werner LEMBERG
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 7:57 David PONCE
2003-10-06 9:26 David PONCE
2003-10-06 9:06 David PONCE
2003-10-06 9:18 ` Lute Kamstra
2003-10-07 5:32 ` Richard Stallman
2003-10-07 6:57 ` Lute Kamstra
2003-10-04 1:03 Karl Berry
2003-10-04 3:51 ` Luc Teirlinck
2003-10-01 13:53 Lute Kamstra
2003-10-02 5:55 ` Eli Zaretskii
2003-10-02 8:43 ` Lute Kamstra
2003-10-02 13:18 ` Luc Teirlinck
2003-10-02 15:11 ` Lute Kamstra
2003-10-02 16:00 ` Luc Teirlinck
2003-10-02 16:14 ` Lute Kamstra
2003-10-02 16:54 ` Andreas Schwab
2003-10-02 17:25 ` Luc Teirlinck
2003-10-03 1:50 ` Luc Teirlinck
2003-10-03 2:13 ` Luc Teirlinck
2003-10-03 3:45 ` Luc Teirlinck
2003-10-02 19:04 ` Oliver Scholz
2003-10-03 8:39 ` Lute Kamstra
2003-10-03 16:18 ` Luc Teirlinck
2003-10-03 19:37 ` Lute Kamstra
2003-10-03 18:33 ` Luc Teirlinck
2003-10-03 18:42 ` Luc Teirlinck
2003-10-03 19:46 ` Lute Kamstra
2003-10-04 10:47 ` David Ponce
2003-10-06 7:11 ` Lute Kamstra
2003-10-06 23:19 ` Juri Linkov
2003-10-07 9:08 ` Lute Kamstra
2003-10-03 19:42 ` Richard Stallman
2003-10-03 21:19 ` Juri Linkov
2003-10-02 14:07 ` Luc Teirlinck
2003-10-02 19:15 ` Richard Stallman
2003-10-02 18:56 ` Kevin Rodgers
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=20031005123612.A17768@math.cas.cz \
--to=kasal@ucw.cz \
--cc=bug-texinfo@gnu.org \
--cc=emacs-devel@gnu.org \
/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).