unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: terminal escapes in Info files?
Date: Thu, 30 Oct 2003 02:37:33 +0000 (UTC)	[thread overview]
Message-ID: <m1AF2gn-000UNaC@rattlesnake.com> (raw)
In-Reply-To: <ur80vwz3s.fsf@ID-87814.user.dfncis.de> (message from Oliver Scholz on Wed, 29 Oct 2003 21:47:03 +0100)

   ... (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 \x1f

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

  parent reply	other threads:[~2003-10-30  2:37 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 17:46 terminal escapes in Info files? Karl Berry
2003-10-28 18:08 ` Stefan Monnier
2003-10-29 12:20   ` Oliver Scholz
2003-10-29 14:21     ` Eli Zaretskii
2003-10-29 16:24       ` Oliver Scholz
2003-10-29 17:29         ` Robert J. Chassell
2003-10-29 18:09           ` Stefan Monnier
2003-10-30  1:13             ` Robert J. Chassell
2003-10-30  6:10               ` Stephen J. Turnbull
2003-10-30 22:06                 ` Robert J. Chassell
2003-11-03 12:19                   ` Stephen J. Turnbull
2003-10-30 16:36               ` Stefan Monnier
2003-10-29 18:40           ` Oliver Scholz
2003-10-29 19:09             ` Oliver Scholz
2003-10-29 20:02               ` Luc Teirlinck
2003-10-29 20:47                 ` Oliver Scholz
2003-10-29 22:58                   ` Luc Teirlinck
2003-10-30  2:37                   ` Robert J. Chassell [this message]
2003-10-30  2:55                   ` Robert J. Chassell
2003-10-29 17:45         ` Eli Zaretskii
2003-10-29 18:00         ` Reiner Steib
2003-10-29 18:43           ` Oliver Scholz
2003-10-30  4:19     ` Richard Stallman
2003-10-30  6:11       ` Eli Zaretskii
2003-10-31  0:07         ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 20:09 Karl Berry
2003-10-29 12:52 ` Oliver Scholz
2003-10-29 14:14   ` Eli Zaretskii
2003-10-29 14:31     ` Andreas Schwab
2003-10-29 17:51       ` Alper Ersoy
2003-10-29 18:53         ` Alper Ersoy
2003-10-29 18:11       ` Eli Zaretskii
2003-10-29 21:08         ` Andreas Schwab
2003-10-29 21:18           ` Alper Ersoy
2003-10-29 21:40           ` Eli Zaretskii
2003-10-29 15:28     ` Oliver Scholz
2003-10-31  2:29     ` Thien-Thi Nguyen
2003-10-29 19:02 ` Richard Stallman
2003-10-28 20:06 Karl Berry
2003-10-28 20:06 Karl Berry
2003-10-28 21:23 ` Stefan Monnier
2003-10-28 23:41 ` Miles Bader
2003-10-28 16:51 Karl Berry
2003-10-28 16:59 ` Stefan Monnier
2003-10-28 17:16   ` Eli Zaretskii
2003-10-28 17:56     ` Stefan Monnier
2003-10-28 20:34       ` Eli Zaretskii
2003-10-28 16:50 Karl Berry
2003-10-28  1:26 Karl Berry
2003-10-28 10:51 ` Alper Ersoy
2003-10-28 13:48   ` Oliver Scholz
2003-10-30 10:42     ` Alper Ersoy
2003-10-28 16:19   ` Stefan Monnier
2003-10-29 19:02     ` Richard Stallman
2003-10-29 19:47       ` David Kastrup
2003-10-29 21:43         ` Eli Zaretskii
2003-10-29 22:39           ` David Kastrup
2003-10-30  6:03             ` Eli Zaretskii
2003-10-30 18:00         ` Richard Stallman
2003-10-29 19:01   ` Richard Stallman
2003-10-29 19:45     ` Alper Ersoy
2003-10-29 19:42       ` Eli Zaretskii
2003-10-30 18:00       ` Richard Stallman
2003-10-29 19:02 ` Richard Stallman
2003-10-26 12:20 Karl Berry
2003-10-26 12:40 ` Simon Josefsson
2003-10-26 15:40   ` Alex Schroeder
2003-10-27  7:02 ` Richard Stallman
2003-10-27 19:29   ` Eli Zaretskii

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=m1AF2gn-000UNaC@rattlesnake.com \
    --to=bob@rattlesnake.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).