From: "Scot Becker" <scot.becker@gmail.com>
To: Paul R <paul.r.ml@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Footnotes and org-export, revisited
Date: Wed, 17 Dec 2008 15:59:42 +0000 [thread overview]
Message-ID: <e0e1fe620812170759q715cae29u2f38c9fe840a06ea@mail.gmail.com> (raw)
In-Reply-To: <873agmyg4y.fsf@gmail.com>
I'm torn.
Usage 1 is harder to read. My footnotes, for example, are very long
compared to your example. Of course, within emacs, this could be made
much less severe with a little syntax coloring. It has the advantage
that it never gets lost or otherwise mangled without your knowledge,
and you don't have to wonder whether you used 'kenpo' as a reference
already, and just what might be the consequences if you did. It's
only liability is readability.
Usage 2 is easier to read, which is the trend in plain-text markup
these days. Pandoc, Multi-Markdown and ReST all do it this way, which
isn't to say that we should. It is a little more fragile, since I
might move the paragraph and forget its accompanying footnote, and it
leaves the user to come up with an original reference name, which
could get to be burdensome in if you try to write in an academic field
which averages 3-5 footnotes per page (1 per 75 words or so). It's
also more typing work.
Some of the disadvantages of Usage 2 can helped. A fairly simple
footnote composition routine could automate the note entry and return
to the body text, and, for the desperate, could append a few random
characters to the reference for uniqueness.
Its similarity to the other minimal markup languages might lend
itself towards easy export to those. (Pandoc, for example, has
initial support for citeproc a citatation scheme still in development
which aims at being a kind of BibTeX for plain-text markup languages).
A user's preference probably depends on whether they expect to do a
lot of editing within org (where you might bias readability and
therefore the separation of note and body text) or just want a quick
write, either because you don't require a lot of reworking or because
you plan to do it elsewhere, in LaTeX, one of the lightweight
markups, or a (gasp) GUI Word Processor.
Scot
next prev parent reply other threads:[~2008-12-17 15:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 12:52 Footnotes and org-export, revisited Scot Becker
2008-12-17 13:28 ` Paul R
2008-12-17 13:31 ` Carsten Dominik
2008-12-17 15:29 ` Paul R
2008-12-17 15:59 ` Scot Becker [this message]
2008-12-17 20:54 ` Matthew Lundin
2008-12-17 22:23 ` Scot Becker
2008-12-17 16:08 ` Carsten Dominik
2008-12-17 16:32 ` Paul R
2008-12-17 16:58 ` Carsten Dominik
2008-12-17 17:25 ` Paul R
2008-12-17 17:18 ` Sivaram Neelakantan
2008-12-18 8:08 ` Carsten Dominik
2008-12-18 17:13 ` Sivaram Neelakantan
2008-12-18 10:34 ` Peter Frings
2008-12-18 10:55 ` Peter Frings
2008-12-17 14:04 ` Jörg Hagmann
2009-01-01 9:07 ` Carsten Dominik
2009-01-01 16:48 ` Matthew Lundin
2009-01-01 17:10 ` Carsten Dominik
2009-01-02 15:10 ` Matthew Lundin
2009-01-03 8:17 ` Carsten Dominik
2009-01-03 22:53 ` Matthew Lundin
2009-01-04 7:39 ` Carsten Dominik
2009-01-12 11:29 ` Scot Becker
2009-01-12 14:21 ` Paul R
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=e0e1fe620812170759q715cae29u2f38c9fe840a06ea@mail.gmail.com \
--to=scot.becker@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=paul.r.ml@gmail.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/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).