emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Frontmatter / Text before first headline
Date: Wed, 01 Feb 2012 19:46:42 +0100	[thread overview]
Message-ID: <87y5sms86l.fsf@Rainer.invalid> (raw)
In-Reply-To: 81lion57bd.fsf@gmail.com

Jambunathan K <kjambunathan@gmail.com> writes:
> I have trouble understanding what the real purpose of the "text before
> the first headline" is.

"When I use a word, it means just what I choose it to mean -- neither
more nor less."

-- Humpty Dumpty, "Through the Looking Glass and what Alice found there"

> It looks to me more like a placeholder for
> capturing the "Frontmatter" [1]. 
>
> I have also trouble understanding what the rightful position for it is:
>
> Should it be like:
> (a) Title, Initial Text, TOC, Chapters
> 	Or like
> (b) Title, TOC, Initial Text, Chapters
>
> Currently org-latex does a (b). 
>
> But if I look at an organization of a typical document, I am inclined to
> think that it should be (a). It is also my contention that Table Of
> Contents is relocatable only as a means to achieve (b).

That would depend a lot on the type of document and the publishing
culture it's intended for.  If we're talking books, then things are even
more complicated, as traditionally you'd have a bastard title(*) before
the actual title page.  The back of the actual title page (which would
be page 3 if it were numbered) almost always has some text, most often
the bibliographic entry.

(*) The bastard title is a relict from those times when you bought your
books as folded signatures as they were coming from the printer and you
had to cut and bind the book yourself if you were going to the trouble
and expense.  The title page(s) and front matter would be printed after
the rest of the book had already been off the press on their own
signature (you wouldn't know the page numbers for the TOC otherwise).

> I am wondering if you would be interested in formalizing frontmatter in
> Org documents. Backends will then be obligated to render the front
> matter headings as "centered text".

I'm not sure why you'd insist on "centered".

> - Title Page
> ,---- Frontmatter
> | - Copyright notice
> | - Abstract
> | - Preface
> | - Acknowledgements
> | - Dedication
> | - Table Of Contents
> | - List of Tables, Figures and Illustrations etc

The title page is considered part of the front matter in traditional
printing as it is printed on the same sheet as the rest of the front
matter.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

      parent reply	other threads:[~2012-02-01 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  7:41 Frontmatter / Text before first headline Jambunathan K
2012-02-01 13:43 ` Nicolas Goaziou
2012-02-01 18:46 ` Achim Gratz [this message]

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5sms86l.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@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/org-mode.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).