Comment by sunshowers
1 day ago
I write most of my content in markdown or asciidoc and I don't pay attention to whether it's b or strong :)
1 day ago
I write most of my content in markdown or asciidoc and I don't pay attention to whether it's b or strong :)
In practice today, that's fine. Typically authors have a hard time differentiating what "emphasis," "importance," and "bring attention to" mean to them. Therefore, nothing conveys a distinction by default.
So then what's the point of making this distinction? I would like to see surveys of how many people actually author content in forms that differentiate between b and strong.
Because the elements already exist. When the elements were invented and defined, CSS didn't exist and authors had to use elements to make presentational changes. When HTML5 was defined, CSS was well established and it was an opportunity to update element descriptions to get rid of specific presentational qualities.
There are lots of elements, if you don't find some of them useful, don't use them. Other people may find uses for the distinctions; even if they use distinctive styling for them all, they may need to document why they're used, not just for all the authors but for the audience as well; clearly we can't expect developers to know what all the elements are for so that's doubly true for the audience.
1 reply →
What, you don't know what's the difference between "emphasis" and "bringing attention to"? Shame on you, shame on you: you're unworthy to write HTML.
The difference, of course, is that one is a Latin word, and the other is an English phrase with the same meaning. But they're different words, so different tags. It's all completely rational and logical, and if you don't see the logic and/or reason, well: you're unworthy to write HTML. See Figure 1.
P.S. I love this ancient "see figure 1" meme. It's originated in the early 80s, and still as relevant as ever, and probably will be forever.
1 reply →
> So then what's the point of making this distinction?
It keeps the semantic web people busy not doing too much damage. Otherwise we might get an XHTML3 or CSS4 based on RDF triples or some such horror.