From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Luca <luca-fxeGFEEDKJzVwve80SRih1jMPmZJtkid@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc filter for (Word) index markers
Date: Thu, 27 May 2021 09:55:52 -0700 [thread overview]
Message-ID: <m2o8cwru93.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <18dc38e8-0adc-f198-0aff-3a557815a892-fxeGFEEDKJzVwve80SRih1jMPmZJtkid@public.gmane.org>
Index markers aren't supported at this point.
Luca <luca-fxeGFEEDKJzVwve80SRih1jMPmZJtkid@public.gmane.org> writes:
> Hi!
>
> I would like to write a (python) filter to handle index markers from an
> input docx document. However, I don't seem to be able to spot any (in
> this example, the word "test" is indexed):
>
> $ pandoc -s -t native input.docx
> Pandoc (Meta {unMeta = fromList []})
> [Para [Str "This",Space,Str "is",Space,Str "a",Space,Str "test."]]
>
> A (very) old post in this newsgroup suggests that this operation is yet
> not possible with Pandoc
> (https://groups.google.com/g/pandoc-discuss/c/gnHmLmLCvUQ/m/PnCc1yEMAAAJ).
>
> I was wondering if this is still the case and if there are any
> workarounds I could consider?
> I am on pandoc 2.13.
>
> Many thanks!!
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/18dc38e8-0adc-f198-0aff-3a557815a892%40openbookpublishers.com.
prev parent reply other threads:[~2021-05-27 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 9:37 Luca
[not found] ` <18dc38e8-0adc-f198-0aff-3a557815a892-fxeGFEEDKJzVwve80SRih1jMPmZJtkid@public.gmane.org>
2021-05-27 16:55 ` John MacFarlane [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=m2o8cwru93.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=luca-fxeGFEEDKJzVwve80SRih1jMPmZJtkid@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).