Re: [xml2rfc-dev] Please help review v3 files

Tom Pusateri <pusateri@bangj.com> Tue, 13 August 2019 21:47 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9D31208E7 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 13 Aug 2019 14:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
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 oxm-JvPJ78yV for <xml2rfc-dev@ietfa.amsl.com>; Tue, 13 Aug 2019 14:47:27 -0700 (PDT)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E95D91208C2 for <xml2rfc-dev@ietf.org>; Tue, 13 Aug 2019 14:47:26 -0700 (PDT)
Received: from [172.16.10.104] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id B9AB132372; Tue, 13 Aug 2019 17:47:25 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1565732846; bh=Sov1Rw1/NKW92xzl5fvoPDeM9n3A72nwpYx16APWyIQ=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=PL0fe6WImN2QUKAB5RENgJKFUNG7LHnsZ6UKZYD5r6ZH2eyHCou+17NJbL7pJDImR kXxeu4+zXMyv3I9zU4VziIB6aOKF4/me49VFNlDsuAoxxmZ6s1ITR8nC2vZALQ/+BT m0GRxm+DBlZerUshJ2MKenxLd9AgWuqF/gfwlENmgeDMWNuYrEPEmLN6KIbBFbSNB+ RpIvFOBL15wfZpp+JkDj7GzJd/TrfL220NuUHRnbqZCeKzdtSET/kM31CBhcFK2cdO cKnBmwo5H5jeADmGlXDdKHlprmQCmhnrTib28qfYi2nmcJ7ASR8AfVKNnd2kekGL2T 5P+C5Y+pe9fnw==
From: Tom Pusateri <pusateri@bangj.com>
Message-Id: <10E0A35E-DE66-4938-9037-F0C319172DBE@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B38132DC-7562-43CF-8EC9-36D980E721AC"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3570.1\))
Date: Tue, 13 Aug 2019 17:47:25 -0400
In-Reply-To: <F39EC291-7E37-49B4-831D-34BC42BBF092@amsl.com>
Cc: Carsten Bormann <cabo@tzi.org>, xml2rfc-dev@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
To: Sandy Ginoza <sginoza@amsl.com>
References: <62908E23-2FC0-4ED7-84B2-E86454020206@amsl.com> <3FA7D490-1D84-4E70-B3D0-997F3AF4F2C5@tzi.org> <F39EC291-7E37-49B4-831D-34BC42BBF092@amsl.com>
X-Mailer: Apple Mail (2.3570.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/8Yfurl5tJT2frMSeCgVotTYB8vw>
Subject: Re: [xml2rfc-dev] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2019 21:47:30 -0000

This is looking slightly better to me (without knowing what to look at).

The Section 6.7 of RFC6550 links now go to https://www.rfc-editor.org/info/rfc6550#section-6.7 <https://www.rfc-editor.org/info/rfc6550#section-6.7>

This almost works. If they instead went to https://www.rfc-editor.org/rfc/rfc6550#section-6.7 <https://www.rfc-editor.org/rfc/rfc6550#section-6.7>, they would work.

The table of contents still disappears when you select it and scroll down on it on an iPhone. This is the same for vertical mode on an iPad. In horizontal mode on an iPad, it seems to work ok.

Links require hitting them twice on an iPhone or iPad but not on a mac with Safari (internal or external). The first time you hit them, a paragraph symbol shows up at the end of the line, the second time you hit them, the link responds.

Have you tried any documents with SVG as an alternate to ASCII art?

Thanks,
Tom


> On Aug 13, 2019, at 5:24 PM, Sandy Ginoza <sginoza@amsl.com> wrote:
> 
> Hi all,
> 
> We have recreated files using the newest release of xml2rfc.  We believe this addresses the issue with the TOC on small devices - please review.  
> 
> Note that there is still an issue with handling of “see Section N of [YYYY]”.
> 
> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.v24.html> 
> 
> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.v24.html> 
> 
> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.v24.html>
> 
> https://www.rfc-editor.org/v3test/draft-ietf-roll-efficient-npdao-15-RE.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-roll-efficient-npdao-15-RE.v2v3.v24.html>
> 
> https://www.rfc-editor.org/v3test/draft-ietf-sipcore-rejected-09-LB.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-sipcore-rejected-09-LB.v2v3.v24.html> 
> 
> https://www.rfc-editor.org/v3test/draft-ietf-lamps-pkix-shake-15-RV.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-lamps-pkix-shake-15-RV.v2v3.v24.html> 
> 
> https://www.rfc-editor.org/v3test/draft-ietf-lisp-introduction-13-MS.v2v3.v24.html <https://www.rfc-editor.org/v3test/draft-ietf-lisp-introduction-13-MS.v2v3.v24.html> 
> 
> FYI - the full set of files (i.e., xml, html, pdf, txt) is available; just change the file extension.  
> 
> Thank you,
> Sandy 
> 
> 
> 
>> On Jul 18, 2019, at 12:23 AM, Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
>> 
>> The HTML form has an intrusive tablet of contents that is hiding a third of each line, is hard to get rid of, and that reappears on the slightest scrolling.  The page is essentially unusable.  (Viewed on an iPhone)
>> 
>> Sent from mobile
>> 
>> On 18. Jul 2019, at 08:19, Sandy Ginoza <sginoza@amsl.com <mailto:sginoza@amsl.com>> wrote:
>> 
>>> Hi all,
>>> 
>>> As you know, the transition to XMLv3 is quickly approaching.  As part of our preparation, the RPC is  converting some XMLv2 files to XMLv3.  We’re hoping some of you will take the time to review the files and provide feedback regarding whether the updates are as expected and the XMLv3 files are considered “good” v3 files.  
>>> 
>>> A couple of notes:
>>> - we focused on format only; we did not make editorial updates. 
>>> - the diff files compare the initial v2v3 output with the files we edited.
>>> 
>>> Please review the following files:
>>> 
>>> 1) draft-ietf-spring-segment-routing-msdc
>>> https://www.ietf.org/id/draft-ietf-spring-segment-routing-msdc-11.txt <https://www.ietf.org/id/draft-ietf-spring-segment-routing-msdc-11.txt>
>>> 
>>> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.html <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.html>
>>> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.pdf <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.pdf>
>>> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.txt <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.txt>
>>> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.xml <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3.xml>
>>> 
>>> rfc-xmldiff:
>>> https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3-xmldiff.html <https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3-xmldiff.html>
>>> 
>>> htmlwdiff:
>>> file:///Volumes/rfcpa/inc-work/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3-htmlwdiff.html <file:///Volumes/rfcpa/inc-work/v3test/draft-ietf-spring-segment-routing-msdc-11-MS.v2v3-htmlwdiff.html>
>>> 
>>> 
>>> 2) draft-ietf-isis-l2bundles
>>> https://www.ietf.org/id/draft-ietf-isis-l2bundles-07.txt <https://www.ietf.org/id/draft-ietf-isis-l2bundles-07.txt>
>>> 
>>> Please pay particular attention to lists and the use of <aside>.  We experimented with list styles and used <aside> for notes.  Using <aside> in this way required some changes because <aside> can’t be used within lists.  
>>> 
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.html <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.html>
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.pdf <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.pdf>
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.txt <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.txt>
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.xml <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.v2v3.xml>
>>> 
>>> rfc-xmldiff:
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.orignal.v2v3-xmldiff.html <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.orignal.v2v3-xmldiff.html>
>>> 
>>> htmlwdiff:
>>> https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.orignal.v2v3-htmlwdiff.html <https://www.rfc-editor.org/v3test/draft-ietf-isis-l2bundles-07-SG.orignal.v2v3-htmlwdiff.html>
>>> 
>>> 
>>> Thanks for your help!
>>> Sandy
>>> 
>>> _______________________________________________
>>> xml2rfc-dev mailing list
>>> xml2rfc-dev@ietf.org <mailto:xml2rfc-dev@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/xml2rfc-dev <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>
>>> 
>>> 
> 
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev