From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB workflow from ConTeXt source?
Date: Thu, 17 Feb 2011 10:49:11 +0100 [thread overview]
Message-ID: <4D5CEF17.4040004@wxs.nl> (raw)
In-Reply-To: <D7225CF0-F6CF-485F-BE01-C8A254EFCA93@storytotell.org>
On 17-2-2011 9:10, Daniel Lyons wrote:
> ePub is definitely structured. I would say too structured, since it makes you provide both a ToC manifest and a navigation manifest that necessarily must include almost identical information ;) Of course, depending on a simplified browser for your document viewing and having lots of secret failover modes to handle poorly formatted documents makes the structure less meaningful than it ought to be.
>
> You are free to break your document into as many HTML chunks as you wish, but you are limited to fairly prosaic HTML and CSS. I'm of the impression the HTML documents generally map onto chapters so as not to distress the hardware's memory constraints too much.
what mean with not being structured is that clever css trickery can hide
weird structure
i have a style somewhere that typesets an epub document (directly) but
when testing an epub file from somehwere it found out that there were
artifacts like
<H1>1</H1><H3>Chapter title</H3>
so i decided not to spend too much time on it and only bother with epub
if it comes to me as project
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:[~2011-02-17 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:42 Gerben.Wierda
2011-02-16 16:47 ` Wolfgang Schuster
2011-02-17 7:14 ` Gerben Wierda
2011-02-17 7:59 ` Hans Hagen
2011-02-17 8:10 ` Daniel Lyons
2011-02-17 9:49 ` Hans Hagen [this message]
2011-02-17 10:48 ` Gerben Wierda
2011-02-17 18:52 ` William Adams
2011-02-18 2:43 Mica Semrick
2011-02-18 18:12 ` Daniel Lyons
2011-02-19 8:32 ` Gerben Wierda
2011-02-19 11:40 ` Hans Hagen
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=4D5CEF17.4040004@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).