IETF Logo Mail Archive

Re: [xml2rfc] #318 (Version 2 cli): Bug in the online XML2RFC HTML output

"xml2rfc issue tracker" <trac@tools.ietf.org> Mon, 22 August 2016 20:23 UTC

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 7821912D7F6 for <xml2rfc@ietfa.amsl.com>; Mon, 22 Aug 2016 13:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 udo0nFkzJDt6 for <xml2rfc@ietfa.amsl.com>; Mon, 22 Aug 2016 13:23:21 -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 0B91B12D0C8 for <xml2rfc@ietf.org>; Mon, 22 Aug 2016 13:23:21 -0700 (PDT)
Received: from localhost ([::1]:43779 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 1bbvkd-0001qj-UA; Mon, 22 Aug 2016 13:23:19 -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, worley@ariadne.com
X-Trac-Project: xml2rfc
Date: Mon, 22 Aug 2016 20:23:19 -0000
X-URL: http://tools.ietf.org/tools/xml2rfc/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/318#comment:1
Message-ID: <081.9a572437d36a8726bfe068010a10087c@tools.ietf.org>
References: <066.a4054d4375a79d2a497493d755fbf11a@tools.ietf.org>
X-Trac-Ticket-ID: 318
In-Reply-To: <066.a4054d4375a79d2a497493d755fbf11a@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: henrik@levkowetz.com, worley@ariadne.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/0zuwsdWDDkGSqjmBY0pNuE3FK1o>
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] #318 (Version 2 cli): Bug in the online XML2RFC HTML output
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, 22 Aug 2016 20:23:22 -0000

#318: Bug in the online XML2RFC HTML output


Comment (by worley@ariadne.com):

 Here's another instance of the problem:  The third paragraph of section 4
 of the HTML output generated for https://svn.resiprocate.org/rep/ietf-
 drafts/worley/draft-ietf-sipcore-dns-dual-stack-08.xml

 It appears that the error works in this way:  When the paragraph has this
 structure:

       <t>For example, consider a server with DNS name example.com, with
 TCP
       transport specified.  The relevant SRV records for example.com are:
       <list style="empty"><t>
       [items]
       </t></list>
       The processing of <xref target="RFC2782"/> results in this
       ordered list of target domain names:
       <list style="empty"><t>
       [items]
       </t></list>
       The address records for sip-1.example.com, as ordered by <xref
 target="RFC6724"/>, are
       <list style="empty"><t>
       [items]
       </t></list>
       and the address records for sip-2.example.com, as ordered by
       <xref target="RFC6724"/>, are:
       </t>

 the text output is correct.  But the HTML structure is incorrect; it has
 the correct sequence of running text sections and lists, but the running
 text is placed into the running text sections incorrectly.  Each of the
 latter running text sections is broken into two parts, where the part
 before the <xref> element is placed correctly, but the <xref> and the
 following text is appended to the first running text section.  The output
 has this structure:

       <t>For example, consider a server with DNS name example.com, with
 TCP
       transport specified.  The relevant SRV records for example.com are:
       [RFC2782] results in this ordered list of target domain names:
       [RFC6724], are [RFC6724], are:

       [items]

       The processing of

       [items]

       The address records for sip-1.example.com, as ordered by

       [items]

       and the address records for sip-2.example.com, as ordered by

-- 
---------------------------------+----------------------------------
  Reporter:  worley@ariadne.com  |      Owner:  henrik@levkowetz.com
      Type:  defect              |     Status:  new
  Priority:  medium              |  Milestone:
 Component:  Version 2 cli       |    Version:  2.5.x
Resolution:                      |   Keywords:
---------------------------------+----------------------------------

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

v2.23.0 | Report a Bug | By Email