public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Massimo Coletti
	<massimo.coletti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: From pub to markdown multiple files
Date: Fri, 28 Aug 2020 12:08:06 -0700	[thread overview]
Message-ID: <m2v9h2r3l5.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <f5bdaa89-602e-4d1c-bb47-4c9a5cf50b19n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Not automatically.  But you can always do something like

unzip -d my.epub
for x in $(find my -name '*.xhtml'); do pandoc -s $x -o ${$(basename $x)%.xhtml}.md; done


Massimo Coletti <massimo.coletti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi, I am a new user of panda: it is possible to convert an ePub file to 
> markdown, obtaining multiple output files (one for each xhtml file in the 
> source pub)?
> Thanks
> Massimo
>
> -- 
> 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/f5bdaa89-602e-4d1c-bb47-4c9a5cf50b19n%40googlegroups.com.


  parent reply	other threads:[~2020-08-28 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 18:16 Massimo Coletti
     [not found] ` <f5bdaa89-602e-4d1c-bb47-4c9a5cf50b19n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-28 19:08   ` John MacFarlane [this message]
     [not found]     ` <m2v9h2r3l5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-28 20:42       ` Massimo Coletti

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=m2v9h2r3l5.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=massimo.coletti-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).