From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#3035: 23.0.92; doc, terminology for graphics, display, terminal, etc. Date: Sat, 18 Apr 2009 20:20:27 +0300 Message-ID: <83fxg5j2uc.fsf@gnu.org> References: <001201c9bf7c$14221e40$0200a8c0@us.oracle.com> <83tz4mig8z.fsf@gnu.org> <002301c9bffa$93ba5040$0200a8c0@us.oracle.com> <83myaei6h4.fsf@gnu.org> <003301c9c041$f6ff1810$0200a8c0@us.oracle.com> Reply-To: Eli Zaretskii , 3035@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1240077348 6135 80.91.229.12 (18 Apr 2009 17:55:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Apr 2009 17:55:48 +0000 (UTC) Cc: 3035@emacsbugs.donarmstrong.com To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Apr 18 19:57:07 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LvEmg-00048q-4x for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Apr 2009 19:56:58 +0200 Original-Received: from localhost ([127.0.0.1]:53275 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvElF-0000j7-Te for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Apr 2009 13:55:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LvElA-0000io-Cf for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2009 13:55:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LvEl5-0000i2-8N for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2009 13:55:23 -0400 Original-Received: from [199.232.76.173] (port=40144 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvEl5-0000hz-40 for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2009 13:55:19 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:52544) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LvEl3-0001pg-Po for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2009 13:55:18 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n3IHhp8g007349; Sat, 18 Apr 2009 10:43:52 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id n3IHP4p4002050; Sat, 18 Apr 2009 10:25:04 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: Eli Zaretskii Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Sat, 18 Apr 2009 17:25:04 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 3035 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 3035-submit@emacsbugs.donarmstrong.com id=B3035.12400752401599 (code B ref 3035); Sat, 18 Apr 2009 17:25:04 +0000 Original-Received: (at 3035) by emacsbugs.donarmstrong.com; 18 Apr 2009 17:20:40 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from mtaout5.012.net.il (mtaout5.012.net.il [84.95.2.13]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n3IHKZ7a001583 for <3035@emacsbugs.donarmstrong.com>; Sat, 18 Apr 2009 10:20:37 -0700 Original-Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KIB009003Z1PL00@i_mtaout5.012.net.il> for 3035@emacsbugs.donarmstrong.com; Sat, 18 Apr 2009 20:20:29 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.124.144.191]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KIB00FAD460RZD0@i_mtaout5.012.net.il>; Sat, 18 Apr 2009 20:20:25 +0300 (IDT) In-reply-to: <003301c9c041$f6ff1810$0200a8c0@us.oracle.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Resent-Date: Sat, 18 Apr 2009 13:55:23 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:27327 Archived-At: > From: "Drew Adams" > Cc: <3035@emacsbugs.donarmstrong.com> > Date: Sat, 18 Apr 2009 09:23:09 -0700 > > > > > > 2. In the Elisp manual, I see the use of terms such as > > > > > "graphical terminal", "graphicical display" (also > > > > > "graphics display"), "(non-)graphics-capable display", > > > > > "text terminals" (opposed to graphical), "graphic > > > > > characters", and "graphical attributes", without any > > > > > real explanation or definition. > > > > > > > > From the node "Frames", near the beginning:... > > > > If this is not good enough, please tell what is missing. > > > > > > Yes, that helps wrt "graphical terminal" and "text > > > terminal" (but not with the rest). > > > > But that's what your Item 2 (above) was all about: the distinction > > between text and graphical terminals. What else is needed? > > Yes and no. Yes for these: "graphical display", "graphics display", and > "graphics-capable display", if one understands that they are synonymous. They are synonymous. > Likewise, for "text terminals" and "non-graphical-capable displays". Also synonyms. > It's also not clear to me how "graphic characters" and "graphical attributes" > fit in with the others. For instance, are they implied by "graphical display"? > Does any of them alone imply "graphical display"? What does each of them mean? "graphic characters" have nothing to do with displays or terminals. They are named "graphic" because they match the [:graph:] regexp. The only place I found "graphical attributes" is in the context of face attributes. Since faces are supported on text terminals as well, these also don't have any direct relation to GUI vs TTY displays. > Dunno if things like italics and bold fonts are feasible in the Info context, > for stuff like this. Someone needs to write code to display _foo_ in italics and *foo* in bold in Info buffers. > you might also consider using bold instead of quoting, for defined > terms (another item we discussed). That is a convention often used > in technical doc. 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. > Maybe a glossary in Elisp would be helpful too? Probably.