From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt epub workflow
Date: Thu, 03 Jul 2014 10:45:03 +0200 [thread overview]
Message-ID: <53B5180F.1040109@wxs.nl> (raw)
In-Reply-To: <op.xid2ijgopw6hmh@ishamid-pc>
On 7/2/2014 11:12 PM, 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? 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? Does anyone have any examples?
the export is xml reflecting the structure etc and as the whole idea of
xml is that it can be transformed one can map that to anything needed
there is mtx-epub but i need to look into that again as one problem with
epub is that all these substandards and devices differ a bit
context can produce xhtml which then with a css can be viewed in full
blown browsers (i used mozilla) although for some constructs (like
hyperlinks) html like thingies have to be used (not part of css)
as xhtml is not becoming the standard it should be, i'm considering a
variant output where everything is a <div> or <span> which then even
more moves things to css (outputting html tags makes no sense as we then
would end up in tag abuse due to the limited number of tags)
> According to
>
> http://wiki.contextgarden.net/epub
>
> There is no support for graphics in ConTeXt epub output. Are there
> workarounds?
all relevant info is embedded and output (with a css mapping to graphics
that one can supply as png/jpg/whatever)
> In any case, all advice for an efficient workflow for this project will
> be greatly appreciated!
(luigi is working on some stuff that transforms the export into wiki
pages for the garden, e.g. the new publications manual)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 8:45 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
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 [this message]
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=53B5180F.1040109@wxs.nl \
--to=pragma@wxs.nl \
--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).