Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schema Issue, RFC 7991, In Section 2.54, <table>

Heather Flanagan <rse@rfc-editor.org> Sat, 20 October 2018 15:55 UTC

Return-Path: <rse@rfc-editor.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 BB557130E63 for <xml2rfc-dev@ietfa.amsl.com>; Sat, 20 Oct 2018 08:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 DODzgteLIesx for <xml2rfc-dev@ietfa.amsl.com>; Sat, 20 Oct 2018 08:55:40 -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 20CEC12D4EB for <xml2rfc-dev@ietf.org>; Sat, 20 Oct 2018 08:55:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A067D1CA42E; Sat, 20 Oct 2018 08:55: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 s7cn5bMbmuP3; Sat, 20 Oct 2018 08:55:01 -0700 (PDT)
Received: from Heathers-MacBook-Pro-2.local (unknown [38.132.111.105]) by c8a.amsl.com (Postfix) with ESMTPSA id E309C1C6297; Sat, 20 Oct 2018 08:54:56 -0700 (PDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, Paul Hoffman <paul.hoffman@icann.org>
Cc: Jim Schaad <ietf@augustcellars.com>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
References: <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de> <3ac63652-2df2-03c7-eee6-bad2cbd326d8@levkowetz.com> <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org> <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com> <a9cbe9b1-1ee4-b60b-bb88-d07d11afa6a3@gmx.de> <20181004192423.xexbgomdqs56pkok@miek.nl> <5694D337-A88C-4F3E-AE2D-8EA34C3A5A93@icann.org> <20181004193939.szec4ng47kp7lapv@miek.nl> <38897ac0-44a7-6b03-4e7e-e19a115fc53d@gmx.de> <f36e6a80-99ad-fd1a-f872-9b8fc83fb763@levkowetz.com> <050c01d45d97$714e51b0$53eaf510$@augustcellars.com> <efc18e10-416f-91ae-bff5-f7ecf2721df4@levkowetz.com> <052b01d45daa$87e71980$97b54c80$@augustcellars.com> <656afb2e-3aa7-53c5-5e39-55050387aa20@levkowetz.com> <0bac2940-1abc-87e3-35e7-f6d621e83f1c@rfc-editor.org> <073e01d45ffc$fc161550$f4423ff0$@augustcellars.com> <d90ce312-8580-5509-d876-3fe889d9b125@levkowetz.com> <2061F6E4-3DF8-4C60-BB35-AB52FCD98EB1@icann.org> <4d46965d-dde8-8143-9252-739c8500fd8a@levkowetz.com>
From: Heather Flanagan <rse@rfc-editor.org>
Message-ID: <a91f0974-12b1-46d7-83f0-ac95e44efa67@rfc-editor.org>
Date: Sat, 20 Oct 2018 08:55:26 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <4d46965d-dde8-8143-9252-739c8500fd8a@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/PaVOG-0hHAHgQH4XaWxoF_rDnyY>
Subject: Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schema Issue, RFC 7991, In Section 2.54, <table>
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: Sat, 20 Oct 2018 15:55:42 -0000

On 10/19/18 8:51 PM, Henrik Levkowetz wrote:
>
> On 2018-10-20 03:33, Paul Hoffman wrote:
>> Sorry to reopen, but I'm not clear on the result. We have consensus on something, but I'm not clear how to implement it.
>>
>>
>> On Oct 9, 2018, at 11:26 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>>>
>>>
>>> On 2018-10-09 20:22, Jim Schaad wrote:
>>>>> -----Original Message-----
>>>>> From: xml2rfc-dev <xml2rfc-dev-bounces@ietf.org> On Behalf Of Heather
>>>>> Flanagan
>>>>> Sent: Tuesday, October 9, 2018 11:01 AM
>>>>> To: xml2rfc-dev@ietf.org
>>>>> Subject: Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, RFC 7991, In
>>>>> Section 2.54, <table>
>>>>>
>>>>>
>>>>> On 10/6/18 2:53 PM, Henrik Levkowetz wrote:
>>>>>> On 2018-10-06 21:26, Jim Schaad wrote:
>>>>>>>>> What is the rule you have for doing the alignment of figure
>>>>>>>>> captions? I think that the same rules should apply to both figures
>>>>>>>>> and tables.
>>>>>>>> Till now, both have been centered.  That can be changed.
>>>>>>>>
>>>>>>> No, I would not change this.  I would keep the centering for the
>>>>>>> caption.  The next interesting question the caption is wider than the
>>>>>>> table should it be wrapped to the table width or run on past the edge
>>>>>>> of the table.  I don't think that I have a preference
>>>>>> I don't (at least currently) have a strong preference.  The current
>>>>>> code wraps the title to fit within the table width.
>>>>>>
>>>>> I'm not entirely sure how this issue differs from the table alignment
>>>> discussed
>>>>> in issues 40 and 9?
>>>> The first was where do you place the table on the page.  This one is how do
>>>> you place the caption in the table.
>>> Much more succinct than my reply :-)
>> Is the result to simply add text that says "the caption will appear
>> centered", or is the result to add a new attribute such as
>> "alignCaption" with the default being "center".
> The caption will be centred under the table, and the combined table and
> caption will be aligned according to the 'align' attribute on <table>.


Yes, this.

-Heather


>
> 	Henrik
>
>> If the latter, should this same new attribute be added to <figure> as
>> well?
>>
>> --Paul
>>