https://bugzilla.wikimedia.org/show_bug.cgi?id=671
--- Comment #45 from Christopher Yeleighton <[email protected]> 2010-07-22 19:33:30 UTC --- (In reply to comment #37) > <abbr> instead. <kbd> and <samp> are basically useless. <q> is dodgy because No, they are useful, albeit a limited domain. If HTML had been designed by biologists, it would have SPECIES and FAMILY instead. (In reply to comment #40) > If a wiki actually wants to use <q> despite the IE problems, it can request > that and it might be considered. I haven't seen such a request. If it were Try "HTML q element" [1]. (In reply to comment #41) > That said (i.e. my personal reason for stumping for dfn), the dfn element is > also very useful all over Wikipedia and similar sites just by the element's > very nature. It should be one of the most-used. For example, I think that on > Wikipedia in particular, the bold-faced beginning of lead sections in > mainspace > articles should mostly be done with a template that auto-adds dfn, instead of > manual boldfacing, e.g.: "An {{leadterm|electrokardiogram}} is..." I mean, > really, that's precisely what this element exists for: To flag the defining > instance (in its context) of a term. I would rather say [[{subst:PAGENAME}]] and leave inserting the DFN tags to the engine. (I admit I have changed my position on this subject.) > major browsers treat it the same. Normally I will never bend at all to suit > broken Microsoft apps, but this issue actually goes beyond that, as some > browsers do not auto-insert quotation marks, HTML5 goes flip-flop about this. The version I have in memory cache says quotation marks should be explicit inside Q. >>> I am trying to figure out the best way to replace the tt element as I >>> migrate to HTML5. The wiki way of embedding code sections is to put white space on the beginning of the line. This leaves the question of in-line code; software manuals need this but it is a very special application. I cannot imagine an example of in-line output. (In reply to comment #43) > I'd like to see specific examples of screen readers or power-users' > stylesheets > that do not treat these the same as <code> or <tt>, since you say these are > near certain or absolutely certain. My Internet Explorer used to render CODE in 10pt and SAMP in 12pt, probably upon assumption that CODE is for nerds with big lenses ;-) ___ [1] <URL:http://en.wikipedia.org/wiki/Wikipedia_talk:Manual_of_Style/Archive_103#HTML_q_element> -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
