From nobody Thu Sep  8 23:58:22 2016
Return-Path: <dev+ietf@seantek.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 ACE5A12B0F7 for <xml2rfc@ietfa.amsl.com>; Thu,  8 Sep 2016 23:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 SJOgYFkUMux6 for <xml2rfc@ietfa.amsl.com>; Thu,  8 Sep 2016 23:58:19 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C96B12B096 for <xml2rfc@ietf.org>; Thu,  8 Sep 2016 23:58:19 -0700 (PDT)
Received: from [192.168.123.110] (unknown [75.83.2.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9EF3050A86 for <xml2rfc@ietf.org>; Fri,  9 Sep 2016 02:58:18 -0400 (EDT)
From: Sean Leonard <dev+ietf@seantek.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <93579AEE-3420-49F2-9D7C-015BEF196648@seantek.com>
Date: Thu, 8 Sep 2016 23:58:17 -0700
To: XML2RFC Interest Group <xml2rfc@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Y-Wx9LbvoWY-BBDnYony9q7psVk>
Subject: [xml2rfc] xml2rfc v2 <artwork src="...">
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Sep 2016 06:58:21 -0000

Hello:

xml2rfc v2 says that <artwork> can have a @src attribute, which is a =
URI. I assume that the base URI is the current URI of the xml2rfc =
document.

What is the proper behavior when an <artwork> has textual data and also =
has the src attribute? Is it a fatal processing error, or does one take =
precedence? RFC 7749 does not say.

Note: The xml2rfc v3 draft says: =E2=80=9CIt is an error to have both a =
"src" attribute and content in the <artwork> (or <sourcecode>) =
element.=E2=80=9D Therefore I would say that v3 treats the condition as =
fatal. The xml2rfc v3 preptool draft suggests that @src is supposed to =
be factored out during the posting/publication process, by including the =
contents directly in the inner XML element, or by using a data: URI.


It appears that the xml2rfc v2 2.5.1 (Python) completely ignores the src =
attribute on <artwork>, as confirmed with both testing and source code =
analysis. It does not even care, so <artwork src=3D=E2=80=9Cfoo.txt"/> =
is treated as <artwork></artwork>, and the presence of both text and =
@src results in just the text being used. I just tried submitting an =
Internet-Draft with an <artwork> with both @src and text, and the upload =
tool took it (I didn=E2=80=99t actually post the draft).

Would this be loosely classified as a =E2=80=9Cbug=E2=80=9D (or missing =
feature), or is this by design?

Sean

PS I am trying to decide if a tool should basically ignore <artwork> =
@src, error out, or do something else.=


From nobody Fri Sep  9 00:27:51 2016
Return-Path: <julian.reschke@gmx.de>
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 04AFE12B09B for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 00:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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 9oAFUNavwPDJ for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 00:27:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C074012B075 for <xml2rfc@ietf.org>; Fri,  9 Sep 2016 00:27:47 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.64.86]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MVayZ-1bY0Wt1y2R-00Z0FR; Fri, 09 Sep 2016 09:27:36 +0200
To: Sean Leonard <dev+ietf@seantek.com>, XML2RFC Interest Group <xml2rfc@ietf.org>
References: <93579AEE-3420-49F2-9D7C-015BEF196648@seantek.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <8435f221-7035-b55a-36e1-392426b4973d@gmx.de>
Date: Fri, 9 Sep 2016 09:27:34 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <93579AEE-3420-49F2-9D7C-015BEF196648@seantek.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:0yL0yNmtowz293okmegBKIPSPCcFYAj7UEj06c/ndKiqHs1LQF+ 9u+Z7/u9y4vpj04iP0R1+mPxJzjDQMFEO89cZ2t9MN9WdIB3AxD/YcDL9TEngSv3D5CGH93 sCAkmeWf1UduEVEz5MnXb2oU9E4omF6Jqlj4roRv6WJW0PrMS5DFwgZCZAkr+6LDRNSccEE pt6aGyRML/VaEda04bZkQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:IreIYAV251A=:Cl+qEFs/MjEsTn4MsDyQGl vBMPZ1pZwzs6gQiKi0mdNWg6UCMhWEgr9hKIII8kVwSfkPyUqATw/ucK5gbwepfkUIw7y/wkO /9aMliJRGFg2UPICUenEGy7qFChDYrnYz5CaumW3RrHzFqJBaAIcylh3MtDJsRuJVh4ZLaJyx 5jHAX/fHBnFNWI0EvQGgIFaWprHp1W6kVfB0fo5QTtznGAQJwAVPw6quw3mNaz5xVWjHFZlGs Duy2+ZPxO8YUY+V7N4GHvlIfRQ5ubOjYVU6A99qSXwvdlSmNrfvxw8vttF12+cN+v5Je3orMe QVs7l3ASHZ2fl3MNZvG6kio9xDZbHdbUnCBItEjg2Fpmp+Z23hCqj2anM+m5kh+RbIHaBTahy 49tEzuu6zHEbPcLEJscNFFrSZmThh8xUlUdLPFhdXE62jhA5Lpbioa13+puqLq/fiBwtcN9b3 I6h3T6hdyrHE8oV4+E8pUKXgMOUsn2STNaHB8cRBOIf/0yUgngEWcYUZq71ZDPJFK4g8Wszqr q571BGa1ZElTVsJ4+E6C0EFxzyTwbo32jLngL9tLO2G4u+OI0P5NypiMN0Jl/M1crmvyBSIwM bRqv1gQvtzHjf3+rmm6wokejEczf4jeO6albqMsfErRo7jGga3NRpW5TiypIdq3KOMqmUeKCf i/2oO2rjfv9yQaGQXhHh1DifCGNaN+FaE8EeB4NS+G+r9TeKlcyI9+yszZJ2OE6fKT13c3QXI ozWhEON13UXRG96DILlLjVz+9KsVaJBwyijNnsqrcX//M5x1rM7HYphLO1QcT2nc8txQkqPg9 fEWYWUk
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/m2-LWo99W6YR0Rero8r0s4vNxMI>
Subject: Re: [xml2rfc] xml2rfc v2 <artwork src="...">
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Sep 2016 07:27:50 -0000

On 2016-09-09 08:58, Sean Leonard wrote:
> Hello:
>
> xml2rfc v2 says that <artwork> can have a @src attribute, which is a URI. I assume that the base URI is the current URI of the xml2rfc document.

Yes.

> What is the proper behavior when an <artwork> has textual data and also has the src attribute? Is it a fatal processing error, or does one take precedence? RFC 7749 does not say.

It depends.

rfc2629.xslt uses the @src attribute when producing HTML.

xml2rfc.tcl AFAIR uses the textual content when producing plain text and 
the @src attribute when producing HTML.

That is, the text content is used as a fallback when the output format 
doesn't support graphics.

(Note that the behavior might depend on the presence of 
<https://greenbytes.de/tech/webdav/rfc7749.html#element.artwork.attribute.type>, 
and it starting with "image/" -- I don't believe anybody has tested this 
with any other media type).

> Note: The xml2rfc v3 draft says: “It is an error to have both a "src" attribute and content in the <artwork> (or <sourcecode>) element.” Therefore I would say that v3 treats the condition as fatal. The xml2rfc v3 preptool draft suggests that @src is supposed to be factored out during the posting/publication process, by including the contents directly in the inner XML element, or by using a data: URI.

That's IMHO a bug in the v3 draft.

> It appears that the xml2rfc v2 2.5.1 (Python) completely ignores the src attribute on <artwork>, as confirmed with both testing and source code analysis. It does not even care, so <artwork src=“foo.txt"/> is treated as <artwork></artwork>, and the presence of both text and @src results in just the text being used. I just tried submitting an Internet-Draft with an <artwork> with both @src and text, and the upload tool took it (I didn’t actually post the draft).
>
> Would this be loosely classified as a “bug” (or missing feature), or is this by design?

I'd consider this a bug with low prio, as it doesn't affect the output 
formats the IETF *currently* works on.

> Sean
>
> PS I am trying to decide if a tool should basically ignore <artwork> @src, error out, or do something else.

It depends on the audience of that tool, I'd say.

Best regards, Julian


From nobody Fri Sep  9 01:05:13 2016
Return-Path: <dev+ietf@seantek.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 6CD8B12B0E3 for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 01:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 r7YJY-riCNjz for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 01:05:11 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1426512B0D3 for <xml2rfc@ietf.org>; Fri,  9 Sep 2016 01:05:11 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 08C5250A84; Fri,  9 Sep 2016 04:05:09 -0400 (EDT)
To: Julian Reschke <julian.reschke@gmx.de>, XML2RFC Interest Group <xml2rfc@ietf.org>
References: <93579AEE-3420-49F2-9D7C-015BEF196648@seantek.com> <8435f221-7035-b55a-36e1-392426b4973d@gmx.de>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <dcd65332-cb41-ef48-069e-e1cdf1b1ca01@seantek.com>
Date: Fri, 9 Sep 2016 01:04:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <8435f221-7035-b55a-36e1-392426b4973d@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/cb0NkjFvFJ_8ZZTAre0j_UPY8Ng>
Subject: Re: [xml2rfc] xml2rfc v2 <artwork src="...">
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Sep 2016 08:05:12 -0000

On 9/9/2016 12:27 AM, Julian Reschke wrote:
> On 2016-09-09 08:58, Sean Leonard wrote:
>> Hello:
>>
>> xml2rfc v2 says that <artwork> can have a @src attribute, which is a 
>> URI. I assume that the base URI is the current URI of the xml2rfc 
>> document.
>
> Yes.
>
>> What is the proper behavior when an <artwork> has textual data and 
>> also has the src attribute? Is it a fatal processing error, or does 
>> one take precedence? RFC 7749 does not say.
>
> It depends.
>
> rfc2629.xslt uses the @src attribute when producing HTML.
>
> xml2rfc.tcl AFAIR uses the textual content when producing plain text 
> and the @src attribute when producing HTML.
>
> That is, the text content is used as a fallback when the output format 
> doesn't support graphics.
>
> (Note that the behavior might depend on the presence of 
> <https://greenbytes.de/tech/webdav/rfc7749.html#element.artwork.attribute.type>, 
> and it starting with "image/" -- I don't believe anybody has tested 
> this with any other media type).

Okay, thanks. Overall it sounds like the intent of @src in v2 is to be 
used for (binary) graphics formats, with the text content being a 
fallback to the (binary) graphic.

>
>> Note: The xml2rfc v3 draft says: “It is an error to have both a "src" 
>> attribute and content in the <artwork> (or <sourcecode>) element.” 
>> Therefore I would say that v3 treats the condition as fatal. The 
>> xml2rfc v3 preptool draft suggests that @src is supposed to be 
>> factored out during the posting/publication process, by including the 
>> contents directly in the inner XML element, or by using a data: URI.
>
> That's IMHO a bug in the v3 draft.

Well, if it's a bug, it's a deliberately-engineered bug: the text in 
draft-iab-rfcv3-preptool-02 says repeatedly to error out if both @src 
and text content are present...

>
>> It appears that the xml2rfc v2 2.5.1 (Python) completely ignores the 
>> src attribute on <artwork>, as confirmed with both testing and source 
>> code analysis. It does not even care, so <artwork src=“foo.txt"/> is 
>> treated as <artwork></artwork>, and the presence of both text and 
>> @src results in just the text being used. I just tried submitting an 
>> Internet-Draft with an <artwork> with both @src and text, and the 
>> upload tool took it (I didn’t actually post the draft).
>>
>> Would this be loosely classified as a “bug” (or missing feature), or 
>> is this by design?
>
> I'd consider this a bug with low prio, as it doesn't affect the output 
> formats the IETF *currently* works on. 

Ok, good enough for my purposes for now.

Sean


From nobody Fri Sep  9 01:09:33 2016
Return-Path: <julian.reschke@gmx.de>
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 5438312B119 for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 01:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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 G5zpiOg1L2rL for <xml2rfc@ietfa.amsl.com>; Fri,  9 Sep 2016 01:09:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEBD812B09B for <xml2rfc@ietf.org>; Fri,  9 Sep 2016 01:09:30 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.64.86]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MZU7V-1bUAP51DPJ-00LCec; Fri, 09 Sep 2016 10:09:26 +0200
To: Sean Leonard <dev+ietf@seantek.com>, XML2RFC Interest Group <xml2rfc@ietf.org>
References: <93579AEE-3420-49F2-9D7C-015BEF196648@seantek.com> <8435f221-7035-b55a-36e1-392426b4973d@gmx.de> <dcd65332-cb41-ef48-069e-e1cdf1b1ca01@seantek.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <21a4f116-a884-c0f4-cbf9-80dd6db9d276@gmx.de>
Date: Fri, 9 Sep 2016 10:09:25 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <dcd65332-cb41-ef48-069e-e1cdf1b1ca01@seantek.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:fFDBi3zt2hhblFBhJBAIrX3ljraSjCi1o8mIsBkCc7xYxJL1c1M efiGSiRHb+EcFD2UR9aLj5asNLCQuc7otmNQEyjVHDml3zeMQmMTK6LfF89q5MlXbgOeGkA eKakbY9GFGV4VTMwz6LWkWv6HeA3wRBZelKAYDYHkG2eE2b4sAYZi16zRXQzd2BMK5o+Q21 3h9ZoEpTzdSPD2rkPEwIQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:k4TUFknqHBQ=:BtmCz9kZOLRdaN8oj0XHkn T6oeDc3CFPKg+JaI0RMjgq+iIJGpITCSy2FAgUpsD2z5Z2vsz671GKymKDURgPJXG9Bc0pOee MQE6syBswxUmXkcuap03g/hkdo/zz6/VxJor/lm1XimXZs/5b44+qsYUkgs9VnDIqKOUmPP9g 3MzNbVoWtn93CGHmHWWrf/j0MtnNsNhCE81Ed6n9EpY870u8XbmWIcfbK1++IBYl+yZrHKMQh clZP2GzpU+NRkAZQ5HWhMoTQ0JUSF3mOBqR93sjARrR4X56UElJaMBgl4TLdzK88xASI61FIc NH+ixzVTN2zqVdzlmFzlAFd9KRHuqY6/eYgjww+tonSuB1zpMSu3knt99ZKZMh1yWbBiYF6dY /yWDxsq6uzcr9yeXrCp3iacwnwO/q+KBrrG/kqnHaPHNxadvXTgG09/yaJABxSuFgskCmC3wV 1PouRsd57auHuYP6KSAwXt3hSNEj6RtZoXcLp2AOWGbn8rBVQ7Kx+HwBlXtukybQWaxgj8t+p CH9X9k437rfyfG2KIEeYiKzOCblgbdEh6fiYn4G+nm2ejmMGnIEKQ3DwfwjCDAX5fkDGNI+ah GzW6r4PhA4daPdvR/5+9XvyeJ8wcGKte9g7fZxG9R5E1QFkQglW5Sp8zZ/qQ+sL7AxH+THwXo /HwXjgPawxC4NU4dv4/h1PsJO8zkNsSID4xqjuxTNY6J+V1yaCwBkqMAWN1FGq867lezrjTHO 2YRWMpuxsos4IH5ekGqvOPYWTkJB8PNSfuZY99FDN0zZzeA5K6acI76f9DMuBzub+jI0XP6g7 qk5i+2K
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/mKZCSvgR34Y-ES05eqq8Jzn7rf4>
Subject: Re: [xml2rfc] xml2rfc v2 <artwork src="...">
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Sep 2016 08:09:32 -0000

