[rfc-i] <tt> vs HTML5

julian.reschke at gmx.de (Julian Reschke) Mon, 22 February 2016 22:15 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Mon, 22 Feb 2016 23:15:04 +0100
Subject: [rfc-i] <tt> vs HTML5
In-Reply-To: <64033F61-7D2C-4AA1-BEA8-4B5FFF344125@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> <56C8B772.7000007@gmail.com> <23FA786D-ECD7-4AB6-A975-9608FF8FFC43@cisco.com> <64033F61-7D2C-4AA1-BEA8-4B5FFF344125@vpnc.org>
Message-ID: <56CB8868.5090109@gmx.de>

On 2016-02-22 23:09, Paul Hoffman wrote:
> On 22 Feb 2016, at 9:55, Joe Hildebrand (jhildebr) wrote:
>
>> <sourcecode> can also be used inline in a bunch of places.
>>
>> I agree that if <tt> remains in v3 XML, the HTML doc has to change.
>
> It seems like the easiest change that will still encompass most use
> cases is to leave <tt> as-is in the v3 spec and to change the HTML
> formatting spec to say that <tt> in the XML is rendered as <code> in the
> HTML.

Hm, from 
<https://www.w3.org/TR/html5/text-level-semantics.html#the-code-element>:

> The code element represents a fragment of computer code. This could be an XML element name, a file name, a computer program, or any other string that a computer would recognize.

Does this cover all cases we need?

IMHO, the simplest possible fix still is to use <span> with appropriate CSS.

Best regards, Julian