From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Best strategy for ConTeXt to ePub update
Date: Tue, 5 Feb 2019 09:00:20 +0100 [thread overview]
Message-ID: <EA7910B0-7F74-4DB9-A0E5-E4FFBB242ECF@fiee.net> (raw)
In-Reply-To: <d0e1c921-7a1a-c366-7e68-d4d23b3488e2@regnet.cz>
Am 2019-02-04 um 20:26 schrieb Martin Bruchanov <bruxy@regnet.cz>:
> While ago I wrote a book (http://sstv-handbook.com/) in ConTeXt and I have started to thinking about possibility to export also ePub and xHTML besides the PDF version.
>
> Few questions:
>
> 1. What is current support of ePub, will it export pictures automatically?
it will, but you need postprocessing to make them usable for HTML/ePub
> 2. Do I need to rewrite source code to use those verbose \startsXXX of every element (paragraph, item,...) or is there any simplier way how to handle sources as they are now?
Yes. No.
For a proper XML/XHTML export you need this markup. Also use \definehighlighting instead of switches like \em or \bf.
In my experience, you can work with the exported raw XML if your markup is good, but you must convert it to usable HTML yourself.
Unfortunately I never completed my workflow notes at:
https://wiki.contextgarden.net/Export
https://wiki.contextgarden.net/ePub
Export got better since then, but I’m not up to date about the current state. My latest attempts to get an ePub from a book worked quite well with my conversion workflow (where I use ConTeXt’s export and ePub script, but re-make most of the ePub files via Python and XSLT).
Footnotes and such are a PITA, because there’s no working mechanism in ePub for them.
ePub reader compatibility is still a big mess.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-02-05 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 19:26 Martin Bruchanov
2019-02-05 8:00 ` Henning Hraban Ramm [this message]
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=EA7910B0-7F74-4DB9-A0E5-E4FFBB242ECF@fiee.net \
--to=texml@fiee.net \
--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).