From: Robert Goldman <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Making an index in latex export --- surprisingly difficult
Date: Tue, 26 Apr 2011 16:58:41 -0500 [thread overview]
Message-ID: <4DB74011.2020600@sift.info> (raw)
In-Reply-To: <6174.1303854727@alphaville.americas.hpqcorp.net>
On 4/26/11 Apr 26 -4:52 PM, Nick Dokos wrote:
> Robert Goldman <rpgoldman@sift.info> wrote:
>
>> I was trying to make an index in latex export and found that it was very
>> difficult to make it work. I wonder if this could be simplified.
>> Here's what I had to do:
>>
....
>> 2. put in \index commands (I don't /believe/ #+INDEX works, but I could
>> be wrong)
Am I right about #+INDEX not being translated in the latex back end (it
seems not to work, but it's hard to verify a negative)?
If so, would this be hard to fix? If it wouldn't, seems like that would
be A Good Thing.
....
>> 4. Modify the org-latex-to-pdf-process to
>>
>> ("pdflatex -interaction nonstopmode -output-directory %o %f" "makeindex
>> -o %b.ind %b.idx" "pdflatex -interaction nonstopmode -output-directory
>> %o %f" "pdflatex -interaction nonstopmode -output-directory %o %f")
>>
>> [This was /somewhat/ of a big deal. Suggest we add support for indexing
>> as a built-in option, like bibtex...]
>>
>
> Maybe you can try the texi2dvi option (I think it runs makeindex), but
> texi2dvi did have a bug that has caused problems here in the past:
> that's the reason it's not the default setting for
> org-latex-to-pdf-process. If you run into the bug but still want to try
> texi2dvi anyway, see
>
> http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00032.html
>
> for the fix Karl Berry applied to the development sources.
Once one has makeindex hacked in there (oh, and you've broken the
security!), it works fine, thanks.
>
>> 5. The REAL big deal: edit my texmf.cf file to break the security
>> protection of openout_any=p. By default, makeindex will refuse to open
>> an absolute pathname. But org-mode will only pass absolute pathnames to
>> makeindex (AFAICT). Question: it seems like bibtex should suffer from
>> this same restriction. Has anyone had that problem with it?
>>
>
> I haven't had the problem, primarily because I haven't used bibtex
> through org yet :-) But bibtex should exhibit the same problem: the
> bibtex change predated the makeindex one. Maybe bibtex is only called
> with a relative path (if that's the case, then the same method should
> cure makeindex as well). BTW, ".." is not allowed in the relative path:
> you can only use subdirectories of the current directory.
>
> Nick
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2011-04-26 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:09 Making an index in latex export --- surprisingly difficult Robert Goldman
2011-04-26 21:26 ` Suvayu Ali
2011-04-26 21:44 ` Robert Goldman
2011-04-28 9:28 ` Eric S Fraga
2011-04-28 11:04 ` Robert Goldman
2011-04-28 11:52 ` Eric S Fraga
2011-04-26 21:52 ` Nick Dokos
2011-04-26 21:58 ` Robert Goldman [this message]
2011-04-26 23:14 ` Nick Dokos
2011-04-27 1:32 ` Robert Goldman
2011-04-27 6:35 ` Nick Dokos
2011-04-27 7:38 ` Thomas S. Dye
2011-05-09 6:08 ` Tom Dye
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=4DB74011.2020600@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).