[xml2rfc] Conversion issues with new xnl2rfc

Yaacov Weingarten <wyaacov@gmail.com> Mon, 29 April 2013 19:21 UTC

Return-Path: <wyaacov@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA2321F9BD3 for <xml2rfc@ietfa.amsl.com>; Mon, 29 Apr 2013 12:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 kgXQUGWfSkzx for <xml2rfc@ietfa.amsl.com>; Mon, 29 Apr 2013 12:21:06 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5509021F9BCD for <xml2rfc@ietf.org>; Mon, 29 Apr 2013 12:21:05 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id c10so3172319wiw.14 for <xml2rfc@ietf.org>; Mon, 29 Apr 2013 12:21:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=aBbKQUR05QJrm8Y1SY/psMbbF+Ub8VLexJRgBnGFrIc=; b=OPYRkg5ZUkj2+YEOS1w/DKsWJNOkpb7aUviPGrB0OYsQGh3AvASM6VMWg3uMNRvU/H fgU3cGgeCZ03PSgxBmxQGChfG6dryvqfoMW57KITD1oYa1wr4kEvhZdgMUrQsJkFXEef Vag9SuaqJ2DY3pJ7WU/fEs9qIrwKNTNpRAiCb8o/jWhtLeU/fMHc5IaNwYwUDHVAIVzO zSzosDPUCtZ6JRy1AoFvMnZmZxfR2VBQIxYcUSj236ZPDbSVeEsissiec7Yw0bOe4kkk VYkpXcN1UV9G2T2fo5KlvZwoldu7j2TP4bgeLcXVcUBxsaqCXrA+CfpcH7j2ULamkkza VwMw==
MIME-Version: 1.0
X-Received: by 10.180.189.41 with SMTP id gf9mr10085306wic.32.1367263261870; Mon, 29 Apr 2013 12:21:01 -0700 (PDT)
Received: by 10.194.85.229 with HTTP; Mon, 29 Apr 2013 12:21:01 -0700 (PDT)
Date: Mon, 29 Apr 2013 22:21:01 +0300
Message-ID: <CAM0WBXXMoWTMB8a4tg+TqqF79MNf+1oBnZOyGFyg8F==kiDf6g@mail.gmail.com>
From: Yaacov Weingarten <wyaacov@gmail.com>
To: xml2rfc@ietf.org
Content-Type: multipart/mixed; boundary="001a11c3483009d08c04db84c993"
Subject: [xml2rfc] Conversion issues with new xnl2rfc
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 19:21:07 -0000

Hi,

I am attaching three files for your consideration.
1. draft-ietf-mpls-tp-ring-protection-06.xml - This is an XML version of a
draft that I am converting to text format.

2. draft-ietf-mpls-tp-ring-protection-06.txt - This is the resulting TXT
file from the older xml2rfc tool.

3. draft-ietf-mpls-tp-ring-protection-06-NEW.txt - This is the resulting
TXT file from the new (beta) version of xml2rfc tool.

I would like to point out the following differences in the output that I
observed:
1. In the author list - I do not have any company affiliation, and while in
the older version tool this resulted in a blank line after my name, in the
newer version this blank line is omitted, giving the impression that I work
for Cisco.  I might note that this anomaly was reported earlier and
according to the mailing list was marked as "solved"!

2. Whereas the old version seems to have a definition to keep figures
together on one page (as can be seen in Figure 6 that is pushed over to the
next page rather than break it across the pages), the new version has a
tendency to break them across page boundaries - as can be seen in Figures 3
& 4.

3. The table that is defined in the XML file at line 1029 is displayed
properly in the old version txt file (starting at line 1068) but the
columns lost their alignment in the new version (starting at line 1012).

4. There are two tables defined in the XML file at lines 959 and 966 that
were designed to give the impression that there are two (centered)
preambles to the data.  This worked fine with the old version (line 1012),
but extra lines are added in the new version (line 957) slightly ruining
the effect.

5. There are two instances where a table is broken across page breaks in
the new version that are not broken in the old version. Although this may
just be an accumulation of the different number of lines per page in the
new version file and not by design.

I would appreciate receiving your feedback, not through the mailing list as
I am not subscribed.

Thanx and BR,
yaacov weingarten

-- 
Thanx and BR,
yaacov

*Still looking for new opportunity*



-- 
Thanx and BR,
yaacov

*Still looking for new opportunity*