ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Epub format Was: Re: Context to epub: itemize
Date: Wed, 18 Feb 2015 15:10:27 +0100	[thread overview]
Message-ID: <E705529E-F58A-4435-96D6-51D349386773@web.de> (raw)
In-Reply-To: <BEA485C8-0246-4070-90D0-BDF5E97CC82C@fiee.net>

Hi Hraban,

Good to know. I will investigate at another time and give feed back.
I am in the middle of moving, so I do not have much time.

We ought to think of making a export specific to epub in the long run!
 
regards
	Keith.
> Am 18.02.2015 um 09:14 schrieb Henning Hraban Ramm <texml@fiee.net>:
> 
> 
> Am 2015-02-18 um 04:37 schrieb Aditya Mahajan <adityam@umich.edu>:
> 
>> On Tue, 17 Feb 2015, Hans Hagen wrote:
>> 
>>> Context outputs three varants: regular xml, xhtml, and stupified xhtml with div/class tagging. The last one is supposed to work on all devices as it doesn't demands anything beyond css.
>> 
>> The XML generated by ConTeXt is very well structured. So, an option is to simply provide XLST stylesheets that transform ConTeXT-XML to XHTML/HTML5/whatever.
>> 
>> Such XLST transformation will be better than have ConTeXt chase a moving target.
> 
> See e.g. http://wiki.contextgarden.net/Epub_Sample
> 
> I’ll try to update the pages about ConTeXt’s current export soon, since I have a new book in the pipeline.
> 
> Greetlings, Hraban
> ---
> http://www.fiee.net
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2015-02-18 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 16:17 Axel Kielhorn
2015-02-16 18:55 ` Hans Hagen
2015-02-17  6:11   ` Axel Kielhorn
2015-02-17  7:24     ` Epub format Was: " Keith J. Schultz
2015-02-17 20:16       ` Hans Hagen
2015-02-17 21:01         ` Keith Schultz
2015-02-18 16:54           ` Hans Hagen
2015-02-19  9:27             ` Keith Schultz
2015-02-17 22:37         ` Aditya Mahajan
2015-02-18  8:14           ` Henning Hraban Ramm
2015-02-18 14:10             ` Keith J. Schultz [this message]
2015-02-18 14:21               ` Henning Hraban Ramm
2015-02-18 16:44               ` Hans Hagen
2015-02-18 16:55           ` Hans Hagen

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=E705529E-F58A-4435-96D6-51D349386773@web.de \
    --to=keithjschultz@web.de \
    --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).