Re: [rfc-i] Rendering of xml2rfc v3 fragments

Marc Petit-Huguenin <petithug@acm.org> Tue, 24 January 2017 13:43 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 921DB129855 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 24 Jan 2017 05:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.4
X-Spam-Level:
X-Spam-Status: No, score=-7.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, 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 Rv4JE7cEsSOi for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 24 Jan 2017 05:43:55 -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 719681295F1 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 24 Jan 2017 05:43:55 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 210FEB81049; Tue, 24 Jan 2017 05:43:55 -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 235B3B81049 for <rfc-interest@rfc-editor.org>; Tue, 24 Jan 2017 05:43:53 -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 okVfDbz-l-SN for <rfc-interest@rfc-editor.org>; Tue, 24 Jan 2017 05:43:51 -0800 (PST)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) by rfc-editor.org (Postfix) with ESMTPS id 81987B81048 for <rfc-interest@rfc-editor.org>; Tue, 24 Jan 2017 05:43:51 -0800 (PST)
Received: from [IPv6:2601:648:8300:77bf:9800:9f03:696c:44fa] (unknown [IPv6:2601:648:8300:77bf:9800:9f03:696c:44fa]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id D3982AE7A5 for <rfc-interest@rfc-editor.org>; Tue, 24 Jan 2017 14:43:46 +0100 (CET)
To: rfc-interest@rfc-editor.org
References: <16e452bf-7c97-5e6b-2206-7f59ebd3ee11@acm.org>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <77e1e4b4-ca41-3322-7c0f-dfde915dfee1@acm.org>
Date: Tue, 24 Jan 2017 05:43:44 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0
MIME-Version: 1.0
In-Reply-To: <16e452bf-7c97-5e6b-2206-7f59ebd3ee11@acm.org>
Subject: Re: [rfc-i] Rendering of xml2rfc v3 fragments
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: multipart/mixed; boundary="===============5816946568139682487=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

On 01/08/2017 04:42 PM, Marc Petit-Huguenin wrote:
> Is there any plan for the various renderers for the xml2rfc v3 (text, html, pdf) to be able to generate output for xml fragments, as opposed to a whole document?
> 
> I see some use cases for that, for example to insert normative text into a source program.
> 
> Thanks.
> 

Did not receive any answer on that, but I have another question about the xml2rfc v3 program:  

Will there a way to smoothly integrate a new renderer, like a plugin?  I am trying to add a new writer in xml2rfc v2, and that means modifications in the code that require to ship the whole code, instead of just the code for the new output format.  Having the possibility of plugins with xml2rfc v3 would make that easier.

Thanks.

-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug

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