ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX as an eBook engine?
Date: Thu, 3 Dec 2009 15:48:43 +0100	[thread overview]
Message-ID: <fe8d59da0912030648r517daa7fx34c7f4a4f103390f@mail.gmail.com> (raw)
In-Reply-To: <7F04309D-F522-42B5-9F71-3E2BAFFEC8BD@frycomm.com>

On Thu, Dec 3, 2009 at 2:52 PM, William Adams <will.adams@frycomm.com> wrote:
> 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.
It's true of course.
anyway  have you seen
http://people.mozilla.com/~jkew/woff/woff-spec-latest.html
http://people.mozilla.com/~jkew/woff/
?

I was at guit meeting this year, and  Kaveh too, and I have seen his
device with TeX.
It's really cool: it's not a simple dvi reader, it's a TeX
implementation+dvi reader
so one can exchange tex snippets with similar devices
Next release will use xetex.

I have some experience to port pdf in similar
devices too (it was 3years ago, too much time ago, really)
and in the end I'm convinced that (x)html is still the first choice.


-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2009-12-03 14:48 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
2009-12-03 14:48               ` luigi scarso [this message]
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=fe8d59da0912030648r517daa7fx34c7f4a4f103390f@mail.gmail.com \
    --to=luigi.scarso@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).