From: rpgoldman@sift.info
To: emacs-orgmode@gnu.org
Subject: Translate #+INDEX to Latex \index{} on export
Date: Thu, 28 Apr 2011 06:47:22 -0500 [thread overview]
Message-ID: <1303991243-30731-1-git-send-email-rpgoldman@sift.info> (raw)
The following email contains a patch that will cause the latex export
preprocessor to rewrite #+INDEX: lines in an org file into LaTeX style
\index{} entries.
As far as I can tell, this should be The Right Thing --- latex doesn't seem
to do anything bad if there are index entries without makeindex. So no
downside. And it doesn't seem right to have to do #+INDEX for HTML export
and #+LATEX: \index{} for latex export.
I believe that this should be complemented by some additional code that
would:
1. Add code to turn on and off index generation and appropriately add the
makeindex package and the \makeindex
2. Possibly add code to turn /off/ this translation in the case where the
user wishes to have HTML and Latex documents indexed differently.
Cheers,
r
next reply other threads:[~2011-04-28 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 11:47 rpgoldman [this message]
2011-04-28 11:47 ` [PATCH] Make the latex export preprocessor rewrite #+INDEX to \index rpgoldman
2011-04-28 12:33 ` Nick Dokos
2011-04-28 15:23 ` Robert Goldman
2011-04-28 15:29 ` Robert Goldman
2011-04-28 15:38 ` Patch --- adding an easy template for #+index rpgoldman
2011-04-28 19:11 ` Bernt Hansen
2011-04-28 19:59 ` Robert Goldman
2011-04-28 21:31 ` Bernt Hansen
2011-04-28 15:38 ` [PATCH] Add an easy template for index (i), and move include file to I from i rpgoldman
2011-05-04 7:49 ` [Accepted] " Carsten Dominik
2011-04-29 21:45 ` Bug Re: [PATCH] Make the latex export preprocessor rewrite #+INDEX to \index Robert Goldman
2011-05-04 7:59 ` [Accepted] " Carsten Dominik
2011-05-04 15:08 ` Robert Goldman
2011-05-04 22:36 ` Carsten Dominik
2011-05-04 22:46 ` Robert Goldman
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=1303991243-30731-1-git-send-email-rpgoldman@sift.info \
--to=rpgoldman@sift.info \
--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).