From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: terminal escapes in Info files? Date: Thu, 30 Oct 2003 02:37:33 +0000 (UTC) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200310281746.h9SHk2915693@f7.net> <200310292002.h9TK2kc23440@raven.dms.auburn.edu> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1067483303 8586 80.91.224.253 (30 Oct 2003 03:08:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 30 Oct 2003 03:08:23 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Oct 30 04:08:21 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AF3Ab-0008R3-00 for ; Thu, 30 Oct 2003 04:08:21 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AF3Aa-00079b-00 for ; Thu, 30 Oct 2003 04:08:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AF2zC-0008Ae-6G for emacs-devel@quimby.gnus.org; Wed, 29 Oct 2003 21:56:34 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AF2hS-0001Qk-PE for emacs-devel@gnu.org; Wed, 29 Oct 2003 21:38:14 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AF2gr-0000zT-OE for emacs-devel@gnu.org; Wed, 29 Oct 2003 21:38:08 -0500 Original-Received: from [140.186.114.245] (helo=rattlesnake.com) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AF2gq-0000xf-0b for emacs-devel@gnu.org; Wed, 29 Oct 2003 21:37:36 -0500 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.115) Thu, 30 Oct 2003 02:37:33 +0000 (UTC) Original-To: emacs-devel@gnu.org In-reply-to: (message from Oliver Scholz on Wed, 29 Oct 2003 21:47:03 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17600 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17600 ... (Don't you say “HTML page” in English, too?) Yes, but English speaks do not mean the same when when referring to a printed page and an HTML page. The use of the term in HTML is a metaphorical extension of the concept of `printed page'. I mean the current info format's  I think you meant `node', which if it were printed may print out as more or less than one printed page. A node is also sometimes called a `section'. But in Texinfo documents, sections often consist of several nodes, and then of course, there is the `@section' command. The language is confusing. Which is the the English word you use for the structural equivalent of a printed's output page, i.e. the electronic text that is rendered on an application's screen canvas at a certain time? The `display' or `buffer' or `window'. The amount displayed varies depending on how many lines your window is showing. For example, right now my display is showing 48 lines for this *mail* buffer, but just a few moments ago, I divided this frame into two and my display was showing only 24 lines for this buffer. In HTML, the word that corresponds to a `node' or `section' is a `page'. It is what you get when you fetch a URL. Put another way, a URL points to a page. Thus, `http://www.teak.cc' points the the default page indicated by the URL, which is the `index.html' page. An HTML page may print out as more or less than one printed page. Often, an HTML page is larger than the amount that is displayed by a Web browser at any one time. I have read people using the word `document' to mean one page of an HTML document. By this usage, the W3 mode manual splits into 129 different documents when created as HTML using the default. I find this language confusing, since in fact, the W3 mode manual is a single manual, one `document'. The `(texinfo)HTML Splitting' node in Info says, By default, `makeinfo' splits HTML output into one output file per Texinfo source node. which is much clearer. (The `--no-split' option produces one HTML page from one Texinfo source file.) All in all the language is confusing, and not everyone uses it the same way. -- Robert J. Chassell Rattlesnake Enterprises http://www.rattlesnake.com GnuPG Key ID: 004B4AC8 http://www.teak.cc bob@rattlesnake.com