[xml2rfc] Two issues with new version

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 22 September 2013 05:37 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B2221F9FA2 for <xml2rfc@ietfa.amsl.com>; Sat, 21 Sep 2013 22:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level:
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SS4U+S9bRZZe for <xml2rfc@ietfa.amsl.com>; Sat, 21 Sep 2013 22:37:07 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5950221F9F99 for <xml2rfc@ietf.org>; Sat, 21 Sep 2013 22:37:07 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so2296582pab.13 for <xml2rfc@ietf.org>; Sat, 21 Sep 2013 22:37:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=fXPo0XMJnpyhqr8tCKL4e7bPjmUzasmwQ97ATrOU0/w=; b=prBfYuZk5RbNpAmiX/Xw4oOEsxhlIxGrZuEE9jq5OiJy3QXAxm7Ya7dNnGZ/nK/l6k w5MLZSitTnYP8vVXNJYniFZwk8B11KJe5u/hCJ8FsjCOQybHrGJIPn27qw3/FhBJyX4s TiUNFxnIbNTNpgtYc7Y68D+0If+hHMQJNSbbPSab5GgLKf1ClnEX7nHzlOUtovpl/qO9 nSgjm7g2gwMoBk7D1MGI2W/0mqf62WWZfImCjhIbMYP0Xhsbat1uuelEkiXchxAp0xeB QX3vm9gHAIgDbtA6DicDE+kxkUGFOJPjvmQDjKZp3s20bW18UrRg3jswicxjsOCwOGZS XLWQ==
X-Received: by 10.66.162.167 with SMTP id yb7mr18082770pab.16.1379828227146; Sat, 21 Sep 2013 22:37:07 -0700 (PDT)
Received: from [192.168.178.20] (36.201.69.111.dynamic.snap.net.nz. [111.69.201.36]) by mx.google.com with ESMTPSA id wd6sm29361552pab.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Sep 2013 22:37:06 -0700 (PDT)
Message-ID: <523E81FF.4070904@gmail.com>
Date: Sun, 22 Sep 2013 17:37:03 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: xml2rfc <xml2rfc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [xml2rfc] Two issues with new version
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Sep 2013 05:37:08 -0000

I had a couple of issues with the "March 2013" version (using the
Web service at http://xml.resource.org/) while processing
draft-carpenter-prismatic-reflections-00.xml.

(The posted I-D was processed with http://xml.resource.org/old.html)

ISSUE 1:

In the main text, I included some <erefs> such as

<eref target="https://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html"/>

Generating an HTML file, there's no problem: this simply
generates a link, as expected.

BUT, generating a TXT file, each <eref> appears as [1], [2] etc (despite
using symrefs) but there is no [1], [2] to cite. The old version of XML2RFC,
as expected, just plants the URL in the text.

ISSUE 2:

To work around Issue 1 in a hurry, I simply replaced the
various <eref>s by the bare URL. Again, with the new version
of XML2RFC, HTML output is fine.

BUT, generating a TXT file, the output file is blank, with no
error message.

On further checking today, this problem is quite bizarre. At
first sight it's caused by one specific URL, the one quoted above:

https://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html

but in fact any URL at that point seems to generate the problem.

I can "fix" the problem by deleting about 45 characters from
later in the same <section>, so I think there is some sort
of buffer overflow involved - but no error messages, just
an empty output file.

I will supply the guilty XML file to anyone interested.

     Brian




Regards
   Brian Carpenter