Skip to content

Commit

Permalink
[e] (0) Tone down the rhetoric around the <i> element being a last re…
Browse files Browse the repository at this point in the history
…sort, as it doesn't really help authors to say this. (credit: hs)

git-svn-id: http://svn.whatwg.org/webapps@2585 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Dec 25, 2008
1 parent 78cd155 commit b9a4c7c
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 20 deletions.
15 changes: 5 additions & 10 deletions index
Expand Up @@ -13814,21 +13814,16 @@ her&mdash;&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;Raymond woke with a start as the fire alarm rang out.&lt;/p&gt;</pre>
</div>

<p>The <code><a href=#the-i-element>i</a></code> element should be used as a last resort when
no other element is more appropriate. In particular, citations
should use the <code><a href=#the-cite-element>cite</a></code> element, defining instances of
terms should use the <code><a href=#the-dfn-element>dfn</a></code> element, stress emphasis
should use the <code><a href=#the-em-element>em</a></code> element, importance should be denoted
with the <code><a href=#the-strong-element>strong</a></code> element, quotes should be marked up
with the <code><a href=#the-q-element>q</a></code> element, and small print should use the
<code><a href=#the-small-element>small</a></code> element.</p>

<p>Authors are encouraged to use the <code title=attr-class><a href=#classes>class</a></code> attribute on the <code><a href=#the-i-element>i</a></code>
element to identify why the element is being used, so that if the
style of a particular use (e.g. dream sequences as opposed to
taxonomic terms) is to be changed at a later date, the author
doesn't have to go through the entire document (or series of related
documents) annotating each use.</p>
documents) annotating each use. Similarly, authors are encouraged to
consider whether other elements might be more applicable than the
<code><a href=#the-i-element>i</a></code> element, for instance the <code><a href=#the-em-element>em</a></code> element for
marking up stress emphasis, or the <code><a href=#the-dfn-element>dfn</a></code> element to mark
up the defining instance of a term.</p>

<p class=note>Style sheets can be used to format <code><a href=#the-i-element>i</a></code>
elements, just like any other element can be restyled. Thus, it is
Expand Down
15 changes: 5 additions & 10 deletions source
Expand Up @@ -14766,22 +14766,17 @@ her&mdash;&lt;/i>&lt;/p>
&lt;p>Raymond woke with a start as the fire alarm rang out.&lt;/p></pre>
</div>

<p>The <code>i</code> element should be used as a last resort when
no other element is more appropriate. In particular, citations
should use the <code>cite</code> element, defining instances of
terms should use the <code>dfn</code> element, stress emphasis
should use the <code>em</code> element, importance should be denoted
with the <code>strong</code> element, quotes should be marked up
with the <code>q</code> element, and small print should use the
<code>small</code> element.</p>

<p>Authors are encouraged to use the <code
title="attr-class">class</code> attribute on the <code>i</code>
element to identify why the element is being used, so that if the
style of a particular use (e.g. dream sequences as opposed to
taxonomic terms) is to be changed at a later date, the author
doesn't have to go through the entire document (or series of related
documents) annotating each use.</p>
documents) annotating each use. Similarly, authors are encouraged to
consider whether other elements might be more applicable than the
<code>i</code> element, for instance the <code>em</code> element for
marking up stress emphasis, or the <code>dfn</code> element to mark
up the defining instance of a term.</p>

<p class="note">Style sheets can be used to format <code>i</code>
elements, just like any other element can be restyled. Thus, it is
Expand Down

0 comments on commit b9a4c7c

Please sign in to comment.