Information Processing Systems - Open Systems Interconnection Reference Model

, 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 From infrastation@yandex.ru Sun Sep 22 00:37:29 2013 Return-Path: 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 4C3A121F9E46 for ; Sun, 22 Sep 2013 00:37:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.379 X-Spam-Level: *** X-Spam-Status: No, score=3.379 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, RCVD_ILLEGAL_IP=1.908] 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 sQxI6HhmKoPD for ; Sun, 22 Sep 2013 00:37:24 -0700 (PDT) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by ietfa.amsl.com (Postfix) with ESMTP id B467621F9E3F for ; Sun, 22 Sep 2013 00:37:17 -0700 (PDT) Received: from web3j.yandex.ru (web3j.yandex.ru [5.45.198.44]) by forward13.mail.yandex.net (Yandex) with ESMTP id 6D143141DEA for ; Sun, 22 Sep 2013 11:37:14 +0400 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web3j.yandex.ru (Yandex) with ESMTP id 243447081048; Sun, 22 Sep 2013 11:37:14 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1379835434; bh=q+vaomLfzmTTe1I3Sv/PRzSvmyE6mXUK+7blzAxpdus=; h=From:To:In-Reply-To:References:Subject:Date; b=ec9uVV9bigV4pJ1cswd+oX0ls2z4pfSFCJXdviPgtN0NcZhAYaj7sxlhvccLQZS8b BZUOJndkTTAu6lz5SHczxfK+fh1zYiL1AVupPMziTtZQU3Kg1GgY5v/dEZu7WYgPf9 /KfBFH3Fb0t6LDLeIYMo/Jis51ehoUDNJ+S5fWB0= Received: from broadband-46-188-49-204.2com.net (broadband-46-188-49-204.2com.net [46.188.49.204]) by web3j.yandex.ru with HTTP; Sun, 22 Sep 2013 11:37:13 +0400 From: Denis Ovsienko To: xml2rfc In-Reply-To: <523E81FF.4070904@gmail.com> References: <523E81FF.4070904@gmail.com> MIME-Version: 1.0 Message-Id: <66681379835433@web3j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 22 Sep 2013 11:37:13 +0400 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: Re: [xml2rfc] Two issues with new version X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 07:37:29 -0000 [...] > Generating an HTML file, there's no problem: this simply > generates a link, as expected. > > BUT, generating a TXT file, each 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. [...] Hello. For my own input (symrefs="yes" and two EREFs in the middle of a list item each) the _old_ xml2rfc produces "[1]" and "[2]", adding an "URIs" section just after the informative references. -- Denis Ovsienko From trac@tools.ietf.org Sun Sep 22 11:19:50 2013 Return-Path: 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 CC6EB21F940D for ; Sun, 22 Sep 2013 11:19:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 NP0h+49a1yDs for ; Sun, 22 Sep 2013 11:19:50 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF7021F9E36 for ; Sun, 22 Sep 2013 11:19:46 -0700 (PDT) Received: from localhost ([127.0.0.1]:45902 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VNoG1-00085k-0x; Sun, 22 Sep 2013 20:19:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, john-ietf@jck.com X-Trac-Project: xml2rfc Date: Sun, 22 Sep 2013 18:19:44 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/198 Message-ID: <065.270f26f919042693c1a1087744dfd2f1@tools.ietf.org> X-Trac-Ticket-ID: 198 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, john-ietf@jck.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org Subject: [xml2rfc] #198: Misleading "premature end of data" indication X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 18:19:50 -0000 #198: Misleading "premature end of data" indication Hi. I accidentally copied some text into a source document that came from rich text web content and that contained an EM-dash. The xml2rfc parser went a little crazy, treating the element block in which that character appeared as having a "premature end of data" somewhere (and than, of course, assuming premature end of data for all containing elements). Recommendation: Put a test into the parser for non-ASCII characters and report them accordingly. Even better, couple that text with a new processing directive list and default it to "no". I think the combination will head off a lot of strange issues and bad diagnostics when such characters are permitted (other values might eventually be "yes" and/or "per-style-manual"). But even the first alone would allow a much more useful error indicating. -- -------------------------------+---------------------------------- Reporter: john-ietf@jck.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Keywords: | -------------------------------+---------------------------------- Ticket URL: xml2rfc From brian.e.carpenter@gmail.com Sun Sep 22 13:07:17 2013 Return-Path: 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 07C7B21F9D2C for ; Sun, 22 Sep 2013 13:07:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.552 X-Spam-Level: X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, 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 W1gDJg0ZvmF6 for ; Sun, 22 Sep 2013 13:07:16 -0700 (PDT) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 95F0921F9D2A for ; Sun, 22 Sep 2013 13:07:14 -0700 (PDT) Received: by mail-pb0-f47.google.com with SMTP id rr4so2396438pbb.34 for ; Sun, 22 Sep 2013 13:07:13 -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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QOyf2EcebbEk+F33FmtU05ldh/4Uq7cAr35F2zYS3NA=; b=H8rhSPiHOf9udELvlbIH+5/Xz1PzQsGDQPkgBjYYApeNpJj+FM/3jERQMToMfZKYCK adE9USCz/67TAaZt6EZpQuBaeLzGhLSSARNJVW8ZdUpp1G8oQjrGmdCh0PIBU6BaDGxu m21QiUf3yzxNIf09vjUl8/eU3EnSVHWWLgB1PWgA48nL2yj+gpUgs31pZCnK4GjvAamv kv71tdxpkHPXwrWwXlww61TKywZU607O8M4dIfXQkGKEnS2z5wfLplHa0GBVHaUxIGyo SCnnTeX/mXZjRQNcOTaANmJi62d/yNXCgdlvtJUI8fYbANIxQ13sd3zUz8LxydFOtsxJ sXkw== X-Received: by 10.68.225.99 with SMTP id rj3mr4328299pbc.122.1379880433110; Sun, 22 Sep 2013 13:07:13 -0700 (PDT) Received: from [192.168.178.20] (104.192.69.111.dynamic.snap.net.nz. [111.69.192.104]) by mx.google.com with ESMTPSA id j9sm33237265paj.18.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 22 Sep 2013 13:07:12 -0700 (PDT) Message-ID: <523F4DE6.8030300@gmail.com> Date: Mon, 23 Sep 2013 08:07:02 +1200 From: Brian E Carpenter Organization: University of Auckland User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Denis Ovsienko References: <523E81FF.4070904@gmail.com> <66681379835433@web3j.yandex.ru> In-Reply-To: <66681379835433@web3j.yandex.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: xml2rfc Subject: Re: [xml2rfc] Two issues with new version X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 20:07:17 -0000 On 22/09/2013 19:37, Denis Ovsienko wrote: > [...] >> Generating an HTML file, there's no problem: this simply >> generates a link, as expected. >> >> BUT, generating a TXT file, each 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. > [...] > > Hello. > > For my own input (symrefs="yes" and two EREFs in the middle of a list item each) the _old_ xml2rfc produces "[1]" and "[2]", adding an "URIs" section just after the informative references. That is definitely not what I see. Brian From trac@tools.ietf.org Sun Sep 22 13:17:47 2013 Return-Path: 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 39E1611E8147 for ; Sun, 22 Sep 2013 13:17:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Yo-rnxxJWLuZ for ; Sun, 22 Sep 2013 13:17:46 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 76F6D11E8145 for ; Sun, 22 Sep 2013 13:17:46 -0700 (PDT) Received: from localhost ([127.0.0.1]:53791 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VNq6D-0001G1-Hy; Sun, 22 Sep 2013 22:17:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Sun, 22 Sep 2013 20:17:45 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/198#comment:1 Message-ID: <080.c46410a960c45bf4ae4f200bed359b8d@tools.ietf.org> References: <065.270f26f919042693c1a1087744dfd2f1@tools.ietf.org> X-Trac-Ticket-ID: 198 In-Reply-To: <065.270f26f919042693c1a1087744dfd2f1@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org Subject: Re: [xml2rfc] #198: Misleading "premature end of data" indication X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 20:17:47 -0000 #198: Misleading "premature end of data" indication Comment (by henrik@levkowetz.com): Hi John, Actually, the parser should be able to handle unicode, even if we later limit the text to ascii or something else. Would it be possible for you to attach the file that caused the problem to this issue? Best regards, Henrik -- --------------------------------+---------------------------------- Reporter: john-ietf@jck.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Resolution: | Keywords: --------------------------------+---------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Sun Sep 22 16:23:12 2013 Return-Path: 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 2C77D21F9DBE for ; Sun, 22 Sep 2013 16:23:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 4SKHOBIrqGkV for ; Sun, 22 Sep 2013 16:23:11 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9B75621F93BF for ; Sun, 22 Sep 2013 16:23:11 -0700 (PDT) Received: from localhost ([127.0.0.1]:37401 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VNszd-0004Ie-El; Mon, 23 Sep 2013 01:23:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, tony@att.com X-Trac-Project: xml2rfc Date: Sun, 22 Sep 2013 23:23:09 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/198#comment:2 Message-ID: <080.62870f90956384ff6c76966e15507c86@tools.ietf.org> References: <065.270f26f919042693c1a1087744dfd2f1@tools.ietf.org> X-Trac-Ticket-ID: 198 In-Reply-To: <065.270f26f919042693c1a1087744dfd2f1@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.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 grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org Subject: Re: [xml2rfc] #198: Misleading "premature end of data" indication X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 23:23:12 -0000 #198: Misleading "premature end of data" indication Comment (by tony@att.com): I wouldn't be surprised if the em-dash was in a character encoding other than utf-8. -- --------------------------------+---------------------------------- Reporter: john-ietf@jck.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Resolution: | Keywords: --------------------------------+---------------------------------- Ticket URL: xml2rfc From infrastation@yandex.ru Sun Sep 22 22:20:40 2013 Return-Path: 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 7B6BB11E8186 for ; Sun, 22 Sep 2013 22:20:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.425 X-Spam-Level: ** X-Spam-Status: No, score=2.425 tagged_above=-999 required=5 tests=[AWL=0.954, BAYES_50=0.001, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875] 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 D6bBdb5O9-0h for ; Sun, 22 Sep 2013 22:20:36 -0700 (PDT) Received: from forward16.mail.yandex.net (forward16.mail.yandex.net [IPv6:2a02:6b8:0:1402::1]) by ietfa.amsl.com (Postfix) with ESMTP id BAED311E80D7 for ; Sun, 22 Sep 2013 22:20:35 -0700 (PDT) Received: from web2g.yandex.ru (web2g.yandex.ru [95.108.252.102]) by forward16.mail.yandex.net (Yandex) with ESMTP id 48972D20C53; Mon, 23 Sep 2013 09:20:31 +0400 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web2g.yandex.ru (Yandex) with ESMTP id CE8A61261632; Mon, 23 Sep 2013 09:20:30 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1379913631; bh=9KFPsBW1jACVvbs5YTkw3xpUpVccBtf2NU+wISb6IMo=; h=From:To:In-Reply-To:References:Subject:Date; b=I2L1eZsKn5/gmUyHTQwxqXKYBXr7AqzlHDJjZRVIiQ3OpQU89EhS2dXJAZu2A17/G 4Q+f2mnB6jDcqqtu45LG3uOiZa3yRcf0WpdpoSBVyErdps4iRDAI7SrtWOnaFBcSUQ KJZdDgav5v1tQKaDcrZDIMjYiaq/gHy9MsrIQqNg= Received: from broadband-46-188-49-204.2com.net (broadband-46-188-49-204.2com.net [46.188.49.204]) by web2g.yandex.ru with HTTP; Mon, 23 Sep 2013 09:20:30 +0400 From: Denis Ovsienko To: Brian E Carpenter , xml2rfc@ietf.org In-Reply-To: <523F4DE6.8030300@gmail.com> References: <523E81FF.4070904@gmail.com> <66681379835433@web3j.yandex.ru> <523F4DE6.8030300@gmail.com> MIME-Version: 1.0 Message-Id: <87321379913630@web2g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 23 Sep 2013 09:20:30 +0400 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r Subject: Re: [xml2rfc] Two issues with new version X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 05:20:40 -0000 >> �For my own input (symrefs="yes" and two EREFs in the middle of a list item each) the _old_ xml2rfc produces "[1]" and "[2]", adding an "URIs" section just after the informative references. > > That is definitely not what I see. Just checked once again, it works in the old version (the source is http://tools.ietf.org/id/draft-ovsienko-babel-hmac-authentication-03.xml). The new version doesn't generate the "URIs" section (known issue #133). I don't know if it depends on any processing directives. -- Denis Ovsienko From trac@tools.ietf.org Mon Sep 23 12:58:35 2013 Return-Path: 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 8A16121F9E01 for ; Mon, 23 Sep 2013 12:58:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 0FGfT3uaeJKE for ; Mon, 23 Sep 2013 12:58:35 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id CA9A021F9DF7 for ; Mon, 23 Sep 2013 12:58:34 -0700 (PDT) Received: from localhost ([127.0.0.1]:57767 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VOCHB-0004Wf-EK; Mon, 23 Sep 2013 21:58:33 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, arusso@amsl.com X-Trac-Project: xml2rfc Date: Mon, 23 Sep 2013 19:58:33 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/199 Message-ID: <063.7d9e761362a8ec1c1e59062c5f452564@tools.ietf.org> X-Trac-Ticket-ID: 199 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: [xml2rfc] #199: add warning about bad texttable output X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 19:58:35 -0000 #199: add warning about bad texttable output Sometimes the texttable element yields bad text output (when line breaks have been automatically inserted). v1 gives a warning when this occurs, as follows: xml2rfc: warning: so many s in that some words need to be split around input line 1032 v2 is silent, but it should give a warning so the user can change the table if needed. Example from Section 8 of the attached file. See how 394, 396, etc., appear. {{{ | 393 | flowSelectedFlowDeltaCount | 39 | selectorIDTotalFlowsObser | | | | 4 | ved | | | | | | | 395 | selectorIDTotalFlowsSelect | 39 | samplingFlowInterval | | | ed | 6 | | | | | | | | 397 | samplingFlowSpacing | 30 | samplingSize | | | | 9 | | | | | | | | 310 | samplingPopulation | 31 | samplingProbability | | | | 1 | | | | | | | | 398 | flowSamplingTimeInterval | 39 | flowSamplingTimeSpacing | | | | 9 | | | | | | | | 326 | digestHashValue | 40 | hashFlowDomain | | | | 0 | | | | | | | | 329 | hashOutputRangeMin | 33 | hashOutputRangeMax | | | | 0 | | | | | | | | 331 | hashSelectedRangeMin | 33 | hashSelectedRangeMax | | | | 2 | | | | | | | | 333 | hashDigestOutput | 33 | hashInitialiserValue | | | | 4 | | | | | | | | 320 | absoluteError | 32 | relativeError | | | | 1 | | | | | | | | 336 | upperCILimit | 33 | lowerCILimit | | | | 7 | | | | | | | | 338 | confidenceLevel | | | +-----+----------------------------+----+---------------------------+ }}} -- -----------------------------+---------------------------------- Reporter: arusso@amsl.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: minor | Milestone: Component: Version 2 cli | Version: 2.4.x Keywords: | -----------------------------+---------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Mon Sep 23 13:52:43 2013 Return-Path: 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 6B12A21F9E01 for ; Mon, 23 Sep 2013 13:52:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GfGxdV9swdu4 for ; Mon, 23 Sep 2013 13:52:40 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B086721F9DA8 for ; Mon, 23 Sep 2013 13:52:40 -0700 (PDT) Received: from localhost ([127.0.0.1]:32891 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VOD7X-0004Sq-AM; Mon, 23 Sep 2013 22:52:39 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, arusso@amsl.com X-Trac-Project: xml2rfc Date: Mon, 23 Sep 2013 20:52:39 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/200 Message-ID: <063.50cec0668844c23051eaab38ed2fcaf8@tools.ietf.org> X-Trac-Ticket-ID: 200 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: [xml2rfc] #200: in title element makes bad output in TOC X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 20:52:43 -0000 #200: in title element makes bad output in TOC When the title contains an entity, the Table of Contents contains instead of a non-breaking space. For example: XML: {{{

}}} v2 txt: {{{3. Test (Sept. Delay)}}} Should be (v1 txt): {{{3. Test (Sept. Delay)}}} ( is occasionally used as a work-around to control space; in this case to force a single space after "Sept.") -- -----------------------------+---------------------------------- Reporter: arusso@amsl.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: minor | Milestone: Component: Version 2 cli | Version: 2.4.x Keywords: | -----------------------------+---------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Mon Sep 23 14:17:28 2013 Return-Path: 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 B566421F9FC8 for ; Mon, 23 Sep 2013 14:17:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 8rWgv0YNLc3o for ; Mon, 23 Sep 2013 14:17:28 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 090B321F9E88 for ; Mon, 23 Sep 2013 14:17:28 -0700 (PDT) Received: from localhost ([127.0.0.1]:34386 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VODVQ-0006qv-Mk; Mon, 23 Sep 2013 23:17:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: arusso@amsl.com, infrastation@yandex.ru, tony@att.com, henrik@levkowetz.com X-Trac-Project: xml2rfc Date: Mon, 23 Sep 2013 21:17:19 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/115#comment:14 Message-ID: <081.2726fabe162e7341bf487ae638a38b54@tools.ietf.org> References: <066.1445983ce9e57ad5e29ee2ecd7564429@tools.ietf.org> X-Trac-Ticket-ID: 115 In-Reply-To: <066.1445983ce9e57ad5e29ee2ecd7564429@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: arusso@amsl.com, infrastation@yandex.ru, tony@att.com, henrik@levkowetz.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org Subject: Re: [xml2rfc] #115: xml2rfc 2.4.1 v2 puts two spaces after "i.e." X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 21:17:28 -0000 #115: xml2rfc 2.4.1 v2 puts two spaces after "i.e." Comment (by arusso@amsl.com): Please add "et al." to the special cases. It appears in the middle of a sentence sometimes and should have one space after the period. For example: v2 output: {{{Jones et al.[space][space]will be}}} Should be: {{{Jones et al.[space]will be}}} -- ---------------------------------+-------------------- Reporter: jonathan@vidyo.com | Owner: Type: defect | Status: closed Priority: major | Milestone: Component: Version 2 cli | Version: Resolution: fixed | Keywords: ---------------------------------+-------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Mon Sep 23 14:28:46 2013 Return-Path: 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 7E15521F9D68 for ; Mon, 23 Sep 2013 14:28:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 osBQQ0WZadTS for ; Mon, 23 Sep 2013 14:28:46 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A3E5C21F9D8D for ; Mon, 23 Sep 2013 14:28:42 -0700 (PDT) Received: from localhost ([127.0.0.1]:35205 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VODgN-0003aX-52; Mon, 23 Sep 2013 23:28:39 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: jbothun@concentricsky.com, arusso@amsl.com X-Trac-Project: xml2rfc Date: Mon, 23 Sep 2013 21:28:39 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/47#comment:2 Message-ID: <079.7bd7f8950f9a8bcafd655190ca2cae8b@tools.ietf.org> References: <064.d4783deb5c466018965c6990ca886d78@tools.ietf.org> X-Trac-Ticket-ID: 47 In-Reply-To: <064.d4783deb5c466018965c6990ca886d78@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: jbothun@concentricsky.com, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: Re: [xml2rfc] #47: when category="std", missing text in Status of This Memo X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 21:28:46 -0000 #47: when category="std", missing text in Status of This Memo Comment (by arusso@amsl.com): Seems changeset [595] should also be applied to BCPs (i.e., category="bcp"). The RFC Editor will insert the consensus="yes" in the XML file for these cases, just to be unambiguous, but it seems it's best if the default is correct (i.e., consensus="yes" when category="std" OR category="bcp") Using v2 to convert a file with category="bcp" without a consensus attribute yields bad output (a Status of This Memo option that doesn't exist). -- -------------------------------+--------------------------------------- Reporter: ahagens@amsl.com | Owner: jbothun@concentricsky.com Type: defect | Status: closed Priority: major | Milestone: Component: Version 2 cli | Version: Resolution: fixed | Keywords: -------------------------------+--------------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Mon Sep 23 15:08:00 2013 Return-Path: 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 5089E21F9DD5 for ; Mon, 23 Sep 2013 15:08:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.999 X-Spam-Level: X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_63=0.6, 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 a3YjJrcaWZ+t for ; Mon, 23 Sep 2013 15:07:59 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 8E69721F9DA8 for ; Mon, 23 Sep 2013 15:07:47 -0700 (PDT) Received: from localhost ([127.0.0.1]:37413 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VOEIC-0002c9-M5; Tue, 24 Sep 2013 00:07:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, arusso@amsl.com X-Trac-Project: xml2rfc Date: Mon, 23 Sep 2013 22:07:44 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/201 Message-ID: <063.14f94add5ae172e5021a179265141b48@tools.ietf.org> X-Trac-Ticket-ID: 201 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: [xml2rfc] #201: bug with cref element and PI inline=yes X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 22:08:00 -0000 #201: bug with cref element and PI inline=yes There are a couple issues when cref elements are used and comments="yes". XML example: {{{This point needs revision.}}} Using v1: The PI controls whether the comments are displayed inline or at the end of the document. Output when : {{{[[Q1: This point needs revision. --JD]]}}} Output when in text: {{{[Q1]}}} and at the end of the document: {{{ Editorial Comments [Q1] JD: This point needs revision. }}} --------- Using v2, the output is mangled: {{{[[: Q1This point needs revision.]]}}} * In v2, inline="yes" vs. "no" does not have any effect. Either way the comment appears inline. See attached file. * In v1, if you there's no anchor attribute, it automatically numbers them as [anchor1], [anchor2], etc. However, in v2, if you remove the anchor attribute, there is no numbering. (Seems related to inline="no" not working.) Side notes about the DTD (suggestions for a more flexible vocabulary to enable commenting on a figure): * allow cref inside figure/artwork (v1 gives warning; v2 gives error) * allow figure/artwork to contain cref (v1 gives warning; v2 gives error) -- -----------------------------+---------------------------------- Reporter: arusso@amsl.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Keywords: | -----------------------------+---------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Tue Sep 24 14:22:01 2013 Return-Path: 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 B4A9B21F9CC7 for ; Tue, 24 Sep 2013 14:21:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.544 X-Spam-Level: X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, 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 iifi10umUL2a for ; Tue, 24 Sep 2013 14:21:47 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 6B04021F9CAF for ; Tue, 24 Sep 2013 14:21:45 -0700 (PDT) Received: from localhost ([127.0.0.1]:36774 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VOa3D-0008Lp-G3; Tue, 24 Sep 2013 23:21:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, arusso@amsl.com X-Trac-Project: xml2rfc Date: Tue, 24 Sep 2013 21:21:43 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/194#comment:2 Message-ID: <078.a28c1f9039d0d2ff2e6db9d79bf9ca30@tools.ietf.org> References: <063.3304121621b15aea16c9ad2d39d4a3fe@tools.ietf.org> X-Trac-Ticket-ID: 194 In-Reply-To: <063.3304121621b15aea16c9ad2d39d4a3fe@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, arusso@amsl.com, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: Re: [xml2rfc] #194: handling of leading space in figure artwork X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2013 21:22:01 -0000 #194: handling of leading space in figure artwork Comment (by arusso@amsl.com): Right, my mistake. Clarification below. In summarizing the behavior, Tony Hansen wrote: {{{ Version 1 is consistent and predictable. Its rules were: If length <= 69, indent = 3 else if length == 70, indent = 2, warn about outdent else if length == 71, indent = 1, warn about outdent else if length == 72, indent = 0, warn about outdent else if length > 72, indent = 0, warn about excess characters output line Version 2 is consistent and predictable. Currently its rules are: indent = 3 if length > 69, warn about excess characters output line The problem is that version 1 and version 2 are different. Consequently, documents that are acceptable with v1 are not acceptable with v2. I'm told that this is particularly an issue with MIBs, which I'm also told tend to use very LONG artwork and often hit that 70-72 range. The question is which is "proper and correct" and should be the rule going forward. }}} For v1, the summary is accurate. (The question of "Is outdenting good?" was also mentioned in #129.) For v2 text output, there's an aspect that's not captured above: * If input has leading space 0-3 chars, the output has 3. (This is different from v1. See Section 2 of attached files where indented 1 space and 2 spaces.) * If input has leading space > 3 chars, the output matches the input. Another point of confusion: v2 text output does not match v2 nroff output (then made into text). This is shown in the attached file sample_lines_nroffdiff.html. -- ------------------------------+---------------------------------- Reporter: arusso@amsl.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Resolution: | Keywords: ------------------------------+---------------------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Sat Sep 28 21:57:56 2013 Return-Path: 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 C73C321F9F77 for ; Sat, 28 Sep 2013 21:57:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.549 X-Spam-Level: X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, 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 UxgjCCh1fZvJ for ; Sat, 28 Sep 2013 21:57:56 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 36B1C21F9F80 for ; Sat, 28 Sep 2013 21:57:56 -0700 (PDT) Received: from localhost ([127.0.0.1]:52347 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VQ94s-0003x3-6p; Sun, 29 Sep 2013 06:57:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: l.wood@surrey.ac.uk X-Trac-Project: xml2rfc Date: Sun, 29 Sep 2013 04:57:54 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/202 Message-ID: <067.2204184257353aaee938aa117e3c30e7@tools.ietf.org> X-Trac-Ticket-ID: 202 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: l.wood@surrey.ac.uk, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org Subject: [xml2rfc] #202: non-breaking space not honoured in table headings X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Sep 2013 04:57:56 -0000 #202: non-breaking space not honoured in table headings Very short table headings, e.g. 'Bit 11' were being broken across two lines, even though it would have been neater if they were in one line, e.g. Bit 13 output +---+ | Bit | | 13 so I attempted to use non-breaking space to keep the text together and run the heading consistently on one line: Bit 13 desired output +-----+ | Bit 13 | This non-breaking space was rendered by xml2rfc as character 160, i.e. Bit 13 . Non-breaking space and its intent should be understood and honoured by xml2rfc. Thanks! -- ---------------------------------+------------------- Reporter: l.wood@surrey.ac.uk | Owner: Type: defect | Status: new Priority: medium | Milestone: 1.37 Component: xml2rfc.tcl | Version: 2.4.x Keywords: | ---------------------------------+------------------- Ticket URL: xml2rfc From trac@tools.ietf.org Mon Sep 30 05:42:04 2013 Return-Path: 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 EACEF21F893E for ; Mon, 30 Sep 2013 05:42:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.553 X-Spam-Level: X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, 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 65rK3LqI2tcj for ; Mon, 30 Sep 2013 05:42:04 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id CCAED21F9BD3 for ; Mon, 30 Sep 2013 05:41:59 -0700 (PDT) Received: from localhost ([127.0.0.1]:53055 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1VQcnG-0003S2-Q6; Mon, 30 Sep 2013 14:41:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "xml2rfc issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: henrik@levkowetz.com, cabo@tzi.org X-Trac-Project: xml2rfc Date: Mon, 30 Sep 2013 12:41:39 -0000 X-URL: http://tools.ietf.org/tools/xml2rfc/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/151#comment:1 Message-ID: <078.33831363323bdb595e9d6cd00c393818@tools.ietf.org> References: <063.bc2b309beb252f9c656181ca730d64a1@tools.ietf.org> X-Trac-Ticket-ID: 151 In-Reply-To: <063.bc2b309beb252f9c656181ca730d64a1@tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: henrik@levkowetz.com, cabo@tzi.org, sginoza@amsl.com, xml2rfc@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: xml2rfc@ietf.org, sginoza@amsl.com Subject: Re: [xml2rfc] #151: figure handling: indentation and extraneous blank lines X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2013 12:42:05 -0000 #151: figure handling: indentation and extraneous blank lines Comment (by cabo@tzi.org): Workaround: put at least one empty (as in: not even spaces) line in the artwork element. (That then makes two spurious empty lines, but at least the indentation is consistent.) (The workaround simply defeats the faulty minimum indentation logic.) For fixing this, this logic needs to ignore empty lines and add 3 to the indentation in write_raw. To fix the spurious empty line, the call to write_label at the end of write_figure needs to be conditional on actually having a label. -- ------------------------------+---------------------------------- Reporter: arusso@amsl.com | Owner: henrik@levkowetz.com Type: defect | Status: new Priority: medium | Milestone: Component: Version 2 cli | Version: 2.4.x Resolution: | Keywords: ------------------------------+---------------------------------- Ticket URL: xml2rfc From william.atwood@concordia.ca Mon Sep 30 19:58:23 2013 Return-Path: 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 5533121F99FB for ; Mon, 30 Sep 2013 19:58:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.432 X-Spam-Level: X-Spam-Status: No, score=-0.432 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_50=0.001] 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 J6-JWp9p2XSs for ; Mon, 30 Sep 2013 19:58:17 -0700 (PDT) Received: from cyclone.public.resource.org (cyclone.public.resource.org [192.101.98.135]) by ietfa.amsl.com (Postfix) with ESMTP id CCA0F21F99F4 for ; Mon, 30 Sep 2013 19:58:17 -0700 (PDT) Received: from oldperseverance.encs.concordia.ca (root@oldperseverance.encs.concordia.ca [132.205.96.92]) by cyclone.public.resource.org (8.14.5/8.14.4) with ESMTP id r912w8x4082171 for ; Mon, 30 Sep 2013 19:58:09 -0700 (PDT) (envelope-from william.atwood@concordia.ca) Received: from [127.0.0.1] (bill@grace.encs.concordia.ca [132.205.2.217]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id r912w6On021348 for ; Mon, 30 Sep 2013 22:58:06 -0400 Message-ID: <524A3A3E.8090606@concordia.ca> Date: Mon, 30 Sep 2013 22:58:06 -0400 From: William Atwood Organization: Concordia University, Montreal User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: xml2rfc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2013/09/30 22:58:06 EDT Subject: [xml2rfc] Failure, probably when processing a "list" X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2013 02:58:23 -0000 I am attempting to build an Internet Draft from an xml file, using the current web-based processor at xml.resource.org. After resolving all of the citations, I get the error messages shown below. A copy of the input file is available if needed. Bill - - - - - - - - - - - - - - - - - WARNING: No DTD given, defaulting to /usr/local/lib/python2.7/dist-packages/xml2rfc/templates/rfc2629.dtd Traceback (most recent call last): File "/usr/local/bin/xml2rfc", line 224, in main() File "/usr/local/bin/xml2rfc", line 209, in main pagedwriter.write(filename) File "/usr/local/lib/python2.7/dist-packages/xml2rfc/writers/base.py", line 1088, in write self.post_rendering() File "/usr/local/lib/python2.7/dist-packages/xml2rfc/writers/paginated_txt.py", line 286, in post_rendering self.emit([''] * remainder) File "/usr/local/lib/python2.7/dist-packages/xml2rfc/writers/paginated_txt.py", line 164, in emit if self.page_length == 1 and text.strip() == '': AttributeError: 'list' object has no attribute 'strip' -- Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 Distinguished Professor Emeritus fax: +1 (514) 848-2830 Department of Computer Science and Software Engineering Concordia University EV 3.185 email:william.atwood@concordia.ca 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill Montreal, Quebec Canada H3G 1M8