This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23645 - "formal way" to indicate the computing language for <code>, <samp> and possibly <var>
Summary: "formal way" to indicate the computing language for <code>, <samp> and possib...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P5 enhancement
Target Milestone: Needs Impl Interest
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-26 15:15 UTC by contributor
Modified: 2014-02-25 16:55 UTC (History)
3 users (show)

See Also:


Attachments

Description contributor 2013-10-26 15:15:05 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html
Multipage: http://www.whatwg.org/C#the-code-element
Complete: http://www.whatwg.org/c#the-code-element
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
I know it can seem useless, but has it ever been proposed to indicate in a
"formal way" the computing language for <code>, <samp> and possibly <var>
element? It could also be useful for syntax highlighting scripts, not to rely
on the author's (in)correct use of @class.

Posted from: 94.39.32.174 by master.skywalker.88@gmail.com
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2013-10-28 22:04:12 UTC
It's something that's come up, but we're not sure there's enough evidence of need for us to do a formal standard. What would be helpful is seeing syntax highlighting script authors get together and come up with their own convention. That would show that there's a need.
Comment 2 Andrea Rendine 2013-10-28 23:49:24 UTC
Is there a public discussion about what did come up? Specific attributes or attribute semantics other than the @class? If you let me know, then we can try to throw a voice among such script authors to see if they can agree on it or propose new things. My effort won't be that strong, but this is the kind of things in which a someone inexpert like me can still help.
Comment 3 Ian 'Hixie' Hickson 2013-10-29 17:11:27 UTC
By "come up" I just mean that people have filed bugs about it, like you (or mailed to the WHATWG list).

The ways scripts are encouraged to collaborate on something like this would be either class="" attributes or data-*="" attributes.