IETF Logo Mail Archive

Re: [rfc-i] Epub format tools

Julian Reschke <julian.reschke@gmx.de> Tue, 22 November 2016 17:13 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C41B1295F6 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 22 Nov 2016 09:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.498
X-Spam-Level:
X-Spam-Status: No, score=-5.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rh-TpOAmgegL for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 22 Nov 2016 09:13:53 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F4D61295E8 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 22 Nov 2016 09:13:53 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DDE2CB8038A; Tue, 22 Nov 2016 09:13:52 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9F6B3B8038A for <rfc-interest@rfc-editor.org>; Tue, 22 Nov 2016 09:13:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdflvwz0aT7c for <rfc-interest@rfc-editor.org>; Tue, 22 Nov 2016 09:13:50 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by rfc-editor.org (Postfix) with ESMTPS id C2EB3B80387 for <rfc-interest@rfc-editor.org>; Tue, 22 Nov 2016 09:13:49 -0800 (PST)
Received: from [192.168.178.20] ([93.217.100.105]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MFLhE-1busdu1YVo-00ELMK; Tue, 22 Nov 2016 18:13:42 +0100
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <CAMm+LwiPYuvnYkGmxt51-osVwGzak6SVvsNrfNOUXMO8LFQ4dw@mail.gmail.com> <7B942896-8F81-4EC0-AB4D-A232FEA5ADC7@att.com> <CAMm+LwgdqVtXQJNSrM1ovPTq5zi_NvddN=-b=WOvXh10fJoo7g@mail.gmail.com> <059a8209-9998-e101-bbab-c8820c75b88e@gmx.de> <CAMm+LwjhiYVfL-gJtVErv=OmiYJvWSdbAq0TBEqT+P25tFjqVQ@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <37d962cc-f82c-7ac2-3d56-2310c8a226c8@gmx.de>
Date: Tue, 22 Nov 2016 18:13:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjhiYVfL-gJtVErv=OmiYJvWSdbAq0TBEqT+P25tFjqVQ@mail.gmail.com>
X-Provags-ID: V03:K0:RbJZR1q+pjBmqCrfkOTnSkd3QLV2Zk7TFhZUk9FzBQJMkXhFVug U1AJuTg1uhfWM8ArhTdqnTnlOXNKps42AWAX73fGfcGRkjBVsxwvdlKKSgE2laiepbdCVGZ ci8oVoqQ3jnLm3gyi7mclfzN0wpYPVQHnCOswy8wULJ51RaV8AeIGeht7nOX7U7AocDmT+U 1j/Oh/0hIY5xtzmd31nDg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:g99462eT0Ug=:5EwXm13KE47/4XaeZ/k60N vpoiYDvVVZHSqxTiifATE8Dj35cae+Bd3Y7np6VJrg7SYnhQgMfJZQRhiW/6zWayd8NTmoId4 Hwo6I+QSkTnL8koe1GjPH18sx7nwkDC5WO20B+ljGaYGuh22VDKOEE4LbHeczC97hmUh4edbN Sbv21Oyl2TeScUBxRUB0DC0lpljVGxKQV5AMBiKyPmyB5BgkECNM2RKj2/YjWsMqLX1FoV66y O/De5oFXfJLsqOoXzL3fm9weTwfx5QzX8q/asJDx/or53/OT1ZrAoZLWTET89ewMAgyj0npVr bsQS/YndR1t2p5CPf3rt8tGhyuNT43SySVNUmPJH2zZRvr9ty608l7x9k3pO9ur/yDGW4V1Gm f8ZuHkYtevM+tu0SU0wZdVAzJh8zw4GjzR/nEpPhPJMbSMyhvsjSN60sBmkRct6qycakzHnpk fh8bBR21mHNHASAbKDfBNNMNejk8s10AZ5L7zGXiFpn2h+AFhxpZklcyGDol4nKu1j3iyFtnG 81GLqGhjKJ9qYE46JoY4K/mALa1u4IV09mZa8+paHfOJeHmN6gTBCIk/9tL7rWF1YBoMQwXtX nFpHxVAx8tr7mr/dee4gXBJWdE9SGndiBOn9vHcqglVgrLyerBZTkF6Q65MuGp79MQTHloleF RXKgXoLptx5WSZIfG2DO19Vv8KsE4dT4lI+PgJMiCQFwmsunTPrdyFLgolGhUxjU1rqJI01nK ZW+fop3RjCNJDr9ydDt48j07K856uO/ViQ8hNLPxyouOo38gTJDCOMvhe9Ony23soVS4kdF5i PxRSN+z
Subject: Re: [rfc-i] Epub format tools
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, "HANSEN, TONY L" <tony@att.com>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

On 2016-11-22 17:54, Phillip Hallam-Baker wrote:
> On Tue, Nov 22, 2016 at 11:27 AM, Julian Reschke <julian.reschke@gmx.de
> <mailto:julian.reschke@gmx.de>> wrote:
>
>     On 2016-11-22 17:22, Phillip Hallam-Baker wrote:
>
>         They seem to have already done all the work on deciding what HTML
>         features to use. And they have a well developed tool chain.
>
>         Why reinvent the wheel?
>
>
>     What problem do you want to solve exactly? Is this an attempt to
>     undo the work on the new RFC format?
>
>     Best regards, Julian
>
>
> ​We don't seem to be getting there very fast. ​At the current rate of
> progress and given the resources currently available, I don't expect to
> be able to use the new format till 2020.

I agree it's too slow. That said, I'm already using big parts of it.

> The epub folk have a fully developed infrastructure supported by a
> mature tool chain that is designed by people with experience of actually
> solving these issues.
>
> When it comes to code, I am utterly ruthless about consigning my own
> code to the bit bucket when there is something better available. And I
> am even more willing to drop other people's.
>
> But in this case, it looks to me as if quite a few of those tools
> already solve gaps in the system. How we organize composite documents
> for upload for example. I don't see any reason for the IETF upload
> format to look any different to the epub format with an XML2RFC document
> in place of the XHTML files.

Ok, so yes, a ZIP file (that's what an epub file is) sounds like a good 
approach.

Best regards, Julian


_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.8.7 | Report a Bug | By Email