On 29 Sep, 2006, at 14:34, Brian Kirsch wrote:
That's the "custom XML format" that gets me worried: since we're
planning to use that in email editing, we can't really send around
custom XML. How would that be displayed in other email clients?
AFAIK, RTF is the way to go for basic email fancy work (bkirsch,
please confirm or deny, I'm really not sure here...). Is there a
method to convert back and forth between this format and RTF?
Yes, RTF or HTML are the standard formats. For Chandler, I would
prefer to leverage the HTML format ala Thunderbird. For all rich
text messages (HTML / RTF) I will also send an alternate part that
contains a plain text version for legacy clients.
Do people still use these legacy clients, BTW? I mean, even Pine can
do some kind of richish text display IIRC :).
Anyway, +1 to HTML over text/enriched (I assume that -- RFC 1896 --
is what y'all meant, rather than RTF, which is a different thing
entirely, and not used much in the email world).
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
