From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3035@emacsbugs.donarmstrong.com
Subject: bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc.
Date: Mon, 20 Apr 2009 12:24:48 -0400 [thread overview]
Message-ID: <jwvvdozthtu.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <001b01c9c125$c3982a90$0200a8c0@us.oracle.com> (Drew Adams's message of "Sun, 19 Apr 2009 12:33:48 -0700")
>> You're simply wrong. Maybe in the texts you read it's not
>> common practice. But in the texts I read it is.
> Read more. Technical manuals, in particular, since that is the domain in
> question.
> Yes, some do adopt the same appearance (e.g. italics) for defined
> terms as for emphasis (stress). You might argue that there are enough
> that do this that it can be called _a_ common practice, but it is by
> no means _the_ common practice.
What other convention have you seen?
> Red herring. Obviously, such terms need to be made to stand out
> (emphasized). I stated that from the beginning.
Sorry, I had missed that part. I'm glad we agree.
Stefan
next prev parent reply other threads:[~2009-04-20 16:24 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
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 [this message]
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=jwvvdozthtu.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3035@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
/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).