public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Szepieniec <mszepien-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Customize EPUB Title Page
Date: Sun, 28 Dec 2014 13:49:42 +0100	[thread overview]
Message-ID: <CAE4-1rU5pJmLwGwFs=ww+DJ-ZH-wYyk=X7wW9LPePFX-ag2ipQ@mail.gmail.com> (raw)
In-Reply-To: <549FEA2B.2080005-S0/GAf8tV78@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3324 bytes --]

Is that not simply a YAML issue?

From http://www.pandoc.org/README.html:

The pipe character (|) can be used to begin an indented block that will be
interpreted literally, without need for escaping. This form is necessary
when the field contains blank lines:

On Sun, Dec 28, 2014 at 12:31 PM, Pablo Rodríguez <oinos-S0/GAf8tV78@public.gmane.org> wrote:

> On 12/22/2014 05:25 PM, John MacFarlane wrote:
> > (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.
>
> John,
>
> I’m afraid that the rights metadata field is always considered as being
> a single paragraph.
>
> To make it more customizable, would it be possible that the rights value
> won’t be considered as a single paragraph?
>
> Otherwhise, this won’t work:
>
> ---
> title: My first small ebook
> author: K. Weinert
> stylesheet: mystyle.css
> date: 2014-12-20
> rights: © 2014 Karsten Weinert
>
>     All rights reserved.
>
>     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.
> stylesheet: book.css
> ...
>
> Many thanks for your help,
>
>
> Pablo
> --
> http://www.ousia.tk
>
> --
> 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/549FEA2B.2080005%40web.de
> .
> 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/CAE4-1rU5pJmLwGwFs%3Dww%2BDJ-ZH-wYyk%3DX7wW9LPePFX-ag2ipQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 5088 bytes --]

  parent reply	other threads:[~2014-12-28 12:49 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.
2014-12-28 11:31       ` Pablo Rodríguez
     [not found]         ` <549FEA2B.2080005-S0/GAf8tV78@public.gmane.org>
2014-12-28 12:49           ` Mark Szepieniec [this message]
     [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='CAE4-1rU5pJmLwGwFs=ww+DJ-ZH-wYyk=X7wW9LPePFX-ag2ipQ@mail.gmail.com' \
    --to=mszepien-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).