public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mohit Bansal <bansalmohit031-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Html to docx using pandoc
Date: Tue, 1 Oct 2019 02:15:44 -0700 (PDT)	[thread overview]
Message-ID: <c360b9b1-8bcc-4b76-9e03-aa6308de229d@googlegroups.com> (raw)
In-Reply-To: <43195bbb-c3c1-4f2c-b164-6394b45247c4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]

process of conversion of the document from HTML to Docx is headed.
script in HTML is also there.
how could I preprocess the Html?
could u provide a sample code how should I proceed further?

On Tuesday, October 1, 2019 at 2:37:05 PM UTC+5:30, Agustín Martín wrote:
>
> I guess you could preprocess your html somehow, or just the script part 
> with node, and get the chart's URL 
> <https://stackoverflow.com/a/22523217/4045620>. If you could insert that 
> URL back into your original document it would be picked up by pandoc (I 
> think).
> As jmf said, this is a bit out of scope for pandoc itself.
>
>

-- 
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/c360b9b1-8bcc-4b76-9e03-aa6308de229d%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1943 bytes --]

  parent reply	other threads:[~2019-10-01  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 11:57 Mohit Bansal
     [not found] ` <65c79c89-ba69-4895-bc7e-35e75a2895b5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-30 15:52   ` John MacFarlane
2019-10-01  5:44   ` Mohit Bansal
     [not found]     ` <785651a7-511c-4eab-adf2-062d92db8472-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-01  6:39       ` Mohit Bansal
     [not found]         ` <44aff450-f6c1-4629-880e-9e469e44fbc8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-01  9:07           ` Agustín Martín
     [not found]             ` <43195bbb-c3c1-4f2c-b164-6394b45247c4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-01  9:15               ` Mohit Bansal [this message]
     [not found]                 ` <c360b9b1-8bcc-4b76-9e03-aa6308de229d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-01 16:16                   ` John MacFarlane

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=c360b9b1-8bcc-4b76-9e03-aa6308de229d@googlegroups.com \
    --to=bansalmohit031-re5jqeeqqe8avxtiumwx3w@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).