From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Problem when converting epub to mobi
Date: Sun, 30 Nov 2014 21:47:17 -0800 [thread overview]
Message-ID: <20141201054717.GA59070@localhost.hsd1.ca.comcast.net> (raw)
In-Reply-To: <m5gm64$dbc$1@ger.gmane.org>
Thanks! I think this has already been fixed, in this commit to
pandoc-types:
commit 4425dfc894761cc6cdff8e67d3e5ba78df2d5d4e
Author: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Date: Tue Jul 8 00:23:51 2014 -0600
Added `type="text/css"` to link tags in epub3 template.
I suppose we should get a new release together before the year's
end.
+++ Cesar Romani [Nov 30 14 22:09 ]:
>I'm using pandoc 1.13.2 on Windows 7.
>When I convert markup to epub with pandoc, and subsequently I convert
>the epub to mobi, it doesn't recognize all the customized styles on
>stylesheet.css
>
>I notice that the xhtml files contain the line:
><link rel="stylesheet" href="stylesheet.css" />
>
>it should be:
><link rel="stylesheet" href="stylesheet.css" type="text/css" />
>
>then, all styles on stylesheet.css will be recognized.
>
>
>Many thanks in advance,
>
>--
>Cesar
>
>--
>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/m5gm64%24dbc%241%40ger.gmane.org.
>For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-12-01 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 3:09 Cesar Romani
2014-12-01 5:47 ` John MacFarlane [this message]
2015-01-29 22:04 Cesar Romani
2015-01-30 6:09 ` Pablo Rodríguez
[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
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=20141201054717.GA59070@localhost.hsd1.ca.comcast.net \
--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).