From: William Adams <will.adams@frycomm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX as an eBook engine?
Date: Thu, 3 Dec 2009 08:52:05 -0500 [thread overview]
Message-ID: <7F04309D-F522-42B5-9F71-3E2BAFFEC8BD@frycomm.com> (raw)
In-Reply-To: <fe8d59da0912030522t10e3be4awc79df64719db7e0a@mail.gmail.com>
On Dec 3, 2009, at 8:22 AM, luigi scarso wrote:
> Not really.
My apologies, lost the thread of the discussion. I agree w/ this.
> With mkiv you can typeset xml files as pdf,
> so you can also (using modes) convert it to xhtml (we have lua now).
> Writing a css is not a problem, and you can also manage fonts --
> after all
> you know them because you need for pdf . Other infos are trivial.
>
> Following this route you can also make an (x)html for a WOFF enable
> browser
> like firefox 2.6 beta -- it's almost the same of epub, after all
> Cfr
> people.mozilla.com/~jkew/woff/woff-spec-latest.html
>
> Of course none can say that epub is like pdf from a typographical
> point of view
> but for low energy devices can be better epub than pdf.
I'll grant that .epub can be more flexible and more appropriate, but
one has to keep in mind that one is giving up quite a bit of
typographical quality, and that one is at the mercy of the h&j of the
viewing program and I've yet to see one which puts more than a
minimal / brain-dead / greedy --- set as much as will fit on the
current line and then break to the next algorithm in.
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:[~2009-12-03 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60DB6B0E-C759-43E0-A13F-54AB7D0D5560@wideopenwest.com>
2009-12-02 17:03 ` Otared Kavian
2009-12-02 18:19 ` Hans Hagen
2009-12-03 8:17 ` Henning Hraban Ramm
2009-12-03 8:58 ` Hans Hagen
2009-12-03 9:12 ` luigi scarso
2009-12-03 13:10 ` William Adams
2009-12-03 13:22 ` luigi scarso
2009-12-03 13:52 ` William Adams [this message]
2009-12-03 14:48 ` luigi scarso
2009-12-05 14:58 ` Idris Samawi Hamid ادريس سماوي حامد
2009-12-06 20:30 ` Henning Hraban Ramm
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=7F04309D-F522-42B5-9F71-3E2BAFFEC8BD@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).