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 10:12:12 +0100	[thread overview]
Message-ID: <fe8d59da0912030112q760b939fj4012de4c388d3369@mail.gmail.com> (raw)
In-Reply-To: <4B177DAC.80408@wxs.nl>

On Thu, Dec 3, 2009 at 9:58 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Henning Hraban Ramm wrote:
>>
>> Am 2009-12-02 um 18:03 schrieb Otared Kavian:
>>
>>> For those on the list who didn't see this thread on XeTeX mailing list:
>>> How about ConTeXt and mkiv?
>>
>> Hm, your subject is a bit misleading - I thought you wanted to *create
>> eBooks* using TeX. That would be much more useful...
>> Even if some eBook devices can display PDF, AFAIK we still cannot create
>> the re-flowable variant (needs a XML stream, see other discussions about
>> tagged PDF or PDF/X).
>>
>> In one of the latest c't (German computer magazine) there was a nice
>> article on creating eBooks in Epub format (HTML based). Even if I don't
>> intend to buy an eBook device, it made me think again about using another
>> input language than TeX to create HTML, ConTeXt and whatever from one
>> source. Knut Lickert recently gave a talk on "Creole for LaTeX" (Creole is
>> an unified Wiki markup syntax), I'm still planning to use ReStructuredText
>> (Python's documentation syntax) - note to self: finally adapt that LaTeX
>> output filter to ConTeXt!
>
> Processing epub is rather trivial. On my machine I have a sample style and
> processign boils down to:
>
> context --ctx=x-epub --autopdf dickens-a-tale-of-two-cities.epub
>
> However, the main reason for not posting the style is that I have not much
> reason currently to work on it. Also, as epub is effectively just packaged
> html, one ends up with styles for each specific book ... you just don't want
> to know what mess is hidden in those epub files (for example i ran into
> using h2 for the chapter numbers and h3 for the chapter title).
>
Maybe epub as backend is a more interesting  idea:
given (some kind of gentle )  tex file one can produce an epub file as  result.



-- 
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  9:12 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 [this message]
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
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=fe8d59da0912030112q760b939fj4012de4c388d3369@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).