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

Carsten Bormann <cabo@tzi.org> Tue, 13 August 2019 22:00 UTC

Return-Path: <cabo@tzi.org>
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 EF3E11208C2 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 13 Aug 2019 15:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 fwESuttDXvRq for <xml2rfc-dev@ietfa.amsl.com>; Tue, 13 Aug 2019 15:00:56 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19EA21208E6 for <xml2rfc-dev@ietf.org>; Tue, 13 Aug 2019 15:00:56 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 467RVY713xzyX8; Wed, 14 Aug 2019 00:00:53 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <F39EC291-7E37-49B4-831D-34BC42BBF092@amsl.com>
Date: Wed, 14 Aug 2019 00:00:53 +0200
Cc: xml2rfc-dev@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 587426452.12585-00ecc968a199e4e04c70677437374033
Content-Transfer-Encoding: quoted-printable
Message-Id: <2003815F-1C65-4A6D-831F-2E02A418BABC@tzi.org>
References: <62908E23-2FC0-4ED7-84B2-E86454020206@amsl.com> <3FA7D490-1D84-4E70-B3D0-997F3AF4F2C5@tzi.org> <F39EC291-7E37-49B4-831D-34BC42BBF092@amsl.com>
To: Sandy Ginoza <sginoza@amsl.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/g5-sIqD6vMXZdXeLznP6nZ_UZBo>
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 22:00:58 -0000

On Aug 13, 2019, at 23:24, 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.  

Indeed, much better.

A few quick observations on iOS/Safari (all about the styling, which may be an indication that the XML structure works):

The first click on an internal/literature reference link adds a pilcrow to the paragraph if it didn’t have one yet (this is also true of the TOC).  The second click then advances to the linked reference, the first line of which is sometimes obscured by the TOC menu (if not, scrolling is needed to get the TOC menu again, but that is kind of OK).

How do you add a pilcrow to a paragraph that doesn’t have a reference?

Some horizontal scrolling is needed to view a box notation artwork of more than 18 bits (37 columns).  This is a bit more complicated because both the artwork and the entire document scroll horizontally, so the result is somewhat non-deterministic.  (This is also sometimes true of long headings; I haven’t found a way to reproduce this — maybe it was the smart sizing feature of iOS Safari.)  It would be better to nail down the document so only the artwork needs to scroll horizontally.  I also don’t know why the document text is sometimes wider than the viewport.

Going to landscape just increases the font size and doesn’t help with the artwork.

Grüße, Carsten