Is the richtext content-type going to change? And will the result still
be called richtext?
If so, and it is going to change in a non-backwards compatible way,
then I'm going to refrain from implementing it until the dust
settles. If the new version is going to get a different subtype
(richertext :-), this is no problem, but then minimal MIME compliance
becomes less and less minimal...
Personally I have no major problems with the present version.
There are a few oversights in the minimal compliance requirements
(paragraph support should be mandatory, otherwise </paragraph> is useless)
and the suggested treatment of white space, but these are easily corrected.
Also, the example program does not satisfy the minimal compliance requirements
(it doesn't convert newlines to blank space) and it is too long and
complicated).
(I have already sent detailed comments and a shorter, *compliant*, program
to Nathaniel).
--
Luc Rooijakkers Internet:
lwj(_at_)cs(_dot_)kun(_dot_)nl
Faculty of Mathematics and Computer Science UUCP: uunet!cs.kun.nl!lwj
University of Nijmegen, the Netherlands tel. +3180652271