From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: I'd like to submit a full example to be included with Pandoc documentation
Date: Sun, 23 Jul 2017 10:00:32 +0200 [thread overview]
Message-ID: <20170723080032.GD67976@macbook-air-2.home> (raw)
In-Reply-To: <980c4067-07bf-428e-a83a-525c9627ce6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
"it doesn't work" doesn't give us much to go on. Can you
say precisely what didn't work?
+++ CR [Jul 19 17 10:15 ]:
> Yes I followed that tutorial and it doesn't work for my source which is
> in Markdown.
> On Tuesday, July 4, 2017 at 5:18:53 AM UTC-4, John MacFarlane wrote:
>
> Well, I suppose you've seen the tutorial on the website?
> [1]http://pandoc.org/epub.html
> If you have suggestions for changes, the source is here:
> [2]https://github.com/jgm/pandoc-website/blob/master/epub.txt
> +++ CR [Jul 03 17 08:43 ]:
> > This sample would be how to make an EPUB from Markdown. It could
> go
> > under the documentation site under the "Documentation" dropdown
> (which
> > has some subtopics). It seems many questions could be answered
> by
> > seeing a fully functional example.
> > I'd like to include:
> > 1. A simple example of one Markdown file with meta data and
> showing
> > how to do basic things, including CSS.
> > 2. The resulting EPUB file.
> > 3. Screenshot of the directory.
> > 4. CSS file.
> >
> > How can I got about doing this?
> > Thanks. Have a good holiday!
> >
> > --
> > 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][3]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To post to this group, send email to
> > [2][4]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> > [3][5]https://groups.google.com/d/msgid/pandoc-discuss/
> 2e7a346f-676f-45dc-
> > 8965-064a1eaaf2a3%[6]40googlegroups.com.
> > For more options, visit [4][7]https://groups.google.com/
> d/optout.
> >
> >References
> >
> > 1. mailto:[8]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 2. mailto:[9]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 3. [10]https://groups.google.com/d/
> msgid/pandoc-discuss/2e7a346f-676f-45dc-8965-064a1eaaf2a3@
> googlegroups.com?utm_medium=email&utm_source=footer
> > 4. [11]https://groups.google.com/d/optout
>
> --
> 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 [12]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [13]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [14]https://groups.google.com/d/msgid/pandoc-discuss/980c4067-07bf-428e
> -a83a-525c9627ce6e%40googlegroups.com.
> For more options, visit [15]https://groups.google.com/d/optout.
>
>References
>
> 1. http://pandoc.org/epub.html
> 2. https://github.com/jgm/pandoc-website/blob/master/epub.txt
> 3. javascript:/
> 4. javascript:/
> 5. https://groups.google.com/d/msgid/pandoc-discuss/2e7a346f-676f-45dc-
> 6. http://40googlegroups.com/
> 7. https://groups.google.com/d/optout
> 8. javascript:/
> 9. javascript:/
> 10. https://groups.google.com/d/msgid/pandoc-discuss/2e7a346f-676f-45dc-8965-064a1eaaf2a3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 11. https://groups.google.com/d/optout
> 12. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 13. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 14. https://groups.google.com/d/msgid/pandoc-discuss/980c4067-07bf-428e-a83a-525c9627ce6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 15. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-07-23 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 15:43 CR
[not found] ` <2e7a346f-676f-45dc-8965-064a1eaaf2a3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-03 15:45 ` CR
2017-07-04 9:17 ` John MacFarlane
[not found] ` <20170704091750.GB26431-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-07-19 17:15 ` CR
[not found] ` <980c4067-07bf-428e-a83a-525c9627ce6e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-23 8:00 ` John MacFarlane [this message]
2017-07-04 9:27 ` Kolen Cheung
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=20170723080032.GD67976@macbook-air-2.home \
--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).