From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/66134 Path: news.gmane.org!not-for-mail From: Mica Semrick Newsgroups: gmane.comp.tex.context Subject: Re: EPUB workflow from ConTeXt source? Date: Thu, 17 Feb 2011 18:43:43 -0800 Message-ID: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0111260909==" X-Trace: dough.gmane.org 1297997071 7676 80.91.229.12 (18 Feb 2011 02:44:31 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 18 Feb 2011 02:44:31 +0000 (UTC) To: ntg-context@ntg.nl Original-X-From: ntg-context-bounces@ntg.nl Fri Feb 18 03:44:27 2011 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PqGKY-0005oX-TL for gctc-ntg-context-518@m.gmane.org; Fri, 18 Feb 2011 03:44:27 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 6DE3BCAA1D; Fri, 18 Feb 2011 03:44:25 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lc-eP9uTo7aX; Fri, 18 Feb 2011 03:44:09 +0100 (CET) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 626FBCA9FC; Fri, 18 Feb 2011 03:44:09 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 2AC13CA9FC for ; Fri, 18 Feb 2011 03:44:08 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Sbwvj2+usKIC for ; Fri, 18 Feb 2011 03:43:45 +0100 (CET) Original-Received: from filter3-til.mf.surf.net (filter3-til.mf.surf.net [194.171.167.219]) by balder.ntg.nl (Postfix) with ESMTP id 5BE8DC9A7C for ; Fri, 18 Feb 2011 03:43:45 +0100 (CET) Original-Received: from mail-wy0-f169.google.com (mail-wy0-f169.google.com [74.125.82.169]) by filter3-til.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p1I2hi2D008066 for ; Fri, 18 Feb 2011 03:43:44 +0100 Original-Received: by wyj26 with SMTP id 26so3255863wyj.14 for ; Thu, 17 Feb 2011 18:43:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Vk82/hfz6y6CdQ+1gTAEBH6U9cP4/PCgBCpZHdytjLM=; b=epvSNhd25EbadOcmIYc0dyxszUH81lFou7TGhMRAS83chG0yLmkm/18gFBKkJCv2lr rIJzBr03fFnzTAX0Lta+OKpJhp1UhzeA0VFLoeU3SyuoeQTu60F+y/n6uvs2T7CkpSt+ tVpuE0u26qOK9fee89jEFRuPYKb+HEu7mT7rw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=wxjBzN9hszVh8Elm5XkW2pgQhnxt7LnxtRATkFr5qxWNQf7d0q3OaKeLadFJdEhaNu JxWn5AtqA9cLootxcp5c3hKdRmTeXYTko1NnTssqV8WMaTlcisxlVEjG+RbLdCKwcPlv 0MfjKbk1yhPZHcZ+ZHSujuB5SDbmvxhPwxe1k= Original-Received: by 10.216.178.138 with SMTP id f10mr120814wem.98.1297997023846; Thu, 17 Feb 2011 18:43:43 -0800 (PST) Original-Received: by 10.216.188.135 with HTTP; Thu, 17 Feb 2011 18:43:43 -0800 (PST) X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=74.125.82.169; country=US; region=CA; city=Mountain View; postalcode=94043; latitude=37.4192; longitude=-122.0574; metrocode=807; areacode=650; http://maps.google.com/maps?q=37.4192,-122.0574&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 0eE9eHIdj - 2b2995af4870 - 20110218 X-Scanned-By: CanIt (www . roaringpenguin . com) on 194.171.167.219 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:66134 Archived-At: --===============0111260909== Content-Type: multipart/alternative; boundary=00163642664586a263049c857b06 --00163642664586a263049c857b06 Content-Type: text/plain; charset=ISO-8859-1 Have you considered authoring in something besides context? Say TEI XML or Docbook, or even markdown (if possible)? If markdown is suitable, then you can end up with both epub and context at the end. Or if using TEI or docbook, you can write a map file (something I have been trying to do) and typeset the xml file directly with context. I'm always happier knowing that I can get as many different output types from a single source as possible. BR, Mica > Message: 8 > Date: Thu, 17 Feb 2011 01:10:42 -0700 > From: Daniel Lyons > To: mailing list for ConTeXt users > Subject: Re: [NTG-context] EPUB workflow from ConTeXt source? > Message-ID: > Content-Type: text/plain; charset=windows-1252 > > > On Feb 17, 2011, at 12:59 AM, Hans Hagen wrote: > > > On 17-2-2011 8:14, Gerben Wierda wrote: > >> On 16 Feb 2011, at 17:47, Wolfgang Schuster wrote: > >> > >>> > >>> Am 16.02.2011 um 17:42 schrieb Gerben.Wierda@rna.nl: > >>> > >>>> I'd like to keep working in one format so I was wondering if there is > a > >>>> ConTeXt based workflow/setup that can produce EPUB (next to normal > PDF)? > >>> > >>> With MkIV you can get a xml version of document with > \setupbackend[export=yes]. > >> > >> But that XML is not ePUB's XML, I assume. > > > > no, but one can of course convert one kind of xml into another > > > > for epub one has to provice css etc anyway (and epub is not much more > than packaged html + css) > > This would also be useful to me. In my experience, the unpleasant part of > generating ePub is making correctly formatted manifests and putting them in > the right places inside the right kinds of zip files. If ConTeXt could do > this for me, it would certainly make life easier. On the other hand, it may > not be appropriate to bother because there are other tools that will convert > HTML to ePub for you and make the manifests (Calibre, for example). > > I consider CSS intractable so that's not something I would worry about > ConTeXt generating for me, if it were on the table. > > > going the other way around, processing an epub file also demands some > handywork as the source code is not by definition well structured > > > ePub is definitely structured. I would say too structured, since it makes > you provide both a ToC manifest and a navigation manifest that necessarily > must include almost identical information ;) Of course, depending on a > simplified browser for your document viewing and having lots of secret > failover modes to handle poorly formatted documents makes the structure less > meaningful than it ought to be. > > You are free to break your document into as many HTML chunks as you wish, > but you are limited to fairly prosaic HTML and CSS. I'm of the impression > the HTML documents generally map onto chapters so as not to distress the > hardware's memory constraints too much. > > Overall, ePub and Kindle's format strike me as too much and too little > respectively. I should be able to change the font and the formatting, but I > definitely consider HTML + CSS is too much complexity. > > ? > Daniel Lyons > > > > ------------------------------ > > --00163642664586a263049c857b06 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Have you considered authoring in something besides context? Say TEI XML or = Docbook, or even markdown (if possible)? If markdown is suitable, then you = can end up with both epub and context at the end. Or if using TEI or docboo= k, you can write a map file (something I have been trying to do) and typese= t the xml file directly with context. I'm always happier knowing that I= can get as many different output types from a single source as possible.= =A0

