« Blogs as disruptive tech | Home | Useful articles from Linux magazine »
July 2, 2002
Day 17: defining acronyms with the acronym tag
I used 50 acronyms and abbreviations on this weblog last month: ADA, ALT, CGI, CMS, CSS, CTRL, DMV, DNS, DTD, EFF, FAQ, FSF, GFDL, GIA, GPL, HTML, IE, IIRC, IIS, IO, KB, KDE, LONGDESC, MB, MSDN, MSN, MT, Mac, NC, OPML, P2P, PGDN, PGUP, PBS, PDF, PONUR, RSS, RU, SOAP, SSN, TDD, US, VNC, W3C, WCAG, WYSIWYG, Win, XHTML, and XML.
If you know what all 50 of them mean, congratulations; you have a long and prosperous future as a technical editor. If not, you'll appreciate the fact that I defined each of them with the tag. Hover your cursor over each acronym to see what it stands for. This works in all modern browsers, and is harmless in Netscape 4.
You should define an acronym whenever you use it, or at least>Michael benefits. When Michael hovers his cursor over an acronym, Opera displays the acronym title as a tooltip.
How to do it
The first time you use an acronym, mark it up with an tag, like this:
CSS
Radio users can automate this markup by using shortcuts. From your Radio home page, click "Shortcuts" in the main navigation menu, then define the acronyms you use frequently. (Be sure to change the input type from "WYSIWYG" to "Source" so you can type the HTML directly.) For example:
Name: CSS
Value: CSS
Then, in your post, simply type "CSS" (with the quotes), and Radio will render it with the acronym tag and the title, just as you defined it.
[dive into mark]