Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issue, RFC 7991, New Section 2.20.4, "indent" Attribute
Jim Schaad <ietf@augustcellars.com> Sun, 07 October 2018 15:10 UTC
Return-Path: <ietf@augustcellars.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 7C895130E2F for <xml2rfc-dev@ietfa.amsl.com>; Sun, 7 Oct 2018 08:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 7eVoBF_wbfzF for <xml2rfc-dev@ietfa.amsl.com>; Sun, 7 Oct 2018 08:10:50 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 512F1130E30 for <xml2rfc-dev@ietf.org>; Sun, 7 Oct 2018 08:10:50 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 7 Oct 2018 08:06:05 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Henrik Levkowetz' <henrik@levkowetz.com>, xml2rfc-dev@ietf.org
References: <E1g6wUz-0002Cp-91@durif.tools.ietf.org> <d1acab8a-6807-5840-50e4-b96d698849dc@gmx.de> <a69fe5d2-8f76-be02-0f9d-c0e926c0b2d2@levkowetz.com> <d70281e8-fb0a-fbe8-62f6-7498d95eaf3d@levkowetz.com>
In-Reply-To: <d70281e8-fb0a-fbe8-62f6-7498d95eaf3d@levkowetz.com>
Date: Sun, 07 Oct 2018 08:10:40 -0700
Message-ID: <055101d45e4f$eab33f30$c019bd90$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQE/60/iC0oW5uFeRsGOaCY9EO+4sAJMfbGjAKtuqJsCbqsHJaYRk6vA
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/GhDhmzloRwRCqaLKhp1-XnXKRAQ>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issue, RFC 7991, New Section 2.20.4, "indent" Attribute
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: Sun, 07 Oct 2018 15:10:52 -0000
> -----Original Message----- > From: xml2rfc-dev <xml2rfc-dev-bounces@ietf.org> On Behalf Of Henrik > Levkowetz > Sent: Sunday, October 7, 2018 7:14 AM > To: xml2rfc-dev@ietf.org > Subject: Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issue, RFC 7991, New > Section 2.20.4, "indent" Attribute > > I propose closing this ticket with the following resolution: > > Add an attribute "indent" to <dl>, signifying the character indentation in > monospace rendering, and the indentation measured in en-space [1] units in > other renderings. > > If there are no objections to the resolution by EOB Monday, I'll close the ticket. > > With respect to document text, I propose the following new text under Section > 2.20. <dl>: > > --- > 2.20.4. "indent" Attribute > > Indicates the indentation to be used for the second and following > lines of item rendering (the first line starts with the term, and > is not indented). The indentation is to be interpreted as characters > for monospace renderings, and en-space units when using proportional > fonts. One en-space is assumed to be the length of 0.5 em-space in > CSS units. I think it would be fine just to use em rather than en. Also I don't think that the text needs to be written as different between monospace and proportional fonts. The width of an em is going to be font specific and is equal to a character width for monospace. If you don't do the 0.5 but just use em to start with then everything is consistant. Jim > > --- > > [1] https://en.wikipedia.org/wiki/En_(typography) > > > Best regards, > > Henrik > > > On 2018-10-01 14:39, Henrik Levkowetz wrote: > > Hi Julian, > > > > On 2018-10-01 14:09, Julian Reschke wrote: > >> On 10/1/2018 1:36 PM, henrik@levkowetz.com wrote: > >>> This captures an issue noted during implementation, also described > >>> in > >>> https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementatio > >>> n#section-3.1.4 > >>> > >>> --- > >>> New Section 2.20.4, "indent" Attribute > >>> > >>> The deprecation of the "hangIndent" attribute on <list> leaves no > >>> opportunity to control the size of the hanging indent. In some > >>> definition lists, it is desirable to have a wide indentation, in order > >>> to clearly show the terms, in other cases it is more important to allow > >>> for a larger text volume than the width of the terms would allow. > >>> > >>> Recommendation: Add an "indent" attribute on <dl> to control the size > >>> of the hanging indent. > >>> > >>> Implementation: The current version of xml2rfc does not support the > >>> attribute, but has all the underlying functions needed > >>> to apply such an attribute. Internally, an indentation > >>> is calculated based on length of the <dt> text and the > >>> settings of some of the other attributes. > >>> --- > >>> ... > >> > >> I agree that this would be useful - however we'll need to define it > >> in a way that works well with non-monospaced fonts. > > > > Agreed. > > > > What about specifying indentation as a number that would indicate > > characters in monospaced output, and en-space otherwise? >
- [xml2rfc-dev] RFC 7991 issue #39: Schema Issue, R… henrik
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #39: Schem… Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #39: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #39: Schem… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #39: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Carsten Bormann
- Re: [xml2rfc-dev] RFC 7991 issue #39: Schema Issu… Henrik Levkowetz