emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "D. C. Toedt" <dc@toedt.com>
To: emacs-orgmode@gnu.org
Subject: Tables of contents for individual sections wanted -- will donate
Date: Sun, 29 Jun 2014 13:51:15 -0500	[thread overview]
Message-ID: <CAGN11+1ePWrdDUO0MONmLC3S8jyoROGsmV78oTtEyYnD7ESFyg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2647 bytes --]

Hi all --

BACKGROUND:  I've been using org-mode to develop the *Common Draft*
annotated collection of business contract clauses, in part for the law
school course in contract drafting that I teach to third-year law students.
 I've been posting the collection as a Creative Commons document at
http://www.CommonDraft.org, and plan to expand and maintain it.

QUESTION:  I'm currently using a single, multi-level table of contents
(TOC) at the beginning of the document.  That ends up being a lot to scroll
through to get to the first chapter.  I'd like instead to have:

   - a one-level "master" TOC at the beginning of the document, listing and
   linking to just the articles (in contracts, "articles" are the same as
   "chapters" in books, that is, the top-level sections); and


   - at the beginning of each article, a TOC listing and linking to the
   subheadings within that article.

EXAMPLE of the desired capability:

[book title:] COMMON DRAFT:  Business Contract Clauses, Annotated and
Explained


SUMMARY OF CONTENTS


1.  Definitions & Usages


2.  Arbitration


3.  Assignment of Agreement


[etc.]


ART. 1.  DEFINITIONS & USAGES


TABLE OF CONTENTS

1.1  Affiliate Status


1.2  Agreement Definition


[etc.]


1.1  Affiliate Status

Two entities are affiliates if one of them controls, is controlled by, or
is under common control of the other, where "control" refers ....


1.2  Agreement Definition

The term "this Agreement" refers to this signed document as well as its
exhibits, appendixes, annexes, .....


​Suggestions?  ​If it can't currently be done in org-mode but can be
implemented, I'd donate US$100.00 to the org-mode support fund if someone
were to come up with and publish a working solution.  As for doing it
myself in e-lisp, I'm just scratching the surface of e-lisp, so it's not
something I could undertake at this juncture.


Regards,

--D. C.

*D*ell *C*harles "D. C." Toedt III  *(my** last name is pronounced "Tate") *
Attorney and neutral arbitrator -- tech contracts and intellectual property
​Editor, ​​​Common Draft <http://www.commondraft.org/> project:  Model
contract term sheets & clauses, annotated
dc@toedt.com     LinkedIn: dctoedt <http://www.linkedin.com/in/dctoedt>
Calendar
<https://www.google.com/calendar/embed?src=dc.toedt@toedt.com&mode=WEEK>
(redacted)
O: +1 (713) 364-6545    C: +1 (713) 516-8968
​​

​
Houston, Texas (Central time zone)

Unless expressly stated otherwise, this message is not intended
to serve as an electronic signature nor as assent to an agreement.

[-- Attachment #2: Type: text/html, Size: 9541 bytes --]

             reply	other threads:[~2014-06-29 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 18:51 D. C. Toedt [this message]
2014-06-30 18:40 ` Tables of contents for individual sections wanted -- will donate Ian Barton
2014-06-30 18:55   ` D. C. Toedt
2014-06-30 20:19     ` Ian Barton
2014-07-01  2:45       ` D. C. Toedt
2014-07-01 13:10 ` Nick Dokos

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=CAGN11+1ePWrdDUO0MONmLC3S8jyoROGsmV78oTtEyYnD7ESFyg@mail.gmail.com \
    --to=dc@toedt.com \
    --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).