<http://www.faqs.org/rfcs/rfc2822.html> is the controlling document for the basics of internet email. (Some would claim that the real RTF is 822 which is formally approved and not still "standards track". It's worth a read. Its also worth while to poke around on that site for general education. RFC's (Requests for Comments) are the way the internet is supposed to work.
<http://www.faqs.org/rfcs/rfc2045.html> Is the starting point for MIME extensions to email. Discussion of Content-Transfer-encoding is discussed there. It's a starting point for the proper inclusion of type HTML in a multipart mail message. It's widely ignored assuming that the client can look for an <html> tag in the body of a message. At 00:50 -0400 7/18/10, Kevin Barth wrote: >OK. so now it seems you're arguing that everybody should limit themselves to >plaintext because you >can't read a proportional font? Or at least that you find a proportional font >harder to read than a >non-proportional one? At 22:34 -0500 7/17/10, James Therrault wrote: >All plain text does is default to a non-proportiona font family such as >courier. IOW, an "I" takes up the >same space as a "W" etc. Plain text has absolutely noting to do with font or its character width and kerning. The reader, or his mail client, gets to choose it. At 01:18 -0400 7/18/10, Dan wrote: >First of all, realize that "rich text" is a form of HTML. At 09:08 -0400 7/18/10, Dan wrote: >RTF (Rich Text Format) is HTML, but without some of the formal headers and >such. Since it hasn't got >all the headers, it's a bit more efficient -- but not by much. <http://www.faqs.org/rfcs/rfc1563.html> describes enriched text. It was once called rich text but that got changed because of confusion with RTF (rich text format) which originated with Microsoft and was first used on Apple products as part of the BASIC language. As far as I know nobody has ever used RTF in the body of an email. It certainly is NOT HTML in any sense of the acronym. Apple, in OS neXt, uses a form of RTF for the likes of TextEdit.app. It's not compatible with the most current release, by Microsoft, of its RTF standard. (And by the way, you need to be a licensed developer to have access to that. I can't read my pirated copy in Word 5.1 or in TextEdit.). The last email that I received in enriched text probably came over arpanet.. >From RFC 1563: >This document defines one particular type of MIME data, the > text/enriched type, a refinement of the "text/richtext" type defined > in RFC 1341. > The syntax of "text/enriched" is very simple. It represents text in > a single character set -- US-ASCII by default, although a different > character set can be specified by the use of the "charset" parameter. > (The semantics of text/enriched in non-ASCII character sets are > discussed later in this document.) At 00:13 -0600 7/18/10, Tina K. wrote: > I'm curious, how does RTF fits into the discussion? Is Mail.app's RTF format > really HTML? Mail.app will NOT place either Apple's RTF or Microsoft's RTF into the body of a mail message. As an attachment it would be possible. Like dragging the icon of a raw TextEdit file into the attachment box of a mail client. Mail.app defaults to using HTML for all messages but it can be told not to do that. If it calls HTML RTF it ought to be reported as a bug. There was once a UNIX tool called demime that would convert HTML to plain text. Mailing lists made extensive use of it for things like creating digests that work. I donno what it's current status is but I just might try it on stuff from this list. I'll have to move off this 8500 first. -- --> From the U S of A, the only socialist country that refuses to admit it. <-- -- You received this message because you are a member of G-Group, a group for those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs. The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to g3-5-list@googlegroups.com For more options, visit this group at http://groups.google.com/group/g3-5-list
