Hi John, Thanks - it would be indeed a one-time conversion. I may end up going this route, but I thought there should be a proper way of doing it :)
Best, --Diego On Tue, Feb 20, 2018 at 1:25 AM, John Kitchin <jkitc...@andrew.cmu.edu> wrote: > If it is a one-time conversion, it might be worthwhile just replacing the > index terms with something temporary, getting to the org-file, and then > putting them back in the right way. For example, you could replace each > term with a uuid, and keep a list that maps the uuid to the term. Then the > uuid would pass through the pandoc untouched, and afterwards, go back > through and replace the uuid with the #+INDEX entries. > > I don't know if that is worth the effort, but it might get you a faster > org-doc than bug reporting :) > > John > > ----------------------------------- > Professor John Kitchin > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 <(412)%20268-7803> > @johnkitchin > http://kitchingroup.cheme.cmu.edu > > > On Mon, Feb 19, 2018 at 11:54 AM, Diego Zamboni <di...@zzamboni.org> > wrote: > >> Hi, >> >> I have a large document (a book) written in AsciiDoc, and I’ve been >> thinking of converting it to org-mode, which I find eminently more >> readable. The method I’ve come up with is: >> >> 1. AsciiDoc -> Docbook using asciidoc or asciidoctor >> 2. Docbook -> org using pandoc >> >> The conversion seems to work well, except for one thing: I have index >> terms in my AsciiDoc files using the ‘((( … )))’ syntax ( >> http://asciidoctor.org/docs/user-manual/#index-terms). Step 1 converts >> them correctly into <indexterm> tags, but pandoc inserts them as part of >> the main text instead of producing‘#+INDEX entries. >> >> Before I go report the bug to Pandoc, I was wondering if anyone has tried >> this and maybe come up with some other way of doing the conversion. >> >> Thanks! >> >> —Diego >> >> >
