[rfc-i] <tt> vs HTML5
brian.e.carpenter at gmail.com (Brian E Carpenter) Sat, 20 February 2016 18:58 UTC
From: brian.e.carpenter at gmail.com (Brian E Carpenter)
Date: Sun, 21 Feb 2016 07:58:58 +1300
Subject: [rfc-i] <tt> vs HTML5
In-Reply-To: <9D53D262-B079-49B1-BDEF-63882E9703DF@vpnc.org>
References: <56C84484.2000902@gmx.de>
<DE3016C2-86EA-4019-9D00-DF585DFB90D4@vpnc.org> <56C8966F.3050102@gmx.de>
<9D53D262-B079-49B1-BDEF-63882E9703DF@vpnc.org>
Message-ID: <56C8B772.7000007@gmail.com>
On 21/02/2016 05:51, Paul Hoffman wrote:
...
> What do you mean by "all cases of <tt>"? It is currently defined as:
> Causes the text to be displayed in a constant-width font.
> This element can be combined with other character formatting elements, and the
> formatting will be additive.
And this is IMHO not an aesthetic issue in our context. It's a technical
requirement - we want certain text in rendered RFCs to be rendered in a
constant-width font. I think we should be able to express that without
being forced into a purist view of the distinction between semantics and
presentation. Constant-width font *is* the semantic, if you like.
How it is rendered in HTML is a separate matter.
Brian
P.S. /tt was originally defined in LaTeX as "typewriter" style (a bit
unfair on some typewriters) and the comment in RFC1866 is
<!-- <TT> Typewriter text -->
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Carsten Bormann
- [rfc-i] <tt> vs HTML5 Riccardo Bernardini
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Carsten Bormann
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Brian E Carpenter
- [rfc-i] <tt> vs HTML5 Joe Hildebrand jhildebr
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke