From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Prelude.!!: negative index
Date: Thu, 3 Aug 2017 09:10:19 -0700 [thread overview]
Message-ID: <20170803161019.GA56119@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <e2a60168-8d99-43f4-854e-b4bd25524edb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Thanks! I've created an issue to track this:
https://github.com/jgm/pandoc/issues/3830
Please submit the docx file there, if you come up with it.
That would be helpful indeed.
+++ Greg Bullock [Aug 02 17 18:56 ]:
> Thank you for the reply.
> I'll try to create a small input docx file to demonstrate the problem.
> Indeed gug.native contains two instances of Header 0, as seen in this
> snippet:
> ...
> ,BlockQuote
> [Para [Str "Appendix"]]
> ,Para [Str "A",Space,Str "Instructions",Space,Str "for",Space,Str
> "Adding",Space,Str "an",Space,Str "Appendix",Space,Str "29"]
> ,Header 0 ("figures",[],[]) [Str "FIGURES"]
> ,Para [Strong [Str "Figure",Space,Str "Page"]]
> ,Para [Strong [Str "No",Space,Str "table",Space,Str "of",Space,Str
> "figures",Space,Str "entries",Space,Str "found."]]
> ,Header 0 ("tables",[],[]) [Str "TABLES"]
> ,Para [Strong [Str "Table",Space,Str "Page"]]
> ,Para [Strong [Str "No",Space,Str "table",Space,Str "of",Space,Str
> "figures",Space,Str "entries",Space,Str "found."]]
> ...
> In a re-post of the original message, I reported that the problem seems
> to occur only when writing a reStructuredText file. Converting the
> same docx file to another format (e.g., odt or html) works without
> complaint. (I'd tried to delete the original post and leave only the
> re-post, but it seems that didn't take effect, or didn't take effect in
> time.)
> On Wednesday, August 2, 2017 at 6:55:34 AM UTC-7, John MacFarlane
> wrote:
>
> That's certainly a bug in pandoc, not a mistake on your part!
> I have a guess about what's going on. It would be easiest
> to test if you could send or link to an input docx file
> sufficient to reproduce the problem. If you can't do that,
> could you try the following experiment?
> pandoc -f docx -t native -o gug.native gug.docx
> Then search gug.native to see if it contains
> Header 0
> at any point...
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/e2a60168-8d99-43f4-
> 854e-b4bd25524edb%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/e2a60168-8d99-43f4-854e-b4bd25524edb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-08-03 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 1:56 Greg Bullock
[not found] ` <4ed75c9b-5447-42e1-a69b-a79e5f0b2ac2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-02 13:55 ` John MacFarlane
[not found] ` <20170802135519.GC38349-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-03 1:56 ` Greg Bullock
[not found] ` <e2a60168-8d99-43f4-854e-b4bd25524edb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-03 16:10 ` John MacFarlane [this message]
[not found] ` <20170803161019.GA56119-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-03 17:46 ` Greg Bullock
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=20170803161019.GA56119@Johns-MacBook-Pro.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).