From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/90271 Path: news.gmane.org!not-for-mail From: Keith Schultz Newsgroups: gmane.comp.tex.context Subject: Re: Epub format Was: Re: Context to epub: itemize Date: Tue, 17 Feb 2015 22:01:38 +0100 Message-ID: References: <26301630-C723-4870-A56D-345219EB4E99@axelkielhorn.de> <54E23D2D.7050306@wxs.nl> <8BA925AF-1101-4DA2-84FC-D4747E47C5AB@web.de> <54E3A18B.1030901@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/mixed; boundary="===============1892240309==" X-Trace: ger.gmane.org 1424206978 28139 80.91.229.3 (17 Feb 2015 21:02:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Feb 2015 21:02:58 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Tue Feb 17 22:02:43 2015 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([5.39.185.229]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YNpI1-0006Zh-9j for gctc-ntg-context-518@m.gmane.org; Tue, 17 Feb 2015 22:02:41 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id A9D6C10234 for ; Tue, 17 Feb 2015 22:02:40 +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 1whF0oaIm89S for ; Tue, 17 Feb 2015 22:02:39 +0100 (CET) Original-Received: from balder.ntg.nl (localhost [IPv6:::1]) by balder.ntg.nl (Postfix) with ESMTP id 1FC52101FC for ; Tue, 17 Feb 2015 22:02:12 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 9A504101FD for ; Tue, 17 Feb 2015 22:02:07 +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 mOQmMe8O2XQC for ; Tue, 17 Feb 2015 22:02:06 +0100 (CET) Original-Received: from filter3-utr.mf.surf.net (filter3-utr.mf.surf.net [195.169.124.154]) by balder.ntg.nl (Postfix) with ESMTP id 4E882101FC for ; Tue, 17 Feb 2015 22:02:05 +0100 (CET) Original-Received: from st11p06mm-asmtp001.mac.com (st11p06mm-asmtp001.mac.com [17.172.124.249]) by filter3-utr.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id t1HL212M020486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 17 Feb 2015 22:02:04 +0100 Original-Received: from [10.0.0.106] (p5DCCEBE7.dip0.t-ipconnect.de [93.204.235.231]) by st11p06mm-asmtp001.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NJX005BGP2S9W00@st11p06mm-asmtp001.mac.com> for ntg-context@ntg.nl; Tue, 17 Feb 2015 21:01:50 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-02-17_07:2015-02-17,2015-02-17,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502170202 In-reply-to: <54E3A18B.1030901@wxs.nl> X-Mailer: Apple Mail (2.2070.6) X-Bayes-Prob: 0.0001 (Score 0, tokens from: ntg-context@ntg.nl, base:default, @@RPTN) X-CanIt-Geo: ip=17.172.124.249; country=US; region=California; city=Cupertino; latitude=37.3230; longitude=-122.0322; http://maps.google.com/maps?q=37.3230,-122.0322&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 08NRx24NW - 085918415edf - 20150217 (trained as not-spam) Received-SPF: pass (filter3-utr.mf.surf.net: domain of keithjschultz@icloud.com designates 17.172.124.249 as permitted sender) receiver=filter3-utr.mf.surf.net; client-ip=17.172.124.249; envelope-from=; helo=st11p06mm-asmtp001.mac.com; identity=mailfrom X-Scanned-By: CanIt (www . roaringpenguin . com) on 195.169.124.154 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:90271 Archived-At: --===============1892240309== Content-type: multipart/alternative; boundary="Apple-Mail=_833FAAFB-9959-4E17-A716-F61532C81B91" --Apple-Mail=_833FAAFB-9959-4E17-A716-F61532C81B91 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Am 17.02.2015 um 21:16 schrieb Hans Hagen : >=20 > On 2/17/2015 8:24 AM, Keith J. Schultz wrote: >> Hi Axel, All, >>=20 >>=20 [snip, snip] >> IMHO : ConTeXt should not output XHMTL for epub, but HMTL5. >> Yes, yes, I know XHMTL is part of HMTL5. >=20 > And html 5 is just html with some extras (and assuming javascript i = guess) ... marketing. The html 5 standard is far more. For one is makes flash, java and more = obsolete. Far more than a marketing gag!=20 >=20 >> Another question for me is if ConTeXt should also output code for >> the iBooks epub format, (Basicaly epub, but some extras). >=20 > Isn't a book supposed to be independent and kind of portable + long = term visible? So no way that a context epub will be specific for a = device. (I probably can't even get it on / test it on my outdated ipad 1 = anyway.) I was thinking more along the line of the spine. >=20 >> There are thing you can do in/with ConTeXt that would work with = iBooks >> that do not in =E2=80=9Eordinary=E2=80=9C epub books. >>=20 >> Then, there is the Kindle format one might want to consider! >=20 > Another lock-in device. >=20 >> Another, question which needs investigation is if the ConTeXt output = for >> epub, >> also, implementing the fallbacks for missing features which is = required? >=20 > 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 have not investigated how it handles dimensions, widths, font = sizes, spacing, etc. These are important in order to create output that adjust proper = to the devices capabilities.=20 One should avoid absolute values. Of course if we want to emulate the printed output then we could = simply create a pdf or very page as pdf and put in an epub wrapper. Not asking for anything, just mentioning it. =09 reagrds Keith. --Apple-Mail=_833FAAFB-9959-4E17-A716-F61532C81B91 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Am 17.02.2015 um 21:16 schrieb Hans Hagen <pragma@wxs.nl>:

On 2/17/2015 8:24 AM, Keith J. Schultz = wrote:
Hi Axel, All,


[snip, snip]
IMHO : ConTeXt should not output XHMTL for epub, but = HMTL5.
Yes, yes, I know XHMTL is part of HMTL5.

And html 5 is just html = with some extras (and assuming javascript i guess) ... = marketing.
The html 5 standard is far more. For one = is makes flash, java and more obsolete. Far more than a marketing = gag! 

Another question for me is if ConTeXt should also = output code for
the iBooks epub format, (Basicaly epub, = but some extras).

Isn't a book supposed to be independent and kind = of portable + long term visible? So no way that a context epub will be = specific for a device. (I probably can't even get it on / test it on my = outdated ipad 1 anyway.)
I was thinking more along the line = of the spine.

There are thing you can do in/with ConTeXt that would = work with iBooks
that do not in =E2=80=9Eordinary=E2=80=9C = epub books.

Then, there is the Kindle = format one might want to consider!

Another lock-in device.

Another, question which = needs investigation is if the ConTeXt output for
epub,
also, implementing the fallbacks for missing features which = is required?

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 have not investigated how it = handles dimensions, widths, font sizes, spacing, etc.
These are = important in order to create output that adjust proper to = the
        devices = capabilities. 
One should avoid absolute = values.

Of course if we want to emulate = the printed output then we could simply
create a = pdf or very page as pdf and put in an epub wrapper.


Not = asking for anything, just mentioning it.
=
reagrds
Keith.

= --Apple-Mail=_833FAAFB-9959-4E17-A716-F61532C81B91-- --===============1892240309== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============1892240309==--