From: "Karsten W." <karsten.g.weinert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Customize EPUB Title Page
Date: Mon, 22 Dec 2014 16:30:05 -0800 (PST) [thread overview]
Message-ID: <e187874d-86f1-4859-8af8-d5c028740113@googlegroups.com> (raw)
In-Reply-To: <20141222162500.GB95411-bi+AKbBUZKaOwiQRAsGx7a+gxsCIUpAnHiGdP5j34PU@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3864 bytes --]
Thanks for your replies!
I just downloaded pandoc 1.13.2 and learned about the
pandoc -D epub
and
pandoc --template=FILE
features. This is great and easy to understand. I will certainly use it at
some point.
For the current project, I decided to create a colophon section at the end
of the document where all the stuff, credits, disclaimer, etc goes into.
Kind regards
Karsten
Am Montag, 22. Dezember 2014 17:25:16 UTC+1 schrieb John MacFarlane:
>
> (These remarks concern pandoc 1.13.2 and its default templates.)
>
> You can customize the epub (or epub3) template. See the User's Guide
> under Templates for basic instructions. The epub templates have
> conditionals
>
> $if(titlepage)$
> ...
> $endif$
>
> and whatever goes in place of the ... will be on the title page.
> So, this is extremely customizable.
>
> +++ Karsten W. [Dec 21 14 12:05 ]:
> >Hi,
> >still an my small first ebook project, I am exploring the possibilities
> of
> >the title page before the table of contents. Currently, it shows title,
> >name and date:
> >
> ><body>
> > <h1 class="title">My first small ebook</h1>
> > <h2 class="author">K. Weinert</h2>
> > <h3 class="date">2014-12-20</h3>
> ></body>
> >
> >Now is it possible to include further metadata on this page? For
> instance,
> >the "rights" would be useful in my case. With the metadata being:
> >
> >---
> >title: My first small ebook
> >author: K. Weinert
> >cover-image: cover.jpg
> >stylesheet: mystyle.css
> >date: 2014-12-20
> >rights: |
> > (c) by me.
> >
> > The author is not offering this ebook as legal, accounting, or other
> >professional services advice. While best efforts have been used in
> >preparing this book,
> > the author make no representations or warranties of any kind and
> assume
> >no liabilities of any kind with respect to the accuracy or completeness
> of
> >the
> > contents and specifically disclaim any implied warranties of
> >merchantability or fitness of use for a particular purpose.
> >
> > Neither the author nor the publisher shall be held liable or
> >responsible to any person or entity with respect to any loss or
> incidental
> >or consequential damages
> > caused, or alleged to have been caused, directly or indirectly, by
> the
> >information or programs contained herein.
> >
> >...
> >
> >For further projects, also the abstract metadata comes to mind as a
> >candidate for the title page. I searched pandoc's user guide and the epub
> >example "Pro Git",
> >but did not find something.
> >
> >Any hints on styling the title page are appreciated!
> >
> >Kind regards
> >Karsten
> >
> >--
> >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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> <javascript:>.
> >To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/cb41e923-e763-4f38-aabc-426c8fa3f3a3%40googlegroups.com.
>
> >For more options, visit 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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e187874d-86f1-4859-8af8-d5c028740113%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 5973 bytes --]
next prev parent reply other threads:[~2014-12-23 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 20:05 Karsten W.
[not found] ` <cb41e923-e763-4f38-aabc-426c8fa3f3a3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-21 20:44 ` Pablo Rodríguez
2014-12-22 16:25 ` John MacFarlane
[not found] ` <20141222162500.GB95411-bi+AKbBUZKaOwiQRAsGx7a+gxsCIUpAnHiGdP5j34PU@public.gmane.org>
2014-12-23 0:30 ` Karsten W. [this message]
2014-12-28 11:31 ` Pablo Rodríguez
[not found] ` <549FEA2B.2080005-S0/GAf8tV78@public.gmane.org>
2014-12-28 12:49 ` Mark Szepieniec
[not found] ` <CAE4-1rU5pJmLwGwFs=ww+DJ-ZH-wYyk=X7wW9LPePFX-ag2ipQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-28 16:56 ` Pablo Rodríguez
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=e187874d-86f1-4859-8af8-d5c028740113@googlegroups.com \
--to=karsten.g.weinert-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).