From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 3035@emacsbugs.donarmstrong.com
Subject: bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc.
Date: Sat, 18 Apr 2009 14:18:04 -0700 [thread overview]
Message-ID: <000201c9c06b$2a134770$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <83eivpiswn.fsf@gnu.org>
> > > I don't think it's a good idea to show bold in Info when
> > > it comes out as slanted in print. And making this change
> > > in the printed output as well would be unwise, IMO, as
> > > this is a very old and well-known convention of Texinfo.
> >
> > I see. But you said the same thing about emphasis (_foo_).
> > If both "some quotation" and _something emphasized_ appear
> > as slanted text in print, then how
> > does a reader distinguish these uses?
>
> I think the reader cannot distinguish, indeed, by the typeface alone.
> But @emph is really very rarely used, unlike @dfn; and then, there's
> context. So in practice the problem is not very big one, I think. At
> least I myself never had problems.
OK.
IMO, using slant for a defined term in print is not too good, and having the
same appearance for defined terms and emphasized text (unrelated) is also not
too good. I'm a bit surprised, frankly, given the fine-grained print
representation of things like keys - by contrast, this seems rather coarse. But
if this is the long-established Texinfo convention, so be it.
Here are some possibilities for defined terms in Info - that is, terms that are
defined in place (whether or not they are also listed in a separate glossary). I
assume that both "..." and _..._ will continue to be slant in print. And I
assume emphasis in Info will continue to be shown using italics.
* italics
* bold
* underlining (not underscore wrappers)
* some other face (e.g. color)
next prev parent reply other threads:[~2009-04-18 21:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 16:46 bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc Drew Adams
2009-04-18 7:16 ` Eli Zaretskii
2009-04-18 7:52 ` Drew Adams
2009-04-18 10:47 ` Eli Zaretskii
2009-04-18 16:23 ` Drew Adams
2009-04-18 17:20 ` Eli Zaretskii
2009-04-18 17:29 ` Drew Adams
2009-04-18 20:55 ` Eli Zaretskii
2009-04-18 21:18 ` Drew Adams [this message]
2009-04-19 3:17 ` Stefan Monnier
2009-04-19 5:01 ` Drew Adams
2009-04-19 18:09 ` Stefan Monnier
2009-04-19 19:33 ` Drew Adams
2009-04-20 16:24 ` Stefan Monnier
2011-07-11 14:29 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2009-04-18 1:50 Chong Yidong
2009-04-18 2:03 ` Drew Adams
2009-04-18 6:26 ` Eli Zaretskii
2009-04-18 7:17 ` Drew Adams
2009-04-18 10:39 ` Eli Zaretskii
2009-04-18 16:23 ` Drew Adams
2009-04-18 13:41 ` Chong Yidong
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='000201c9c06b$2a134770$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=3035@emacsbugs.donarmstrong.com \
--cc=eliz@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).