From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Epub woes
Date: Thu, 15 Nov 2012 19:13:10 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.02.1211151908510.1091@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <50A53B55.3010204@meahan.net>
On Thu, 15 Nov 2012, Bill Meahan wrote:
> I tried to generate an epub document using ConTeXt following the recipe on
> the wiki. Didn't work. So, I tried running the export-example.tex file that
> comes with the distribution, unmodified. Same bad results.
>
> Cover is not generated
> TOC is not generated (though it is noted this might be the state of the
> export)
> Sectioning doesn't happen.
> Paragraphing doesn't happen.
> The resultant epub file cannot even be opened with FBReader.
>
> Importing the epub into Sigil shows one big blob of text, with only the
> between word spacing that's present in the source file. The \quotation{}
> markup did get turned into quotation marks, chapter numbers were generated
> and the rest of the markup was stripped out.
>
> Same behavior with both the TeXLive 2012 version of ConTeXt and a quite
> recent beta.
>
> What am I doing wrong?
Have you considered using pandoc to generate epub?
If your text is relatively simple (no multiline math, no fancy image
scaling, no complicated tables, etc.), then Markdown is a reasonable input
format. You can use pandoc to translate the text to multiple output
formats (including ConTeXt).
In general, I have found pandoc's XHTML export to be more predictable than
that of ConTeXt. I have used pandoc's epub export only for short articles,
but from what I remember, it does handle cover images and toc correctly.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-16 0:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:58 Bill Meahan
2012-11-15 19:24 ` Wolfgang Schuster
2012-11-15 20:20 ` Bill Meahan
2012-11-15 23:55 ` Marcin Borkowski
2012-11-16 0:13 ` Aditya Mahajan [this message]
2012-11-16 0:48 ` Bill Meahan
2012-11-16 4:17 ` Aditya Mahajan
2012-11-16 15:41 ` Bill Meahan
2012-11-16 16:36 ` Aditya Mahajan
2012-11-16 6:49 ` Andy Thomas
2012-11-16 7:13 ` luigi scarso
2012-11-16 7:18 ` Andy Thomas
2012-11-16 23:18 ` Zenlima
2012-11-16 23:21 ` Zenlima
2012-11-16 23:41 ` Bill Meahan
2012-11-17 7:08 ` luigi scarso
2012-11-17 9:18 ` Alan BRASLAU
2012-11-17 16:48 ` Bill Meahan
2012-11-17 17:24 ` luigi scarso
2012-11-16 10:21 ` Keith J. Schultz
2013-11-16 15:16 EPUB woes Bill Meahan
2013-11-16 16:00 ` Keith J. Schultz
2013-11-16 16:51 ` Bill Meahan
2013-11-16 17:37 ` Aditya Mahajan
2013-11-16 18:15 ` Bill Meahan
2013-11-18 9:00 ` Keith J. Schultz
2013-11-18 12:21 ` Hans Hagen
2013-11-18 15:11 ` Keith J. Schultz
2013-11-18 15:33 ` Hans Hagen
2013-11-18 18:12 ` Keith J. Schultz
2013-11-19 21:39 ` Mica Semrick
2013-11-20 9:39 ` Keith J. Schultz
2013-11-20 13:59 ` Aditya Mahajan
2013-11-20 18:11 ` Bill Meahan
2013-11-20 19:43 ` Jan Tosovsky
2013-11-20 19:12 ` Keith J. Schultz
2013-11-18 8:05 ` Keith J. Schultz
2013-11-16 16:07 ` Wolfgang Schuster
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=alpine.LNX.2.02.1211151908510.1091@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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).