Re: [xml2rfc] Indenting a <dl>

Robert Sparks <rjsparks@nostrum.com> Wed, 17 May 2023 12:48 UTC

Return-Path: <rjsparks@nostrum.com>
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 51FC1C15199D for <xml2rfc@ietfa.amsl.com>; Wed, 17 May 2023 05:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level:
X-Spam-Status: No, score=-1.676 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pckxZYvmUoB for <xml2rfc@ietfa.amsl.com>; Wed, 17 May 2023 05:48:00 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B655AC151096 for <xml2rfc@ietf.org>; Wed, 17 May 2023 05:48:00 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 34HClp5b093108 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 17 May 2023 07:47:52 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1684327674; bh=V34M7OwCq+ROXiZSp0/QKnwy++HreVGcp+ogonEAQm8=; h=Date:Subject:To:References:From:In-Reply-To; b=Rn6pgRWeZoaMb4/gTW7y9wDOhNRtvRc7CxHim1PAL4fyMX+rpxHZQu41WSFXHdA3z 0IKeAlFICcQg1PfZa1K4rvazTaxMe0h7OGX3hEJHnjBIC3UZiAD8I+HYMJubdjxrRC Zv+IhM2EIa+vEgr0RF7NJB5vTd92AeyD103e/4jI=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <6a1f2f34-615d-0dc5-c451-10fada03d1a1@nostrum.com>
Date: Wed, 17 May 2023 07:47:46 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: Robert Moskowitz <rgm@htt-consult.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <b644493a-cce5-05f1-88a8-8ee200fc20dc@htt-consult.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <b644493a-cce5-05f1-88a8-8ee200fc20dc@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/kF16B0pWjN7QGzoHqDyvsutzamM>
Subject: Re: [xml2rfc] Indenting a <dl>
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 17 May 2023 12:48:04 -0000

On 5/17/23 7:37 AM, Robert Moskowitz wrote:
> I have a <dl> block that I want indented.
>
> I do not see in rfc7991 or xml2rfc FAQ any attribute to add to <dl> 
> for indenting.  Like no margin attribute.
>
> I tried putting it in a <blockquote>, but that tosses | at the 
> beginning of each line, and I don't see how to turn that off.
>
> I tried putting the <dl> in a <ul> and that is not allowed.
>
> So how do I indent a <dl> list?

There is no good way at the moment. See 
https://github.com/ietf-tools/xml2rfc/issues/990 and the discussion of 
current workarounds at https://github.com/ietf-tools/xml2rfc/issues/985

RjS

>
> thanks
>
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc