[rfc-i] <tt> vs HTML5
paul.hoffman at vpnc.org (Paul Hoffman) Mon, 22 February 2016 22:09 UTC
From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Mon, 22 Feb 2016 14:09:34 -0800
Subject: [rfc-i] <tt> vs HTML5
In-Reply-To: <23FA786D-ECD7-4AB6-A975-9608FF8FFC43@cisco.com>
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>
Message-ID: <64033F61-7D2C-4AA1-BEA8-4B5FFF344125@vpnc.org>
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. --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