[rfc-i] <tt> vs HTML5
paul.hoffman at vpnc.org (Paul Hoffman) Sat, 20 February 2016 16:51 UTC
From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Sat, 20 Feb 2016 08:51:42 -0800
Subject: [rfc-i] <tt> vs HTML5
In-Reply-To: <56C8966F.3050102@gmx.de>
References: <56C84484.2000902@gmx.de>
<DE3016C2-86EA-4019-9D00-DF585DFB90D4@vpnc.org> <56C8966F.3050102@gmx.de>
Message-ID: <9D53D262-B079-49B1-BDEF-63882E9703DF@vpnc.org>
On 20 Feb 2016, at 8:38, Julian Reschke wrote:
> On 2016-02-20 17:29, Paul Hoffman wrote:
>> On 20 Feb 2016, at 2:48, Julian Reschke wrote:
>>
>>> <https://tools.ietf.org/html/draft-iab-html-rfc-02#section-9.63>:
>>>
>>>> 9.63. <tt>
>>>>
>>>> This element is directly rendered as its HTML counterpart.
>>>
>>> but
>>> <https://www.w3.org/TR/html5/obsolete.html#non-conforming-features>:
>>>
>>> So that's a requirement to produce invalid HTML...
>>
>> We could easily fix this by getting rid of <tt> in the XML and
>> replace
>> it with <kbd>. Given that <tt> isn't in the v2 grammar, this change
>> seems easy.
>
> Well, replacing it with <kbd> wouldn't be sufficient, because not all
> cases of <tt> would be valid uses of <kbd>.
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.
--Paul Hoffman
- [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