emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Rogers <davidandrewrogers@gmail.com>
To: Alan L Tyree <alantyree@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Index of cases
Date: Sat, 07 Sep 2013 19:05:52 -0700	[thread overview]
Message-ID: <87hadwqd8f.fsf@gmail.com> (raw)
In-Reply-To: <522BB194.7060705@gmail.com> (Alan L. Tyree's message of "Sun, 08 Sep 2013 09:07:00 +1000")

Alan L Tyree <alantyree@gmail.com> writes:

> G'day,
> I am the author of a legal text of about 700 pages. I currently have
> the book in LaTeX using the memoir class. A couple of macros define
> special indexes for a Table of Cases and a Table of Statutes. I would
> like to move the whole thing to Org to make it easier for my editors
> who can be easily alarmed by the LaTeX markup.
> The LaTeX is overkill since I submit the manuscript to the publisher in a Word file.
> Is there a standard way to get, say, the table of cases? A typical "case" looks like this:
>     Howell v Coupland (1874) LR 9 QB 462; (1876) 1 QBD 258
> The Table of Cases needs to indicate where in the text the case is mentioned; reference to section numbers is OK. So, for example, in the Table of Cases, the above case appears as:
>     Howell v Coupland (1874) LR 9 QB 462; (1876) 1 QBD 258  [15.16] [15.25]
> Presuming there is not a "standard", I have considered the following procedure:
>     - maintain a list of cases as I write; I already do this to ensure consistent citation of cases;
>     - use links from the list of cases back into the manuscript to index the places where each case is mentioned in the text.
> Does this seem like a reasonable approach, or is there some obviously better way? I am an extreme novice at elisp but can handle some simple jobs.

In one sense it would be "nicer" and more writer-friendly if the links
went the other direction; that is, when you refer to a case within the
manuscript, you would always tag it in a way that allows it to be
automatically labelled with the section in which it occurs, and
automatically placed into the index of cases for you. That's a
work-saving ideal that I don't actually know how to achieve. (Further
idealistic ramblings: if for example you were to add a new section
between current sections 6 and 7, it would be nice for the labels in
sections 7 through the end to update themselves "wholesale" without your
needing to change each label individually.)

David R

  reply	other threads:[~2013-09-08  2:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 23:07 Index of cases Alan L Tyree
2013-09-08  2:05 ` David Rogers [this message]
2013-09-08  5:56   ` Alan L Tyree
2013-09-08  4:37 ` Jambunathan K
2013-09-08  6:18   ` Alan L Tyree
2013-09-08  7:09     ` Jambunathan K
2013-09-08  7:29       ` Jambunathan K
2013-09-08 22:17         ` David Rogers
2013-09-08 22:55           ` Alan L Tyree
2013-09-09  6:58             ` David Rogers
2013-09-09  7:14               ` Alan L Tyree
2013-09-09  8:10                 ` Suvayu Ali
2013-09-09 19:33                   ` Alan L Tyree
2013-09-09  9:41                 ` Paul Rudin
2013-09-09 19:41                   ` Alan L Tyree
2013-09-09 18:56                 ` Achim Gratz
2013-09-10  0:40                 ` Brian van den Broek
2013-09-10  4:01                   ` Alan Tyree

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:

  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=87hadwqd8f.fsf@gmail.com \
    --to=davidandrewrogers@gmail.com \
    --cc=alantyree@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).