public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Problem when converting epub to mobi
Date: Fri, 30 Jan 2015 07:09:33 +0100	[thread overview]
Message-ID: <54CB201D.6060408@web.de> (raw)
In-Reply-To: <maeapp$62g$1@ger.gmane.org>

On 01/29/2015 11:04 PM, Cesar Romani wrote:
> [...]
> Was it added? Because I'm having the same behavior as before, i.e. all
> xhtml files have
> <link rel="stylesheet" href="stylesheet.css" />
> 
> and not
> <link rel="stylesheet" href="stylesheet.css" type="text/css" />

Hi Cesar,

I get (copied and pasted from an xhtml file inside the ePub document):

    <link rel="stylesheet" type="text/css" href="stylesheet.css" />

when invoking:

    $ pandoc book.md -o book.epub -t epub3

> Moreover, on nav.xhtml it was added:
> 
> <nav epub:type="landmarks" hidden="hidden">
>    <ol>
>      <li>
>        <a href="cover.xhtml" epub:type="cover">Cover</a>
>      </li>
>      <li>
>        <a href="#toc" epub:type="toc">Table of contents</a>
>      </li>
>    </ol>
> </nav>
> 
> which has the effect, that when converting the epub to mobi, it doesn't
> contain any Table of Contents.

I get:

    <nav epub:type="landmarks" hidden="hidden">
      <ol />
    </nav>

after:

    <nav epub:type="toc" id="toc">
      <h1 id="toc-title">pandoc</h1>
      <ol class="toc">
        <li id="toc-li-1">
          <a href="ch001.xhtml">pandoc</a>
        </li>
        <li id="toc-li-2">
          <a href="ch002.xhtml">[Copyright page]</a>
        </li>
      </ol>
    </nav>

I use the latest stable release (pandoc-1.13.2).

Sorry for the stupid question, but are you (sure you are) using this
release: https://github.com/jgm/pandoc/releases/latest?

Jist in case it helps,


Pablo
-- 
http://www.ousia.tk


  reply	other threads:[~2015-01-30  6:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 22:04 Cesar Romani
2015-01-30  6:09 ` Pablo Rodríguez [this message]
     [not found]   ` <54CB201D.6060408-S0/GAf8tV78@public.gmane.org>
2015-01-30 15:32     ` Cesar Romani
     [not found]       ` <54CBA422.9060108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-30 21:49         ` John MacFarlane
     [not found]           ` <20150130214949.GA1805-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-01-31  1:56             ` Cesar Romani
2015-01-31  2:21 ` John MacFarlane
     [not found]   ` <20150131022105.GA5231-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-01-31  3:14     ` Cesar Romani
  -- strict thread matches above, loose matches on Subject: below --
2014-12-01  3:09 Cesar Romani
2014-12-01  5:47 ` 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=54CB201D.6060408@web.de \
    --to=oinos-s0/gaf8tv78@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).