IETF Logo Mail Archive

Re: [rfc-i] Epub format tools

"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Wed, 30 November 2016 22:57 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 8F83C129BCD for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 30 Nov 2016 14:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, 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 H07XU2mYyDxS for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 30 Nov 2016 14:57:16 -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 A5E05129BCF for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 30 Nov 2016 14:57:07 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5D567B80264; Wed, 30 Nov 2016 14:57:07 -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 79389B80264 for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:57:05 -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 5wtgEhL_nUrD for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:57:04 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 9F3BDB80263 for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:57:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3D4631E5653 for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAjaHpKS0lZz for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:54:58 -0800 (PST)
Received: from Heathers-MacBook-Pro.local (c-50-159-75-65.hsd1.wa.comcast.net [50.159.75.65]) by c8a.amsl.com (Postfix) with ESMTPSA id 13A9F1E55C3 for <rfc-interest@rfc-editor.org>; Wed, 30 Nov 2016 14:54:58 -0800 (PST)
To: rfc-interest@rfc-editor.org
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> <C5DBE7BA-D5B4-4890-BCEF-2C65747F1A6E@cursive.net> <CAMm+Lwh43zc-s86HQ4CmqN2m3X7EbTwy1_NL7vtOQu4Kd9kvHw@mail.gmail.com>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <8d614a7d-5dd7-e7bf-b0b8-235f9a202d95@rfc-editor.org>
Date: Wed, 30 Nov 2016 14:57:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwh43zc-s86HQ4CmqN2m3X7EbTwy1_NL7vtOQu4Kd9kvHw@mail.gmail.com>
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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

On 11/30/16 12:34 PM, Phillip Hallam-Baker wrote:
> 
> 
> On Wed, Nov 30, 2016 at 3:25 PM, Joe Hildebrand <hildjj@cursive.net
> <mailto:hildjj@cursive.net>> wrote:
> 
>     > On Nov 22, 2016, at 9:54 AM, Phillip Hallam-Baker <phill@hallambaker.com <mailto:phill@hallambaker.com>> wrote:
>     >
>     > ​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.
> 
>     The RFP is out for bid, and we expect a vendor selection imminently.
>     Starting over with any other (even existing) toolset will certainly
>     set us back by at least 2 years, perhaps more.
> 
>     -1 to starting over from scratch at this point.
> 
> ​
> I never said 'start from scratch'.
> 
> There is a lot of stuff there that we could take. In particular a tool
> chain that already does much of what is needed.
> 
> It is also possible to move in the opposite direction. I already have a
> tool chain for managing RFC format from Word document or Markdown
> source. Adding ePub format to the tool is not a lot of work and gets me
> a vastly larger audience.​
>  
> 

EPUB was one of the formats I had hoped we would offer as one of the
outputs, but I have not found anyone willing to write the requirements
spec for it. I'm still open to the idea of having EPUB as an output
format at some point.

As for whether it's accepted as an Internet Draft input format, I
hesitate to add more input formats if we can avoid them, at least in
terms of what the RFC Editor accepts. I am trying to control cost and
complexity on our end, and limiting what is sent on to the editors to
just TXT and XML is definitely easier for us to manage.

-Heather

_______________________________________________
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