BR,
Mica


Message: 8
Date: Thu, 17 Feb 2011 01:10:42 -0700
From: Daniel Lyons <fusion@sto= rytotell.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-context] EPUB workflow from ConTeXt source?
Message-ID: <D7225CF0-F6CF-485F-BE01-C8A254EFCA93@storytotell.org> Content-Type: text/plain; charset=3Dwindows-1252


On Feb 17, 2011, at 12:59 AM, Hans Hagen wrote:

> On 17-2-2011 8:14, Gerben Wierda wrote:
>> On 16 Feb 2011, at 17:47, Wolfgang Schuster wrote:
>>
>>>
>>> Am 16.02.2011 um 17:42 schrieb Gerben.Wierda@rna.nl:
>>>
>>>> I'd like to keep working in one format so I was wonder= ing if there is a
>>>> ConTeXt based workflow/setup that can produce EPUB (next t= o normal PDF)?
>>>
>>> With MkIV you can get a xml version of document with \setupbac= kend[export=3Dyes].
>>
>> But that XML is not ePUB's XML, I assume.
>
> no, but one can of course convert one kind of xml into another
>
> for epub one has to provice css etc anyway (and epub is not much more = than packaged html + css)

This would also be useful to me. In my experience, the unpleasant part of g= enerating ePub is making correctly formatted manifests and putting them in = the right places inside the right kinds of zip files. If ConTeXt could do t= his for me, it would certainly make life easier. On the other hand, it may = not be appropriate to bother because there are other tools that will conver= t HTML to ePub for you and make the manifests (Calibre, for example).

I consider CSS intractable so that's not something I would worry about = ConTeXt generating for me, if it were on the table.

> going the other way around, processing an epub file also demands some = handywork as the source code is not by definition well structured


ePub is definitely structured. I would say too structured, since it makes y= ou provide both a ToC manifest and a navigation manifest that necessarily m= ust include almost identical information ;) Of course, depending on a simpl= ified browser for your document viewing and having lots of secret failover = modes to handle poorly formatted documents makes the structure less meaning= ful than it ought to be.

You are free to break your document into as many HTML chunks as you wish, b= ut you are limited to fairly prosaic HTML and CSS. I'm of the impressio= n the HTML documents generally map onto chapters so as not to distress the = hardware's memory constraints too much.

Overall, ePub and Kindle's format strike me as too much and too little = respectively. I should be able to change the font and the formatting, but I= definitely consider HTML + CSS is too much complexity.

?
Daniel Lyons



------------------------------


--00163642664586a263049c857b06-- --===============0111260909== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 ___________________________________________________________________________________ --===============0111260909==--