IETF Logo Mail Archive

Re: [Xml-sg-cmt] <contact> Fwd: AUTH48 [LB]: RFC 9147 <draft-ietf-tls-dtls13-43.txt> NOW AVAILABLE

Sandy Ginoza <sginoza@amsl.com> Wed, 05 January 2022 18:23 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94143A09AF for <xml-sg-cmt@ietfa.amsl.com>; Wed, 5 Jan 2022 10:23:01 -0800 (PST)
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 UKLfTPc0Haxr for <xml-sg-cmt@ietfa.amsl.com>; Wed, 5 Jan 2022 10:22:57 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995313A09AD for <xml-sg-cmt@ietf.org>; Wed, 5 Jan 2022 10:22:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 88A61425C152; Wed, 5 Jan 2022 10:22:57 -0800 (PST)
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 iW6BwkLCCWYx; Wed, 5 Jan 2022 10:22:57 -0800 (PST)
Received: from smtpclient.apple (2603-8000-9603-b513-fc9f-a7ef-6508-ad49.res6.spectrum.com [IPv6:2603:8000:9603:b513:fc9f:a7ef:6508:ad49]) by c8a.amsl.com (Postfix) with ESMTPSA id 5592E424B435; Wed, 5 Jan 2022 10:22:57 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <4f44ee3f-7535-2e07-a56e-c855c2d8d8c9@taugh.com>
Date: Wed, 05 Jan 2022 10:22:55 -0800
Cc: Peter Saint-Andre <stpeter@mozilla.com>, XML weed whackers <xml-sg-cmt@ietf.org>, Lynne Bartholomew <lbartholomew@amsl.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <64547590-6ED5-47E1-99BF-262CC72393B0@amsl.com>
References: <CABcZeBMA2HmaozuYGWp5YJ=M+r7HsDrbRykxdsyYamvXtr=Tbg@mail.gmail.com> <ACCBB6F2-5A9B-4271-895F-B36A82FF2F6E@amsl.com> <93565a8e-8b32-bcfb-89d2-42d23ba63527@taugh.com> <4a5ae15e-012f-c194-1086-45274ff8d14b@mozilla.com> <45e09907-ffd7-5d14-ad64-ac712ecb60d4@taugh.com> <1298e8af-b692-323f-a602-e0ecc7506463@mozilla.com> <4f44ee3f-7535-2e07-a56e-c855c2d8d8c9@taugh.com>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/EzJg-rC9CdH7EVAtxjOIHflyxoM>
Subject: Re: [Xml-sg-cmt] <contact> Fwd: AUTH48 [LB]: RFC 9147 <draft-ietf-tls-dtls13-43.txt> NOW AVAILABLE
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2022 18:23:02 -0000


> On Jan 5, 2022, at 9:20 AM, John R Levine <johnl@taugh.com> wrote:
> 
> On Wed, 5 Jan 2022, Peter Saint-Andre wrote:
>>>> Just curious: why does the extra space appear in the first place?
>>> It's just a wart of the way the XML renders into text.  It looks fine in the HTML and PDF.
>> 
>> If it really matters to an author, can this be adjusted by hand before publication?
> 
> Only by a hack like <artwork>, so no.

I would strongly prefer not to do any updates to the XML or output files after the prep tool has been run.  It would make it rerendering more difficult.  


> Remember that the txt is a non-canonical rendering of the XML.  If people desperately want less whitespace in the TXT rendering, I suppose we could open a ticket and ask for the rendering to squish the whitespace.  Or we could ask people to visit the 21st century and take a look at the HTML version.
> 
> I really do not have any interest in trying to replicate the formatting of decade old txt documents.

I don’t think a change is needed because this is the only complaint we’ve received about the spacing (that I am aware of).  
If this issue is wider and change is needed, I lean toward removing the space in the contributors and authors sections so it’s more consistent with the HTML and PDF.  

Thanks,
Sandy 

> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>

v2.23.0 | Report a Bug | By Email