Re: [netmod] artwork folding: dual support modes?

Kent Watsen <kent+ietf@watsen.net> Mon, 04 March 2019 21:28 UTC

Return-Path: <010001694a9bd6f5-87034dff-c252-4e16-8028-f38e9184d2da-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B00131186 for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 13:28:44 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 nMd_VzkXoz4y for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2019 13:28:42 -0800 (PST)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6C4E131199 for <netmod@ietf.org>; Mon, 4 Mar 2019 13:28:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1551734921; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=NzUhs0zfeeVJoI/GczXdHTtuQccSG6CdDluhwFv+qgc=; b=AFrf58qdWrZ5zid+zwM2jV9ywkTmjf9Xp+eidFKFkG5s0uGIBeP6JDN+BsSBclcU dsiKhSmNv3B+oKQql0m1Rufxi0TuQEkIgss+ItY3krp6EHedRKk/43PpFQ6+hfrZudj 9V1zlqnXPg5fJk2HupIKJAxiJLNLXzTVVeAW/Gq0=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <20190304.193540.1020759172873811211.mbj@tail-f.com>
Date: Mon, 04 Mar 2019 21:28:41 +0000
Cc: rwilton@cisco.com, netmod@ietf.org
Content-Transfer-Encoding: 7bit
Message-ID: <010001694a9bd6f5-87034dff-c252-4e16-8028-f38e9184d2da-000000@email.amazonses.com>
References: <0100016949647f53-8a4d372a-c576-4489-a1e5-b885c6510a1f-000000@email.amazonses.com> <20190304.170423.167423260282534149.mbj@tail-f.com> <0100016949d802d6-ccf713c5-df75-4f24-b479-4bc94b4138ec-000000@email.amazonses.com> <20190304.193540.1020759172873811211.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.03.04-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/vrVFxAqt5TdD1hzXgZVs5TjjmtE>
Subject: Re: [netmod] artwork folding: dual support modes?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2019 21:28:51 -0000


>> Now that IETF has officially moved to XML as the sole format
> 
> I'm not sure what you mean, can you provide a pointer?  AFAICT, the
> latest published RFC is still only available as txt and pdf.

I meant that XML is the sole *input* format, per RFC 7990, but you're
right about the XML not currently being easily accessed.   I've signed
up for the IETF 104 CodeSprint to fix this, as well as to introduce
folding support into the publishing process.


>> No, there are cases where this fails.  We went thru this before.
> 
> Only if you have data with > 69 spaces in a row that needs to be
> preserved.

More generally, anytime the fold occurs where space characters
follow.  

But why are you arguing for this? - the double-backslash approach
works great for when indents are desired.   

My interest in this thread was/is only to cover the common case 
when there are no indents, and the continuation line always begins
on column 1, in which case the 2nd backslash is unneeded and 
somewhat counterintuitive.

Kent // contributor