From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB XHTML Format
Date: Thu, 5 Sep 2013 09:57:59 -0700 [thread overview]
Message-ID: <CAANrE7o=L7b4+s6Op+5o=bHvbySuok_jnuMbTNfTi8unOUazTA@mail.gmail.com> (raw)
In-Reply-To: <5228B383.2080004@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]
Hi,
<div class="section" ...>
> <div class="..." ...>
> <div>
> </div>
>
> i.e. only divs and spans
I think that would be a more robust output format, technically, easier to
adapt, and more readily conform to the strict XHTML tag subset.
The other issue I encountered was this:
\startfrontmatter
\startstandardmakeup
Title page
\stopstandardmakeup
\startstandardmakeup
Copyright
\stopstandardmakeup
\completecontent
\stopfrontmatter
This produced "*Title pageCopyright*" as text without any markup, which
makes the EPUB output a bit difficult to parse. I thought the software
should output something like:
<div class="frontmatter">
<div id="standardmakeup1" class="standardmakeup">Title page</div>
<div id="standardmakeup2" class="standardmakeup">Copyright</div>
<div class="contents"><!-- etc... --></div>
</div>
This way the title and copyright pages can be styled independently.
Kindest regards.
[-- Attachment #1.2: Type: text/html, Size: 3341 bytes --]
[-- 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:[~2013-09-05 16:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 1:19 Thangalin
2013-09-04 9:20 ` Hans Hagen
2013-09-04 17:55 ` Thangalin
2013-09-05 13:55 ` Hans Hagen
2013-09-12 14:32 ` Alan BRASLAU
2013-09-05 16:38 ` Hans Hagen
2013-09-05 16:57 ` Thangalin [this message]
2013-09-05 17:57 ` Khaled Hosny
2013-09-05 18:22 ` Hans Hagen
2013-09-05 17:22 ` Aditya Mahajan
2013-09-05 18:21 ` Hans Hagen
2013-09-05 18:11 ` honyk
[not found] ` <00b501ceaa63$61805e50$24811af0$@tosovsky@email.cz>
2013-09-05 18:20 ` Aditya Mahajan
2013-09-05 18:24 ` Hans Hagen
2013-09-05 19:54 ` Mica Semrick
2013-09-05 21:15 ` Michael Hallgren
2013-09-05 22:00 ` Thangalin
2013-09-06 16:09 ` Hans Hagen
2013-09-06 16:36 ` Mica Semrick
2013-09-06 20:20 ` Thangalin
2013-09-06 21:22 ` Thangalin
2013-09-06 21:27 ` Aditya Mahajan
2013-09-07 12:07 ` Hans Hagen
2013-09-07 18:31 ` Thangalin
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='CAANrE7o=L7b4+s6Op+5o=bHvbySuok_jnuMbTNfTi8unOUazTA@mail.gmail.com' \
--to=thangalin@gmail.com \
--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).