public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ian Fantom <ian-0jttZa1E5sTe9xe1eoZjHA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Conversion of indexes?
Date: Wed, 10 May 2023 15:09:48 +0100	[thread overview]
Message-ID: <25f1776b-050f-dfc4-63c8-e03f143adc85@fantom.org.uk> (raw)
In-Reply-To: <87wn1gqu6d.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>

Thanks. Interesting.

I wish to complete an indexing management system I've been writing in 
Perl, to greatly speed up the indexing process. But I can't cope with 
the multiplicity of word process formats. It would be extremely useful 
if I could just write it for Latex then convert.

So if someone is motivated in incorporating conversion of the indexing 
tags into Pandoc, at least one person will be very happy!

Regards,

Ian

On 10/05/2023 12:52, Albert Krewinkel wrote:
> Ian Fantom <ian-0jttZa1E5sTe9xe1eoZjHA@public.gmane.org> writes:
>
>> I understand that Pandoc does not convert indexing.
>>
>> Is this still the case?
>>
>> Is there a particular problem in the conversion of indexing?
>>
>> Are there any plans to incorporate indexing in Pandoc?
> It's been suggested as a new feature and has not been ruled out.
> The relevant issue is https://github.com/jgm/pandoc/issues/6415
>
>


      parent reply	other threads:[~2023-05-10 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 10:53 Ian Fantom
     [not found] ` <af1d80aa-77b6-8f68-0ffc-e20f51065949-0jttZa1E5sTe9xe1eoZjHA@public.gmane.org>
2023-05-10 11:10   ` Stephan Meijer
     [not found]     ` <a2bfed55-19f7-492d-bd9e-7f9968e91777n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-10 11:20       ` Ian Fantom
2023-05-10 11:52   ` Albert Krewinkel
     [not found]     ` <87wn1gqu6d.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-10 14:09       ` Ian Fantom [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25f1776b-050f-dfc4-63c8-e03f143adc85@fantom.org.uk \
    --to=ian-0jttza1e5ste9xe1eozjha@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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. 
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 NNTP newsgroup(s).