From: William Adams <will.adams@frycomm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Style file for iPad?
Date: Wed, 7 Mar 2012 11:30:15 -0500 [thread overview]
Message-ID: <5489AF63-D5B2-4DD1-9836-77A3906D207F@frycomm.com> (raw)
In-Reply-To: <nvitacolonna-04A8E9.09343907032012@news.gmane.org>
On Mar 7, 2012, at 3:34 AM, Nicola wrote:
> It's worse than pre-TeX printed books. Which makes me wonder: is anyone in the
> world addressing this? Are there people in the TeX community involved in the
> standardization processes (say, Epub3, but also the various W3C specifications),
> who could push forward ideas from TeX, like minimum requirements for the
> algorithms that rendering engines should use? These questions (together with
> sighs) arise every time I see a web page especially with mathematical notation…
The problem is, since the rendering is based on HTML, people just grab a web browser framework and build on that to make an ebook viewer.
Here's a post I wrote up once comparing a specific ePub display on a specific viewing program w/ a hand-tweaked Plain TeX version:
http://www.mobileread.com/forums/showpost.php?p=1371218&postcount=7
> those who're curious may find it educational to compare my .pdf w/ this ePub version to see the sort of typographic infelicities which even in the best ePub version can't be controlled for ---
> - one word last lines
> - # of lines on a page constantly changing to prevent widows / orphans
> - overly loose line on the middle of pg. 20
> - 3 word stack on pg. 21 (meditation/Meditation)
> - 2 word stack on pg. 32 (black)
> - 2 word stack on pg. 37 (the) Twice!
> - six word river on pg. 40 (the/their/the/the/its/we)
> - 2 word stacks on pg. 40 (a & We)
> - 3 word stack on pg. 46 (the/the/The)
> - 2 word stack on pg. 47 (a)
> - awkward break at the bottom of the first page of Chapter VII where the poem is referred to, but appears on the following page
> (when viewed in Sony's ebook viewing program)). In the .pdf I believe there were only one or two places where I let two word stacks stand (because they were intractable) --- will have to try again using xetex and margin protrusion and character expansion (I'd used DEK's macro for hanging punctuation from _The TeXbook_).
William
--
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.
___________________________________________________________________________________
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:[~2012-03-07 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:03 Alasdair McAndrew
2012-03-06 11:36 ` Philipp A.
2012-03-06 11:40 ` Alasdair McAndrew
2012-03-06 13:40 ` Khaled Hosny
2012-03-07 8:34 ` Nicola
2012-03-07 16:30 ` William Adams [this message]
2012-03-07 22:35 ` Alasdair McAndrew
2012-03-06 12:47 ` Hans Hagen
2012-03-06 13:48 ` Aditya Mahajan
2012-03-06 14:14 ` Hans Hagen
2012-03-06 13:41 ` Aditya Mahajan
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=5489AF63-D5B2-4DD1-9836-77A3906D207F@frycomm.com \
--to=will.adams@frycomm.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).