From nobody Thu Jul 22 00:38:39 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 6BE093A3C73
 for <xml2rfc@ietfa.amsl.com>; Thu, 22 Jul 2021 00:38:37 -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, SPF_HELO_NONE=0.001, 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 lWNqYBMZWVsV for <xml2rfc@ietfa.amsl.com>;
 Thu, 22 Jul 2021 00:38:34 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de
 [IPv6:2001:638:708:32::15])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 210E13A3C72
 for <xml2rfc@ietf.org>; Thu, 22 Jul 2021 00:38:33 -0700 (PDT)
Received: from smtpclient.apple (p548dcc89.dip0.t-ipconnect.de
 [84.141.204.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GVkpF6mfRz31M0;
 Thu, 22 Jul 2021 09:38:29 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 22 Jul 2021 09:38:29 +0200
Message-Id: <8424B564-47E1-4655-98D3-D9D29D144ECB@tzi.org>
To: xml2rfc@ietf.org
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/4FbuviqR8Dhc6LiH8bUOOTRLf-M>
Subject: [xml2rfc] Outdenting sourcecode
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>,
 <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>,
 <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2021 07:38:38 -0000

When I was younger, xml2rfc outdented artwork that was too wide, giving =
us a whopping three characters more horizontal space.

I still get messages that it does, and it sometimes actually does, but =
then there are cases where it doesn=E2=80=99t.

Before I go on a goose chase: What=E2=80=99s going on here?

(I use xml generated with kramdown-rfc 1.5.2 from =
https://github.com/ietf-rats-wg/basic-yang-module/blob/master/draft-ietf-r=
ats-yang-tpm-charra.md
Yes, one can argue how wise it is to have artwork sources indented by =
four spaces and relying on xml2rfc to reduce its own indent by three so =
everything just fits, but that=E2=80=99s the way it used to work, and I =
don=E2=80=99t see how that broke.)

Gr=C3=BC=C3=9Fe, Carsten

