Brian Heinrich wrote: > > I'm not overjoyed at a situation in which one would have to use, for instance, > '<span class="highlight">word</span>'.
Yes, the extra typing is a bit inconvenient. Maybe someday I'll write a script that will take <highlight> and similar and change it to <span class="highlight">. > So much for separating content from presentation, eh? ;-) In my experience, it's always been worth the trouble. > Perhaps we need to clarify just where we're going with things and then figure > out what tools are appropriate. For m.o, DocBook seems a bit much like > overkill, whether you're looking at developer, technical, wev dev'r, or user > docs. In the context of, say, the help file, however, semantic richness seems > more useful all 'round. > > The point is to get the documentation, get it organised, get it up-to-date, and > be able to maintain it. For /those/ purposes, [X]HTML seems adequate, and its > semantic poverty can in fact work in our advantage, since it'll put less of a > burden on those from whom we really require documentation. Agreed on both points.
