From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: ConTeXt epub workflow
Date: Wed, 02 Jul 2014 15:18:00 -0600 [thread overview]
Message-ID: <op.xid2saz4pw6hmh@ishamid-pc> (raw)
In-Reply-To: <op.xid2ijgopw6hmh@ishamid-pc>
On Wed, 02 Jul 2014 15:12:10 -0600, Idris Samawi Hamid ادريس سماوي حامد
<ishamid@colostate.edu> wrote:
> 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? Many years ago I did some documents in ConTeXt
> with both print and screen pdfs from a single source. Can we do the
> latter in ConTeXt now?
^^^^^^^^
Er, Can we do the *former* in ConTeXt? Viz., generate both pdf and epub
from a single source.
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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-02 21:18 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 ادريس سماوي حامد [this message]
2014-07-03 8:48 ` Hans Hagen
2014-07-03 3:13 ` Henning Hraban Ramm
2014-07-03 3:42 ` Aditya Mahajan
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=op.xid2saz4pw6hmh@ishamid-pc \
--to=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).