Re: HTML adequacy

>Yet if one does a new
>version of HTML, perhaps one should think about all the troubles which
>exist today and attempt to specify a more simple "recursiveable"
>language (see my comment regarding borders above) (also for all those
>beginners in the new decades still using "text"-editors).

Somehow this happend too already. For a precise graphical presentation
you can use SVG (not very useful for an automatical presentation of
paragraphs full of text, but pretty helpful for advanced graphical
representations). And you need no CSS to get this and no HTML, 
but you can use CSS additionally in SVG.
With SVG tiny 1.2 you can even manage some more amount of text
more or less automatically with some linebreaks - however as you may
have observed, this means more freedom for the final graphical 
presentation, therefore for you maybe it works better to position and
to define the appearance of any glyph individually and precisly - this 
is possible and simple with SVG (but as you can imagine, results in 
a lot of information you have to write down, but you can do it with a 
simple text editor).

And the best of it - if you are doing it right with SVG, in general the
text and content is still accessible, because in this way SVG is 
designed to enable you to create accessible graphics.

Another advantage - you do not have to worry about MSIE7, because
this device does not interprete SVG at all, therefore it does not produce
any painful output, you have to care about ;o)

To conclude - (X)HTML and some other, more advanced languages to
markup text note more or less, what kind of text you want to write, CSS
indicates how to present it (roughly). SVG can be used to specify a 
detailed graphical representation of the information, you want to provide.
Therefore in some way, all what you suggested already happened somehow,
you have just to chose a language fitting to your intentions  instead of
trying to change a language to align with your intentions.

Olaf

Received on Saturday, 23 January 2010 15:30:14 UTC