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

Henrik Levkowetz <henrik@levkowetz.com> Wed, 07 August 2019 11:51 UTC

Return-Path: <henrik@levkowetz.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 04B2A1206DC for <xml2rfc-dev@ietfa.amsl.com>; Wed, 7 Aug 2019 04:51:44 -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 IKr43EiXoDT4 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 7 Aug 2019 04:51:42 -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 9098A1206D7 for <xml2rfc-dev@ietf.org>; Wed, 7 Aug 2019 04:51:42 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:54228 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1hvKTl-0000VL-5k; Wed, 07 Aug 2019 04:51:41 -0700
To: Martin Thomson <mt@lowentropy.net>, xml2rfc-dev@ietf.org
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <20c39303-312c-bb75-338a-6e46f69bba9e@levkowetz.com> <11bb5b7c-e839-475b-9ffc-a7f6bc55e9f6@www.fastmail.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <e8544a75-38a9-0fd7-94bb-fdb36fd9c934@levkowetz.com>
Date: Wed, 07 Aug 2019 13:51:33 +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: <11bb5b7c-e839-475b-9ffc-a7f6bc55e9f6@www.fastmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="vr8MN3Aog698Bo7PgnRHsxoViEJPE3vMR"
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: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/CFS1R58IWLW7MtLSSN_WeD2oOws>
Subject: Re: [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." <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: Wed, 07 Aug 2019 11:51:44 -0000

Hi Martin,

On 2019-08-07 05:13, Martin Thomson wrote:
> On Wed, Aug 7, 2019, at 07:03, Henrik Levkowetz wrote:
>> These figures are plain artwork. I've tested adding this CSS after the
>> a.pilcrow {} stanza:
>> 
>>  .artwork .pilcrow {
>>  float: right;
>>  }
>> 
>> and moving the pilcrow up before the <pre>; that gives a pilcrow to the
>> right of the artwork, without reducing the artwork width. Would that
>> work for you?
> 
> What I did instead (and you can see that here:
> https://martinthomson.github.io/i-d-template/sample2.html#section-appendix.a-26)
> is make <pre> outside of <figure> use inline-block. I'd use flexbox,
> but apparently that isn't available.

Right.

However, it seems to me that this will make the bare <artwork> narrower than
figure artwork, which is a concern.

> There's lots of reasons not to use float

What are those?  Modern style frameworks like bootstrap 4 uses float to good
effect, and I seem to remember that when float was introduced it was hailed
as a good thing.

>, and keeping the pilcrow
> after the paragraph is better from a content-model perspective.

You'll have to say more to give me a sense of why it's actually better?

I'll agree that a placement at the end matches user expectancy better, but
that's of course hard if you don't want it floating right, and don't want
the blank line.


	Henrik