From: Aditya Mahajan <adityam@umich.edu>
To: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
Cc: ntg-context@ntg.nl
Subject: Re: ConTeXt epub workflow
Date: Wed, 2 Jul 2014 23:42:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.03.1407022331300.2629@hzvpu.rqh> (raw)
In-Reply-To: <op.xid2ijgopw6hmh@ishamid-pc>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1736 bytes --]
On Wed, 2 Jul 2014, Idris Samawi Hamid ادريس سماوي حامد wrote:
> Dear gang,
>
> I have an urgent project that needs three outputs: pdf, epub, and kindle. The
> formatting needs are pretty basic. In your experience:
>
> What is the recommended, more efficient workflow for this sort of thing?
> Should I start with markdown and then generate context and epub (then convert
> epub=>kindle I presume)? Or does one context file with pdf and epub outputs
> work well?
If you are short on time and your formatting needs are basic, I would
suggest that you start with markdown as your input format and use pandoc
to convert it to epub and context. There are various tools to do epub to
kindle conversion.
Markdown in a very primitive input format. For anything non-trivial
(multiple types of floats, multiple types of emphasis, etc.) you have to
resort to some sort of pre-processing of input.
Pandoc is the only tool that does Markdown to ConTeXt conversion. There
are more tools for Markdown to LaTeX conversion. The ConTeXt markup
generated by pandoc is not ideal (\bf, \em, etc instead of semantic
markup); it is possible to change the output, but you need to learn how to
program in Haskell.
You can start with ConTeXt and generate epub. However, ConTeXt generates
XML+CSS rather than "pure" XHTML. Most browsers can handle XML+CSS, but
most (all?) epub readers cannot. So, the output is not usable without some
post-processing (this might have changed, I haven't tested ConTeXt epub in
a year or so).
In the long run, I think that the "easiest" way to generate multiple
output formats for non-trivial input text is to use XML as your input
format.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2014-07-03 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 21:12 Idris Samawi Hamid ادريس سماوي حامد
2014-07-02 21:18 ` Idris Samawi Hamid ادريس سماوي حامد
2014-07-03 8:48 ` Hans Hagen
2014-07-03 3:13 ` Henning Hraban Ramm
2014-07-03 3:42 ` Aditya Mahajan [this message]
2014-07-03 7:14 ` Gour
2014-07-03 8:23 ` Hans Hagen
2014-07-03 7:41 ` Keith McKay
2014-07-03 8:45 ` Hans Hagen
2014-07-03 18:51 ` Jan Tosovsky
2014-07-03 4:15 Andres Conrado
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.03.1407022331300.2629@hzvpu.rqh \
--to=adityam@umich.edu \
--cc=ishamid@colostate.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).