If you have an at-all-common case for the content of your site
requiring a specific presentation, this is very simply accomplished
with a new span class. USS Enterprise, defining span.shipname in your
CSS as font-style: Italic;
On an author's site, for instance, it might be common convention for
internal monologues - the thoughts of characters - to be rendered in
italics. So create a new span class for 'thought'. And so forth.
Whenever the writer has an intention for XYZ bit of content to be
rendered in a certain way, there is a reason, an identifiable and
underlying definition to the content within the context. Try to
respect that however possible. There are good reasons why this is
important, why lots of really big brains have spent a lot of thought
on things like this. Those of us who 'preach' adherence to those
guidelines do so because we respect their reasons.
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }
On Mon 10/11/08 12:13 , Travis Butler wrote:
On Nov 08, 2010, at 10:43 AM, Fritz Anderson wrote:
On 7 Nov 2010, at 11:16 PM, LuKreme wrote:
> You don't. and should not be used.
This is the case when the intended semantics of the markup is that
emphasis and strong emphasis are to be indicated, and you don't care
how the renderer accomplishes it. Sometimes, however, the intended
semantics are that the text be rendered as the author intends. In
legal citation, the name of the case MUST BE IN ITALICS. When you say
"Brown v. Board of Education," you don't mean to say it emphatically,
you mean to set it in italics. and mean different things, and
treating them as though is just the New! Improved! Modern! is naïve
and wrong.
Alas, this is a terrible example for your case - because there is a
specific semantic tag for citations, , which should be used for such
things. Among other things, it makes it much easier for things like
screen readers and indexing tools to parse the document properly.
I had an argument with a friend of mine who does a lot of e-book
work about this, just a few days ago. I'm a strong supporter of
semantic markup whenever possible, for precisely this reason -
formatting markup should be based on semantic meaning whenever
possible, so that the underlining meaning can be directly accessed by
software tools. However, I also had to acknowledge my friend's point
that there are so many semantic uses for boldface/italic that they
realistically can't be covered by pure semantic markup - ship names,
interior thoughts/monologue, etc. etc.
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
If you have a feature request or would like to report a problem,
please email "supp...@barebones.com" rather than posting to the
group.
Follow @bbedit on Twitter:
Links:
------
[1] http://groups.google.com/group/bbedit?hl=en
[2] http://www.twitter.com/bbedit
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
