From nobody Thu Aug 1 07:15:31 2019 Return-Path: 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 4ECB1120193 for ; Thu, 1 Aug 2019 07:15:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZZIwgOlcEcsP for ; Thu, 1 Aug 2019 07:15:27 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E98012018F for ; Thu, 1 Aug 2019 07:15:27 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:58420 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1htBra-0002kC-Nk; Thu, 01 Aug 2019 07:15:27 -0700 To: Martin Thomson , xml2rfc-dev@ietf.org References: <62908E23-2FC0-4ED7-84B2-E86454020206@amsl.com> From: Henrik Levkowetz Message-ID: <043ca0bc-4d3a-b3f1-a451-2f1f320f1bb4@levkowetz.com> Date: Thu, 1 Aug 2019 16:15:10 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ESplKwRW7MjQw55T9nuqRW1p2TMmRfbXX" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, mt@lowentropy.net 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) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 14:15:29 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ESplKwRW7MjQw55T9nuqRW1p2TMmRfbXX Content-Type: multipart/mixed; boundary="JsHoXn51re2gb1PNcj7kDgjXnVM254oXb"; protected-headers="v1" From: Henrik Levkowetz To: Martin Thomson , xml2rfc-dev@ietf.org Message-ID: <043ca0bc-4d3a-b3f1-a451-2f1f320f1bb4@levkowetz.com> Subject: Re: [xml2rfc-dev] Please help review v3 files References: <62908E23-2FC0-4ED7-84B2-E86454020206@amsl.com> In-Reply-To: --JsHoXn51re2gb1PNcj7kDgjXnVM254oXb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Martin, On 2019-08-01 07:19, Martin Thomson wrote: > I've been looking at the stylesheet. Is > https://github.com/rfc-format/draft-iab-rfc-css-bis still the right > place to go for that? It looks like the issues list hasn't had any > attention in some while, despite some of the issues having been > addressed (I found and closed one). If that is the right place to > go, I'll submit a pull request with what I have. The default stylesheet in actual use is packaged with xml2rfc and maintained in the xml2rfc subversion repo, located at https://svn.tools.ietf.org/svn/tools/xml2rfc/ The stylesheet in trunk is at https://svn.tools.ietf.org/svn/tools/xml2rfc/trunk/cli/xml2rfc/data/xml2r= fc.css I'm happy to take diffs, or if you can countenance working with svn, I can make you an area for personal branches where you can check in changes for merge to trunk. Best regards, Henrik --JsHoXn51re2gb1PNcj7kDgjXnVM254oXb-- --ESplKwRW7MjQw55T9nuqRW1p2TMmRfbXX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1C8+4ACgkQTptXS4+7 FxrZ6w/+NS6ePEwgKT7k9zSkAgbfPYt7D8+i0XHgCZUsmitDDIPtgtDC/RhpVbEL gq8BYUVGZPBr9lx/KU81YbymhI+O95tbKp4XWBlFBIJlI7MSFa9gQp8nwA+o/6HU l7qaXgTSA8EIJ8S1vpU48GHYMXVmNhWp2Jd12ocPYgX5dwQgmKFdvEgrgvhzsDSe dGisMSIbV6UsCrvMeb0PaGhduCoahJBPcRl5k2PQCHhbqA0I1WV+GWvI4RabM0Sl WkKAVg1qQYZUuwM/++xIEFBDgiba0fmJeElT4CDvdgeYIRvl9NmofmXUBIQ/4hik 0DmFRZr2A5Q3K3jf/DpStWKzuAV5EbpZexXb6lX2VfRDtKOOONjleWOL9WMQhAn4 1fGzuNuKMroa4B/aXNjvp7zDDUHX9mpCjt9NXivkgmKXIdR1sggpqFfZ8cblCrTr 9zTsryce7YSzXUnjUUS+gy83ha/dhBu8xaXGcwST//1/Qs70H8n/neuxFvUPWDq5 /Y5hAgeC2AnDdFjxnb09HJb0pK7ZcJIyYGgw+RuoRJf0rrCGXvNY80i/5Eb09vWf DNRdH1fgoQ3h9o0hdQCbl42KJ9Le8IMFsfVnEHsvMUeE3gwedvLh/gLT2eSdYWy9 kVdcYZwB7FGakPbzsCsQzbnvA2SbPr03w4U1NMrVn7K4gF3z0lI= =ECHS -----END PGP SIGNATURE----- --ESplKwRW7MjQw55T9nuqRW1p2TMmRfbXX-- From nobody Fri Aug 2 13:05:36 2019 Return-Path: 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 6060C120192 for ; Fri, 2 Aug 2019 13:05:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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 qbSh3LFr2fYG for ; Fri, 2 Aug 2019 13:05:31 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20C67120059 for ; Fri, 2 Aug 2019 13:05:31 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3380E1C1365; Fri, 2 Aug 2019 13:05:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHZYS7kCcFsE; Fri, 2 Aug 2019 13:05:01 -0700 (PDT) Received: from [IPv6:2605:e000:1524:de:7d79:47d1:8d06:7eac] (unknown [IPv6:2605:e000:1524:de:7d79:47d1:8d06:7eac]) by c8a.amsl.com (Postfix) with ESMTPSA id EE9711C1358; Fri, 2 Aug 2019 13:05:00 -0700 (PDT) From: Sandy Ginoza Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Fri, 2 Aug 2019 13:05:29 -0700 References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> Cc: RFC Editor To: xml2rfc-dev@ietf.org Message-Id: <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [xml2rfc-dev] [v3] 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 20:05:35 -0000 Hi Martin, > On Jul 31, 2019, at 10:19 PM, Martin Thomson = wrote: >=20 > Hi Sandy, >=20 > I've been looking at the stylesheet. Is = https://github.com/rfc-format/draft-iab-rfc-css-bis still the right = place to go for that? It looks like the issues list hasn't had any = attention in some while, despite some of the issues having been = addressed (I found and closed one). If that is the right place to go, = I'll submit a pull request with what I have. >=20 > You can see the work in progress here: = https://martinthomson.github.io/i-d-template/sample.html and = https://martinthomson.github.io/i-d-template/sample2.html Great - thanks for working on this! I saw that Henrik provided info = about where the current CSS lives. =20 Because you=E2=80=99re looking at improving the CSS, I=E2=80=99m hoping = you will take a look at a few items our team has uncovered:=20 a) one of the things we talked about is making the RFC number stand out = somehow. Right now it=E2=80=99s getting lost and because there are no = longer page headers/footers, it=E2=80=99s the only place where the RFC = number appears. Henrik had some suggestions about how to do this, but I = don=E2=80=99t think any final decisions were made. =20 b) as you noted below, longer URLs are getting truncated by the toc in = the HTML/PDF (the text file is ok). No matter how wide I make my = screen, I can=E2=80=99t see the full URL and I can=E2=80=99t scroll = right. [Note, however: it is possible to scroll right if the window is = smaller, so that the TOC doesn=E2=80=99t appear on the right.] More = info below. There are examples of this in = https://martinthomson.github.io/i-d-template/sample.html There is another example here: = https://www.rfc-editor.org/v3test/draft-ietf-sipcore-rejected-09-LB.v2v3-s= napshot.html = https://www.rfc-editor.org/v3test/draft-ietf-sipcore-rejected-09-LB.v2v3-s= napshot.xml c) potentially add a line break after long citation tags in the = references section. =20 > In addition to the stylesheet, I have found several problems with = content. These would need changes in xml2rfc to fix. Great - thank you for reviewing and providing comments! =20 > To aid in styling, these probably need to include in the . = Viewing the html on a phone does strange things to certain elements. = For instance,
is oddly shrunken on my phone. Ok - I will pass this request along to Henrik.=20 > In the second document there are several cases of > MUST NOT > where the "NOT" needs to be under the span. Ahhh! Good point! The issue is in th XML file =E2=80=94 I=E2=80=99ll = see about updating the script for tagging the 2119 keywords updated. =20 > The first sample has empty commas in author blocks. > The first sample puts the editor's name *after* affiliation. Right - we=E2=80=99ve been discussing this with Henrik and Heather. = Currently, I believe the display changes depending on what country the = authors lists.=20 > Figure 3 in the first sample has a pilcrow after the figure, where = other figures don't. =20 Ack - I see the issue in the XML file; fixed in my copy.=20 > I see that there is a blank line for a pilcrow for all figures without = captions. This might be fixed with styling, but I haven't done that yet = as it changes the width of those images. I=E2=80=99ll ask Henrik about this one.=20 I thought I could get rid of the pilcrows using the same fix as fig 3; = it didn't work. =20 > Section 3.1 of the second sample has some very odd formatting. It has = lots of indentation of varying sizes, and some blank lines that I can't = really grok. Maybe it looks OK in text, but the HTML is hard to look = at. Agree - I think we can make this better by updating the XML a bit = differently. =20 This is part of a discussion we=E2=80=99ve having with Heather regarding = whether we need to use the seemingly right list style vs get the right = display. =20 > Tables are captioned inconsistently across both documents. I think this refers to whether or not the tables have titles = consistently?=20 For the second example, our understanding is that table numbering is = required so they could be referred to easily from other = sections/documents, but titles are not required. The original document = did not provide titles for each of the tables. We=E2=80=99ll talk to = Heather about this one - seems like we could make a recommendation in = the Style Guide.=20 In the first example, we missed a title when converting the artwork to = tables. Great catch! =20 > The contributors section in both documents looks terrible in HTML. = Probably because there is no defined way to add contributors in a way = that renders in a manner consistent with authors in text formats, so the = authors choose to use 
/ for that section.  We need to fix =
that somehow.

