ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Keith Schultz <keithjschultz@icloud.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Epub format Was: Re:  Context to epub: itemize
Date: Thu, 19 Feb 2015 10:27:50 +0100	[thread overview]
Message-ID: <355959AF-0637-43E3-A4C6-8F1F22ABA744@icloud.com> (raw)
In-Reply-To: <54E4C3DD.1050904@wxs.nl>

Hi Hans,

I have been playing with the on using LaTeX and later LuaLaTeX
for create epub or ebook. Though I have not got around to.


The idea was to set enviorments, macros and commands that would depending
on a switch that would output the need HTML and epub structure or
call the normal *TeX ones.

In ConTeXt maybe the mode-system could be used.
Like I said I have not investigated deeply, yet.

regards
	Keith.
 
> Am 18.02.2015 um 17:54 schrieb Hans Hagen <pragma@wxs.nl>:
> 
> On 2/17/2015 10:01 PM, Keith Schultz 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.
>> If that is the case it is not very useful for a decent workflow. There
>> would be to much to
>> tweak to make good looking output.
> 
> i'm not sure what you have in mind but context is a typesetting system and as such cannot produce an epub simply because epub is a blob of xml (html) with a css packages in a zip
> 

___________________________________________________________________________________
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-19  9:27 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 [this message]
2015-02-17 22:37         ` Aditya Mahajan
2015-02-18  8:14           ` Henning Hraban Ramm
2015-02-18 14:10             ` Keith J. Schultz
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=355959AF-0637-43E3-A4C6-8F1F22ABA744@icloud.com \
    --to=keithjschultz@icloud.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).