Re: [rfc-i] t with indent
Carsten Bormann <cabo@tzi.org> Tue, 29 December 2020 23:03 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D677A3A0C33; Tue, 29 Dec 2020 15:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, 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 Q0pjiFsvUYwm; Tue, 29 Dec 2020 15:03:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BB453A0C32; Tue, 29 Dec 2020 15:03:38 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ACE71F406D1; Tue, 29 Dec 2020 15:03:08 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id DB193F406D1 for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 15:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGgRiJL_Y0bM for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 15:03:03 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id D7CC0F406C6 for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 15:03:02 -0800 (PST)
Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4D59292dZxzyXP; Wed, 30 Dec 2020 00:03:29 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6551e660-83e3-eb1b-0ac1-bce0d15bcdad@gmx.de>
Date: Wed, 30 Dec 2020 00:03:28 +0100
X-Mao-Original-Outgoing-Id: 630975808.779617-db74dab04839e81628b8b1d38203c6e8
Message-Id: <BDBA9A94-8A40-4A50-B6E6-A229CB4A6DB6@tzi.org>
References: <CABcZeBOvxuD0pnWrkcywcKBMsd4CuCrLB4YkmDStpwh7e-SkSA@mail.gmail.com> <6551e660-83e3-eb1b-0ac1-bce0d15bcdad@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Subject: Re: [rfc-i] t with indent
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
On 2020-12-29, at 20:39, Julian Reschke <julian.reschke@gmx.de> wrote: > > The example IMHO clearly should be a <blockquote> (which will get > indentation), as it cites text from the IANA registry: In RFCXMLv2, the equivalent of an HTML blockquote was done using a <list style=“empty”>, i.e., no bullets. This idiom somehow continues into RFCXMLv3, with <ul empty=“true”>. There now *additionally* is a <blockquote> element, but in xml2rfc that generates a lot of chrome, so it is *not* equivalent. (It also has “cite” and “quotedFrom”(*) attributes.) So kramdown-rfc translates a markdown blockquote into <list style=“empty”>, which is then translated into <ul empty=“true”> by xml2frc for RFCXMLv3. You can still manually enter the new RFCXMLv3 blockquotes: <blockquote> Never argue with stupid people, they will drag you down to their level and then beat you with experience. </blockquote> And will get (xml2rfc TXT version): | Never argue with stupid people, they will drag you down to their | level and then beat you with experience. (or an “inlay” style rendering in HTML), way more heavy than the normal blockquote style. Grüße, Carsten (*) due to its HTML-based roots, kramdown-rfc doesn’t support studLyCaps attributes yet. Ouch. _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] t with indent Eric Rescorla
- Re: [rfc-i] t with indent Julian Reschke
- Re: [rfc-i] t with indent Eric Rescorla
- Re: [rfc-i] t with indent Eric Rescorla
- Re: [rfc-i] t with indent John R Levine
- Re: [rfc-i] t with indent Julian Reschke
- Re: [rfc-i] t with indent Eric Rescorla
- Re: [rfc-i] t with indent John R Levine
- Re: [rfc-i] t with indent Carsten Bormann
- Re: [rfc-i] t with indent Mark Nottingham
- Re: [rfc-i] t with indent Julian Reschke
- Re: [rfc-i] t with indent Julian Reschke