Right - that was the only way we could get the info to display similar =
to Authors=E2=80=99 Addresses. =20
We will discuss this.


> Not sure whether this is a styling issue, but refusing to wrap links =
does odd things like add horizontal scrolling on narrow screens.

We asked Henrik about this one; he believes it=E2=80=99s a styling issue =
because the formatter should not be breaking the URLs.  Please let us =
know if you disagree.=20



> The script for managing the ToC on a narrow screen is much more =
complex than it needs to be.  Here is what I did:

I had not looked at the HTML on a small device, so I=E2=80=99m not sure =
how bad the display was previously.  I looked at your samples on my =
phone, and the ToC handling looks good. =20


Again, thanks for your input! =20

Sandy=20

>=20
> 
>=20
> with styles to support that:
> #toc nav { display: none; } /*already present*/
> #toc.active nav { display: block; }
>=20
>=20
> On Thu, Jul 18, 2019, at 16:19, Sandy Ginoza wrote:
>> Hi all,
>>=20
>> As you know, the transition to XMLv3 is quickly approaching.  As part=20=

>> of our preparation, the RPC is  converting some XMLv2 files to XMLv3. =
=20
>> We=E2=80=99re hoping some of you will take the time to review the =
files and=20
>> provide feedback regarding whether the updates are as expected and =
the=20
>> XMLv3 files are considered =E2=80=9Cgood=E2=80=9D v3 files. =20
>>=20
>> A couple of notes:
>> - we focused on format only; we did not make editorial updates.=20
>> - the diff files compare the initial v2v3 output with the files we =
edited.
>>=20
>> Please review the following files:
>>=20
>> 1) draft-ietf-spring-segment-routing-msdc
>> https://www.ietf.org/id/draft-ietf-spring-segment-routing-msdc-11.txt
>>=20
>> =
https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-1=
1-MS.v2v3.html
>> =
https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-1=
1-MS.v2v3.pdf
>> =
https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-1=
1-MS.v2v3.txt
>> =
https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-1=
1-MS.v2v3.xml
>>=20
>> rfc-xmldiff:
>> =
https://www.rfc-editor.org/v3test/draft-ietf-spring-segment-routing-msdc-1=
1-MS.v2v3-xmldiff.html
>>=20
>> htmlwdiff:
>> =
file:///Volumes/rfcpa/inc-work/v3test/draft-ietf-spring-segment-routing-ms=
dc-11-MS.v2v3-htmlwdiff.html
>>=20
>>=20
>> 2) draft-ietf-isis-l2bundles
>> https://www.ietf.org/id/draft-ietf-isis-l2bundles-07.txt
>>=20
>> Please pay particular attention to lists and the use of