On 2016-09-09 10:04, Sean Leonard wrote:
> ...
> Okay, thanks. Overall it sounds like the intent of @src in v2 is to be
> used for (binary) graphics formats, with the text content being a
> fallback to the (binary) graphic.

Indeed.

> ...
>> That's IMHO a bug in the v3 draft.
>
> Well, if it's a bug, it's a deliberately-engineered bug: the text in
> draft-iab-rfcv3-preptool-02 says repeatedly to error out if both @src
> and text content are present...
> ...

Yes, I happen to disagree with multiple things in v3.

> ...

Best regards, Julian


From nobody Mon Sep 12 16:55:35 2016
Return-Path: <trac@tools.ietf.org>
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 AB53312B15A for <xml2rfc@ietfa.amsl.com>; Mon, 12 Sep 2016 16:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 ygEi15cRnTxz for <xml2rfc@ietfa.amsl.com>; Mon, 12 Sep 2016 16:55:32 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1A3E12B14C for <xml2rfc@ietf.org>; Mon, 12 Sep 2016 16:55:32 -0700 (PDT)
Received: from localhost ([::1]:42304 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1bjb4W-0003Zq-JF; Mon, 12 Sep 2016 16:55:32 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "xml2rfc issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: henrik@levkowetz.com, dev+ietf@seantek.com
X-Trac-Project: xml2rfc
Date: Mon, 12 Sep 2016 23:55:32 -0000
X-URL: http://tools.ietf.org/tools/xml2rfc/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/327
Message-ID: <068.b7f3ae96f2e51d4cec67d807b37b27ec@tools.ietf.org>
X-Trac-Ticket-ID: 327
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: henrik@levkowetz.com, dev+ietf@seantek.com, xml2rfc@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/mlQcFmve7e4sauUVIdVSRmCL92o>
Cc: xml2rfc@ietf.org
Subject: [xml2rfc] #327 (Version 2 cli): Having more than 26 appendices causes unhandled exception
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 12 Sep 2016 23:55:35 -0000

#327: Having more than 26 appendices causes unhandled exception

 When an xml2rfc source has more than 26 appendices, an unhanded exception
 occurs.

 To verify this behavior, create an xml2rfc document with more than 26
 appendices, such as:

 <back>
  <references>...</references>
  <section title="test"><t>test</t></section>
  (repeated 26 or more times)
 </back>

 Then run it on xml2rfc.

 Exemplary output:

 Traceback (most recent call last):
   File "/usr/local/bin/xml2rfc", line 5, in <module>
     pkg_resources.run_script('xml2rfc==2.4.8w', 'xml2rfc')
   File
 "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py",
 line 492, in run_script
     self.require(requires)[0].run_script(script_name, ns)
   File
 "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py",
 line 1350, in run_script
     execfile(script_filename, namespace, namespace)
   File ".../EGG-INFO/scripts/xml2rfc", line 225, in <module>
     main()
   File ".../EGG-INFO/scripts/xml2rfc", line 192, in main
     htmlwriter.write(filename)
   File ".../xml2rfc/writers/base.py", line 1186, in write
     self._build_index()
   File ".../xml2rfc/writers/base.py", line 1035, in _build_index
     self.write_section_rec(back, None, appendix=True)
   File ".../xml2rfc/writers/base.py", line 865, in write_section_rec
     self.write_section_rec(child_sec, uppercase[s_count - 1],
 IndexError: string index out of range


 (Note that, at present, there is no limitation on the number of appendices
 in the xml2rfc vocabulary.)

 The underlying problem is that the code around lines 863-866 in base.py
 have undefined behavior past 26:

                 # Use an alphabetic counter for first-level appendix
                 uppercase = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
                 self.write_section_rec(child_sec, uppercase[s_count - 1],
                                         level=level + 1, appendix=True)

 One correct solution is to compute the appendix letter(s) by converting to
 base 26 ( mod 26 and divide by 26) to get AA-AZ, BA-BZ, etc. as discussed
 in Stack Overflow question #15791780.

-- 
-------------------------------------------+-------------------------------
 Reporter:  dev+ietf@seantek.com           |      Owner:
     Type:  defect                         |  henrik@levkowetz.com
 Priority:  medium                         |     Status:  new
Component:  Version 2 cli                  |  Milestone:
 Keywords:  appendix, appendices, section  |    Version:  2.5.x
-------------------------------------------+-------------------------------

Ticket URL: <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/327>
xml2rfc <http://tools.ietf.org/tools/xml2rfc/>


From nobody Mon Sep 12 20:34:23 2016
Return-Path: <trac@tools.ietf.org>
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 E1AC612B1C9 for <xml2rfc@ietfa.amsl.com>; Mon, 12 Sep 2016 20:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 nM4JArXMHqNu for <xml2rfc@ietfa.amsl.com>; Mon, 12 Sep 2016 20:34:20 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5A4212B1A8 for <xml2rfc@ietf.org>; Mon, 12 Sep 2016 20:34:20 -0700 (PDT)
Received: from localhost ([::1]:46768 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1bjeUG-0004Bk-Hd; Mon, 12 Sep 2016 20:34:20 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "xml2rfc issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: henrik@levkowetz.com, tony@att.com
X-Trac-Project: xml2rfc
Date: Tue, 13 Sep 2016 03:34:20 -0000
X-URL: http://tools.ietf.org/tools/xml2rfc/
X-Trac-Ticket-URL: /ticket/327#comment:1
Message-ID: <083.e70654616d12b259cf9be3d5bf9903d9@tools.ietf.org>
References: <068.b7f3ae96f2e51d4cec67d807b37b27ec@tools.ietf.org>
X-Trac-Ticket-ID: 327
In-Reply-To: <068.b7f3ae96f2e51d4cec67d807b37b27ec@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: henrik@levkowetz.com, tony@att.com, xml2rfc@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/NwOIADRdk5evpQcmWobYryj53r4>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] #327 (Version 2 cli): Having more than 26 appendices causes unhandled exception
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Sep 2016 03:34:23 -0000

#327: Having more than 26 appendices causes unhandled exception

Changes (by tony@att.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in [2253]:

 fix for #327

-- 
-------------------------------+-------------------------------------------
  Reporter:                    |      Owner:  henrik@levkowetz.com
  dev+ietf@seantek.com         |     Status:  closed
      Type:  defect            |  Milestone:
  Priority:  medium            |    Version:  2.5.x
 Component:  Version 2 cli     |   Keywords:  appendix, appendices, section
Resolution:  fixed             |
-------------------------------+-------------------------------------------

Ticket URL: </ticket/327#comment:1>
xml2rfc <http://tools.ietf.org/tools/xml2rfc/>


From nobody Tue Sep 13 08:07:05 2016
Return-Path: <lars@netapp.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 BC90012B651 for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 08:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.409
X-Spam-Level: 
X-Spam-Status: No, score=-8.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.508, 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 glgFmxgkGD2o for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 08:06:57 -0700 (PDT)
Received: from mx142.netapp.com (mx142.netapp.com [216.240.21.19]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69FEF12B66E for <xml2rfc@ietf.org>; Tue, 13 Sep 2016 07:38:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.30,329,1470726000";  d="asc'?scan'208";a="137595030"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx142-out.netapp.com with ESMTP; 13 Sep 2016 07:37:47 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 13 Sep 2016 07:37:46 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::4ca2:22d:a2f1:881b%21]) with mapi id 15.00.1210.000; Tue, 13 Sep 2016 07:37:45 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "citations@rfc-editor.org" <citations@rfc-editor.org>
Thread-Topic: "Dr." prefix in 1id-index.txt
Thread-Index: AQHSDcxjIlws31KK30a+sNzjDJL4bA==
Date: Tue, 13 Sep 2016 14:37:44 +0000
Message-ID: <32A11F1A-7FB4-468E-867E-F8C1722265AC@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_D56281DF-2AA8-44F6-99C2-8F034FDFFE39"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/HVqA-99ULozJk8YVJ9USohDtFMc>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Subject: [xml2rfc] "Dr." prefix in 1id-index.txt
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Sep 2016 15:07:04 -0000

--Apple-Mail=_D56281DF-2AA8-44F6-99C2-8F034FDFFE39
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

apparently, 1id-index.txt now has academic titles for some authors; at =
least I see "Dr." for many entries. This must be new?

This causes xml2rfc to rename all these authors first names to "D.", =
which is incorrect in 95% of the cases :-)

Lars

--Apple-Mail=_D56281DF-2AA8-44F6-99C2-8F034FDFFE39
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJX2A86AAoJEFS1wwm/cMFXMz0P/j/BxDu7W9C3viJf4pjF9KCq
8O1bhv2g3zeJ7kbu4il1pWniouZ6BBb/51jKeyJtkBDTnNfE3R45o5WiaQHPm6Bi
cA2LAyqCd8C06112OY2qSxUrKAvmqEwYP2JLixr3jghZ9frMF/LVxDrFE2fqB2dW
fw5SiTLYe/r8m7iaPvZSOw7Oh70ra3XsW8NYsotl1zaNwZvETYXwZgBAM9vwbL21
ta09O+5Rh10a9aMqLF055OPWeGJNzOBP5/KUdOg6QHZN8Z8ndmGEPAB8WwTvph8W
qm/1IdY59sBNuM3MmDEHovNGnkbh0a6mlLX76vKhq7jtS69OA0vBzjyOCER96lsv
ouqQTWWBsrX1In3C0QYpGrusQFvyjzl7+btQ+SELnZHb7+aJ7YDe6g5DiuoeV1LY
F8RlBU7zV1nl/sujtycBsYzYOMT7TxXGpW5t9+Yipv/ir1HdEgtqHbSr64n4+hmF
knLnn9XS/d+cf0lpceWDjVm30GCGnV3JYM4DUsxSfUn3wFw9E9SoM5tKOPCAN0nP
VmmedkJNEKtMGWhyphslrRVPEvmLZG6ZKIJMKs0zfr0Tf1TiLovP1uw9Txfz9d9L
hH1N5MKhMVRRPcRCbKuhBqN4JyoTkZ9xwm994b/6R/V9ybBmkGWFw6mG3T1Gzi4+
YF0QnBccvKauRdQfCad6
=kXDk
-----END PGP SIGNATURE-----

--Apple-Mail=_D56281DF-2AA8-44F6-99C2-8F034FDFFE39--


From nobody Tue Sep 13 11:55:44 2016
Return-Path: <henrik@levkowetz.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 8C61312B02E for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 11:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 jhh5LDQH0unY for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 11:55:41 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5393312B4F9 for <xml2rfc@ietf.org>; Tue, 13 Sep 2016 11:55:36 -0700 (PDT)
Received: from 81-235-150-134-no105.tbcn.telia.com ([81.235.150.134]:51812 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <henrik@levkowetz.com>) id 1bjsrj-00041V-JF; Tue, 13 Sep 2016 11:55:31 -0700
Message-ID: <57D84B9B.1060704@levkowetz.com>
Date: Tue, 13 Sep 2016 20:55:23 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>,  "citations@rfc-editor.org" <citations@rfc-editor.org>
References: <32A11F1A-7FB4-468E-867E-F8C1722265AC@netapp.com>
In-Reply-To: <32A11F1A-7FB4-468E-867E-F8C1722265AC@netapp.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fqoIhbuaTJVlAgelVqSmHGu0wfnrTEVjK"
X-SA-Exim-Connect-IP: 81.235.150.134
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, citations@rfc-editor.org, lars@netapp.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/IS0pjmCa1tu4ttEGzkIOrKgCKHA>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] "Dr." prefix in 1id-index.txt
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Sep 2016 18:55:42 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--fqoIhbuaTJVlAgelVqSmHGu0wfnrTEVjK
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Lars,

On 2016-09-13 16:37, Eggert, Lars wrote:
> Hi,
>=20
> apparently, 1id-index.txt now has academic titles for some authors;
> at least I see "Dr." for many entries. This must be new?
>=20
> This causes xml2rfc to rename all these authors first names to "D.",
> which is incorrect in 95% of the cases :-)

Ugh.  That was an inadvertent change resulting from some refactoring
that was merged in not so long ago.  Fixed in [11986].

Thanks for the alert!

	Henrik


--fqoIhbuaTJVlAgelVqSmHGu0wfnrTEVjK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJX2EubAAoJEE6bV0uPuxcapo0P/2biyV9KlxP09U1T3r2Yy0Hn
lAmj/xSujClkHUPqnGawcW2s0Xj679cCyrdZ1z49w6cVqKNvxH0Dqw7c6MAWBuY3
Gl0lTbNER49b5lA7WfaaQMK8m7LVfhOvwRpYpCfcip/1OanDXMbZ4HMYGFoySRvU
wXCq1oD4GAQ6g7sNr9erxGnxPNUJW0W3GavtZCxgcbXwyhQYnbcTFOjgmsmR8W/I
pIIB6Ta1MeecsA84I38+XZLUZOKtSBunnYhKHKyY01kYQmeATCpnE9q4d+0YR2ml
dLPyG4j/q4PuEbEcmX5Prv2RmzNAjIiOvuLtQckhkMVEgtQZoo5NBaadqzTNpFwz
3H8NANnGzIeHHkmzFvNmNEkpqwLEpq2Z7FJd/kNC/zTscc71L0O1imnBLvB6yFhn
5bYb6x/wyXyhSvcRblzVzs/EjEtZ6uA7JoajWAAqh6MC4s13G++R3C3bJlcDaxm3
VBMamP3fG3g4N1YHDHLakcUT9HAEq830OSoq0ZK8BkSu+Tv6uLx0x+6p/eam/tQi
NuaCpgi6Xm8/CjTnL8ve6tzEI0TcCX4gq+fHN5Q83+Nn5nyHeoqp+vFNIMSAr2pt
D/77o8XCQ8lUnIGKa5yQ0szDUYRktJH+SxwOSdW1X5c+BH74+Evdrcq65VgVR/j+
Fzq1Ffazm9rbiCcnounp
=0cmP
-----END PGP SIGNATURE-----

--fqoIhbuaTJVlAgelVqSmHGu0wfnrTEVjK--


From nobody Tue Sep 13 12:40:09 2016
Return-Path: <trac@tools.ietf.org>
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 8923912B03A for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 12:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 5S-GPNHuk5ki for <xml2rfc@ietfa.amsl.com>; Tue, 13 Sep 2016 12:40:05 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D24812B009 for <xml2rfc@ietf.org>; Tue, 13 Sep 2016 12:40:05 -0700 (PDT)
Received: from localhost ([::1]:48529 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1bjtYo-0007yZ-Va; Tue, 13 Sep 2016 12:40:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "xml2rfc issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: henrik@levkowetz.com, tony@att.com, dev+ietf@seantek.com
X-Trac-Project: xml2rfc
Date: Tue, 13 Sep 2016 19:40:02 -0000
X-URL: http://tools.ietf.org/tools/xml2rfc/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/327#comment:2
Message-ID: <083.bf17bbc7dd31e24d1ff5fa0f5157c072@tools.ietf.org>
References: <068.b7f3ae96f2e51d4cec67d807b37b27ec@tools.ietf.org>
X-Trac-Ticket-ID: 327
In-Reply-To: <068.b7f3ae96f2e51d4cec67d807b37b27ec@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: henrik@levkowetz.com, tony@att.com, dev+ietf@seantek.com, xml2rfc@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/z2ZcEpzEMO4eVut8lGZodJWV5i8>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] #327 (Version 2 cli): Having more than 26 appendices causes unhandled exception
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Sep 2016 19:40:08 -0000

#327: Having more than 26 appendices causes unhandled exception


Comment (by dev+ietf@seantek.com):

 I tested the patch and it addresses this bug. Thank you!

-- 
-------------------------------+-------------------------------------------
  Reporter:                    |      Owner:  henrik@levkowetz.com
  dev+ietf@seantek.com         |     Status:  closed
      Type:  defect            |  Milestone:
  Priority:  medium            |    Version:  2.5.x
 Component:  Version 2 cli     |   Keywords:  appendix, appendices, section
Resolution:  fixed             |
-------------------------------+-------------------------------------------

Ticket URL: <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/327#comment:2>
xml2rfc <http://tools.ietf.org/tools/xml2rfc/>


From nobody Thu Sep 15 05:24:15 2016
Return-Path: <erik.wilde@dret.net>
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 D58D212B2A1 for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 05:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 9NH9jca-CHO9 for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 05:24:10 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC57D12B212 for <xml2rfc@ietf.org>; Thu, 15 Sep 2016 05:24:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=zyv6M+8Hd8B7tKKaO2ydYVknORQX9RLk+AZACvo0rdQ=; b=YWYZG0HrNMYHzaZ6FG1bqPdQ1h 8uXkjrj3Hm4vd54L7ntfnNDq3RKu+QlDGLsURQQLbbhu8C5vDoLHxLRwBGqv+FSp2ZmOK3flL3cSI ytW90GkLgnDTBjFqHn0QEPAZzWJrupeRVDjyZRc54emjBo3hDji3SPesD3SyR8WMO2xI6JOqCLVaF 18QISgRSeEwVDiS4Qzcl6Yum4E4YwtzV2ce1E7//NS44sJzHDBZDNwlus90Kj6V+HXIsCQOIwOGw3 fFGsjDEr5hV/sZ2Cnucq/ZKVqz7yW5vSEe2s6jKEFRPAe/5nuVQqjQ3i8yD6g4XoQ2ewrf28Rq44Q Mw7xhw5A==;
Received: from [130.200.33.3] (port=2546 helo=dretpro.local) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <erik.wilde@dret.net>) id 1bkVi5-0005ep-Va for xml2rfc@ietf.org; Thu, 15 Sep 2016 08:24:10 -0400
To: xml2rfc@ietf.org
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <0ef0b427-f618-31b3-e267-b662189a4622@dret.net>
Date: Thu, 15 Sep 2016 08:24:09 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/FjHd6euyDHBLIpuMWF_57hQ54bE>
Subject: [xml2rfc] xml2rfc bug report
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Sep 2016 12:24:13 -0000

hello.

https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/308 is a bug i 
reported about half a year ago, and i just ran into it again 
(https://github.com/dret/I-D/issues/37 was reported for a draft i 
published yesterday). i am using the online version of xml2rfc. i am 
wondering about the trac tracker in general: is this an active tracker 
where it makes sense to report feedback such as this bug? is there a 
chance that this bug might be fixed, or at least acknowledged? i'd also 
be more than happy to use some workaround, if there is one.

thanks a lot and cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Thu Sep 15 07:07:26 2016
Return-Path: <cabo@tzi.org>
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 3DBD312BAB4 for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 07:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 otlzLAxrGOze for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 07:07:20 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [IPv6:2001:4b98:c:538::197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BACEE12BAB5 for <xml2rfc@ietf.org>; Thu, 15 Sep 2016 06:27:17 -0700 (PDT)
Received: from mfilter1-d.gandi.net (mfilter1-d.gandi.net [217.70.178.130]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id 22F0841C0AD; Thu, 15 Sep 2016 15:27:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter1-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter1-d.gandi.net (mfilter1-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 2V-KwSqwucCe; Thu, 15 Sep 2016 15:27:14 +0200 (CEST)
X-Originating-IP: 134.102.25.11
Received: from eduroam-pool6-0267.wlan.uni-bremen.de (eduroam-pool6-0267.wlan.uni-bremen.de [134.102.25.11]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 3706241C0AE; Thu, 15 Sep 2016 15:27:13 +0200 (CEST)
Message-ID: <57DAA1B0.5030801@tzi.org>
Date: Thu, 15 Sep 2016 15:27:12 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Erik Wilde <erik.wilde@dret.net>
References: <0ef0b427-f618-31b3-e267-b662189a4622@dret.net>
In-Reply-To: <0ef0b427-f618-31b3-e267-b662189a4622@dret.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/IgIrYjsuU-hux_w4c_XlleheUQg>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] xml2rfc bug report
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Sep 2016 14:07:25 -0000

Partial Workaround: symrefs=yes (I have no idea why people are still
doing symrefs=no).  This will at least make sure the erefs no longer use
the same number space as the bibliography xrefs.

More workaround: In addition, move the erefs out of the <note...>
section, which like the abstract is a weird section for xml2rfc when it
comes to references.

Grüße, Carsten


Erik Wilde wrote:
> hello.
> 
> https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/308 is a bug i
> reported about half a year ago, and i just ran into it again
> (https://github.com/dret/I-D/issues/37 was reported for a draft i
> published yesterday). i am using the online version of xml2rfc. i am
> wondering about the trac tracker in general: is this an active tracker
> where it makes sense to report feedback such as this bug? is there a
> chance that this bug might be fixed, or at least acknowledged? i'd also
> be more than happy to use some workaround, if there is one.
> 
> thanks a lot and cheers,
> 
> dret.
> 


From nobody Thu Sep 15 07:25:40 2016
Return-Path: <erik.wilde@dret.net>
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 B97AB12B83B for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 07:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 5I9IoLjdTcXi for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 07:25:33 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2397112B853 for <xml2rfc@ietf.org>; Thu, 15 Sep 2016 06:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2vsMi+9c39BvTTjqBMm1wNiu9ZdrfOYLQWQjZ3pFCiE=; b=pZ2nqU4U4kgpuGj1/r+v5Xg0Tf M+xdeoPSGjkbUaMnAZ1lR11f7D38StKu5xWvjY/rncJ2R+LGiMztv40XOEgP6FYV+PYz01JBt0gVS +1Q5/RZzBCbxUZFlaCwSDq1dA0N+o2Jm7r+1Y5FICa/jalcNjqI+eMlSHOTv4/ZyEZ/aSka7Mr9W4 3h0WTG5Asqe9jM6b/GB5f2LDBqNdr7UqVbfBeiMNrtuHq26C0Ca3/ik09uP+TjN9T3DgzriBws41e 9v0qUF900KQINzcuLvEiN6D5aOnf462TBxqfN5+MIIYNUVRnOeZI4TwGC0EARV3olr/j5ION+I/59 fAB1/H3g==;
Received: from [199.15.174.247] (port=52156 helo=dretair.local) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <erik.wilde@dret.net>) id 1bkWqj-0003n1-By; Thu, 15 Sep 2016 09:37:09 -0400
To: Carsten Bormann <cabo@tzi.org>
References: <0ef0b427-f618-31b3-e267-b662189a4622@dret.net> <57DAA1B0.5030801@tzi.org>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <417f21a1-41d7-b64a-c8c9-2209d9bea16a@dret.net>
Date: Thu, 15 Sep 2016 09:37:08 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <57DAA1B0.5030801@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/G0zxF2K3hOs-7lfUiDTVAve49lU>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] xml2rfc bug report
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Sep 2016 14:25:38 -0000

guten tag carsten.

On 2016-09-15 09:27, Carsten Bormann wrote:
> Partial Workaround: symrefs=yes (I have no idea why people are still
> doing symrefs=no).  This will at least make sure the erefs no longer use
> the same number space as the bibliography xrefs.

https://github.com/dret/I-D/commit/c260298bc043f1b94c33f88945434bc4dd49406d 
does that, thanks for the idea!

> More workaround: In addition, move the erefs out of the <note...>
> section, which like the abstract is a weird section for xml2rfc when it
> comes to references.

maybe. mostly it was my attempt to put that information into a place 
where it can easily disappear eventually without changing what was the 
actual content of the draft.

thanks and cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Thu Sep 15 08:26:13 2016
Return-Path: <trac@tools.ietf.org>
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 B57EC12B61B for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 08:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 jn3QBNnAYXyE for <xml2rfc@ietfa.amsl.com>; Thu, 15 Sep 2016 08:25:59 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B80512B546 for <xml2rfc@ietf.org>; Thu, 15 Sep 2016 07:27:21 -0700 (PDT)
Received: from localhost ([::1]:52671 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1bkXdI-0002jf-6U; Thu, 15 Sep 2016 07:27:20 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "xml2rfc issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: henrik@levkowetz.com, cabo@tzi.org
X-Trac-Project: xml2rfc
Date: Thu, 15 Sep 2016 14:27:20 -0000
X-URL: http://tools.ietf.org/tools/xml2rfc/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/308#comment:1
Message-ID: <082.4f91420cfaa9dd0ec1a189d3501e01fc@tools.ietf.org>
References: <067.c476289a4cc36deb4e5527f33b090f4c@tools.ietf.org>
X-Trac-Ticket-ID: 308
In-Reply-To: <067.c476289a4cc36deb4e5527f33b090f4c@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: henrik@levkowetz.com, cabo@tzi.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Lu7sOboYejokm-mA0E4Do2_v47w>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] #308 (Version 2 cli): Wrong links for <eref/> elements
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Sep 2016 15:26:07 -0000

#308: Wrong links for <eref/> elements


Comment (by cabo@tzi.org):

 As discussed in https://mailarchive.ietf.org/arch/msg/xml2rfc/IgIrYjsuU-
 hux_w4c_XlleheUQg there are two problems:

  * With symrefs=no, the eref name space is not distinct from the biblio
 xref name space.  Workaround: use symrefs=yes (which is the preferred way
 anyway) with eref.
  * erefs from <note...> elements are semi-swallowed by xml2rfc.
 (Workaround: Don't use erefs from <note...>, but there may be good reasons
 to do so.)

-- 
----------------------------------+----------------------------------
  Reporter:  erik.wilde@dret.net  |      Owner:  henrik@levkowetz.com
      Type:  defect               |     Status:  new
  Priority:  critical             |  Milestone:
 Component:  Version 2 cli        |    Version:  2.4.x
Resolution:                       |   Keywords:
----------------------------------+----------------------------------

Ticket URL: <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/308#comment:1>
xml2rfc <http://tools.ietf.org/tools/xml2rfc/>