2) Language usage such as Latin as this is a long standing convention in
print and must be retained (thus not styled via CSS).
Example: <i lang="la">Lorem ispum</i>
I actually come across this situation from time to time and I have ummed
and ahhed over what the best thing to do is.
My final answer is to place it in spans, such as <span class="species"
lang="latin">Echium plantagineum</span> because:
1. The span offers flexibility: I have air-head moments where I decide
these things should be italic, and bold, and in a different font, and
then I decide the background should be a different colour. I can never
predict what sort of air-head moments I have from year to year, and CSS
allows me to cover for these moments quite easily. So I can change them
to these stupid settings and then quickly change them back again :)
2. The web is essentially about semantic text. The audience reading your
pages may not necessarily be human, and you need to open up your data
to be available to your audience. Placing these sorts of semantic data
in your code opens it up. The web is not about visual presentation, but
about data. This is a really scary but powerful concept, that I believe
will become even more important in the years to come.
3. All in code is evaluated by Google (a non-human audience member), and
that includes the class name of the span. Your quality rating goes up,
and SEOs could say more, but I believe also your listing for 'species
Echium plantagineum' goes up because of the inclusion of the word
'species':)
So my argument is if you find you need to present it visually different
from surrounding text, ask yourself why. Why is this special, and then
mark it up with spans using that speciality.
Kat
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
