I believe the easiest way to differentiate them is to use <acronym> if you can speak it like a word, not spell them out like a group of letters. We say “ray-dar”, not are-aay-dee-ayy-are. So we get
<acronym title="Radio Detection and Ranging">Radar</acronym>.
If spelling them out letter by letter it’s an <abbr>, like this
<abbr title="Cascading Style Sheets">CSS</abbr>.
Thank’s to this comment on a old thread at evolt.org for cutting it clear.
Offcourse, Microsoft has decided not to support the
abbr element in its browsers …
Some other resources for further discussion:
Westciv, the publishers of a number of comprehensive self paced courses for learning CSS, HTML/XHTML and standards based design are giving away a completely free (X)HTML and CSS online course. If you are serious about learning and knowing standards based web design this is a free lunch worth saying yes too. According to some of the blogs in my feedreader this course has been around for some time, but has now been updated to better reflect modern browser’s support. I haven’t done the course myself, but as I understand this course has been the foundation for many of today’s well known designers. Furthermore it’s said to be good for a learner to intermediate level.
If this is old news to you, and you think you know everything there is to know, then why don’t you join Molly in her quest for making the www a better place?
So what is POSH? It’s basicly everything you probably allready know.
- validate your markup
- no tables for layout, or any other presentational HTML for that sake
- use class and id names describing the content, not the looks
Check out the Microformats Wiki for more information.
So I decided not just to talk the talk, but also to walk the walk. I got myself HTML Mastery by Paul Haine . I’ve been through a number of books on CSS, but this is my virgin HTML book! Obviously I’ve spent a fair share of time reading online, but I still find books having some benefits. And so far I’m very impressed by the book. There are off course many things that I allready know, but it’s good to have all the little details explained and put together in a matter that makes since. Like the construction of the DOCTYPE, which tags are and aren’t valid, usable, the historical reasons for their alterations and so on. I’ll write a proper review on the book later, but if you are serious about your markup, and want to become POSH like all the cool kids, HTML Mastery will give you a good start.
I’ve never seen a better workrelated reason to leave Norway. My dreamworkplace has a position up for grabs, but it ain’t gonna be for me. Instead of putting a list of crappy excuses, I’ll say that it’s to do with my current geographic location to these:
Now excuse me, but I have a portfolio to work on.
I’ve been dying to get a brief for any
‘ol new bulletproof webstandards supporting websites, but they seldom come along. Granted, I’ll do my best to incorporate it anyhow, within budget and all. But rarely do I get the request from the other side of the table.
Until recently, when I discovered a little loophole. And I’m gonna share it with you.
It’s easier to sell SEO then webstandards, semantic markup etc. One thing says make more money, the other one says extra work. But they really are closely related. So when you want to do some nice markup, tell your client that it’s to get a higher Google rank rather then it’s for that blind user that might surf by. Your boss will also be happy to hear that you are a SEO specialist as well as a webdesigner ;-)
A bit of a sidenote, but on the same page: while you’re at it, tell them how the handheld webbrowsing marked is exploding at this very moment. Refer to sales of 3G mobilephones and PDAs, and see how many more phones there are then PCs. And that you can design for them too, but only if they let you care about webstandards, valid markup, xhtml, css, microformats and such.