sdorner(_at_)qualcomm(_dot_)com (Steve Dorner) writes:
I do this by delimiting the richtext body parts with <x-rich> and
</x-rich> directives, and then treating the whole thing as (sorta)
text/richtext.
Don't you mean the "delimiting the text/plain parts"?
This is certainly a legal interpretation of richtext--a richtext
reader can "recognize" any formatting command and if it is not
mentioned in a standard, interpret it anyway it wants. It can display
the text top-to-bottom, spiraling out of the center, or as morse code
tapped out on the speaker. As long as you don't *compose* (and send
out) a message that violates the richtext restrictions.
Complicating your parser in order to handle this extension may well be
an overall win for you. This does not necessarily mean it is good to
require all parsers to be similarly complicated.
How do you handle text/plain parts with imbedded "<x-rich>" and
"</x-rich>" text?
--
_.John G. Myers Internet: jgm+(_at_)CMU(_dot_)EDU
LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up