From: Jambunathan K <kjambunathan@gmail.com>
To: Alan L Tyree <alantyree@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Index of cases
Date: Sun, 08 Sep 2013 12:39:30 +0530 [thread overview]
Message-ID: <87a9jnzt5h.fsf@gmail.com> (raw)
In-Reply-To: <522C16AD.9030102@gmail.com> (Alan L. Tyree's message of "Sun, 08 Sep 2013 16:18:21 +1000")
> Here are the LaTeX macros that I use.
Seeing a concrete example helps. Helps avoid speculation. I don't
understand Latex, so I will speculate ...
> #+BEGIN_EXAMPLE
> Provided the documents are in order, the buyer must pay. This is so
> even if it is known that the goods have been lost at sea. For example,
> in \cdx{Manbre Saccharine Co Ltd v Corn Products Co Ltd}{[1919] 1
> KB 198} the defendants sold American pearl starch to the plaintiffs
> on CIF London terms.
> #+END_EXAMPLE
Seems like a heretical form of Inline footnotes to me. I would suggest
that you "fake" a Bibliography entry in a *.bib file and use JabRef to
create your "References" or "Endnotes".
> but I haven't used it with book length writing that requires
> indexes.
You need to just command the machine to do the export :-)
> Obviously would be nice, but I can submit the chapters
> separate from the indexes so it may not be necessary.
As a side-note, I would like to at some point in time add support for
*.odm.
> both approaches would require quite a bit of markup to go back into
> the main part of the manuscript.
A markup is markup. The markup I suggest is paragraph-oriented - which
Org is good at. The markup that you have resorted to is
span/inline-style at which Org sucks.
> This is what I'm trying to avoid since the publisher and editors have
> always required Word.
Why get caught in specifics of Markup when all you want is a Word or a
OpenDocument format or even a plain text format.
In the grand scheme of things, insisting plain text or Org or Word
doesn't really matter. If you want and do get Word, then markup - Org
or otherwise - doesn't matter.
> I have (I think) got them to agree to accept plain text, but I would
> like to make it just as plain as possible.
Oh, Ok. Looks like there is "exchange of ideas" between the author and
publisher...
> Paragraphs in the text may refer to many cases, so I don't think your
> suggestions will meet that goal.
Seems like Citation or Footnote to me.
next prev parent reply other threads:[~2013-09-08 7:07 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
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 [this message]
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:
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=87a9jnzt5h.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=alantyree@gmail.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).