Hi, On Tue, Jul 10, 2012 at 2:54 AM, Nick Dokos <nicholas.do...@hp.com> wrote: > suvayu ali <fatkasuvayu+li...@gmail.com> wrote: > >> Hello all, >> >> On Tue, Jul 10, 2012 at 12:13 AM, Nick Dokos <nicholas.do...@hp.com> wrote: >> > >> > o post an ECM to begin with - no ifs, ands or buts. >> > o post what you tested *exactly*. >> > o test what you (or somebody else) posted *exactly* as it was posted. >> >> A comment with regards to the above; from the experience in this thread >> it seems posting an ECM is better done as a plain text attachment rather >> than inline quoted regions. After all getting from inline quoted regions >> to working examples require human intervention which, as we saw, is >> prone to errors. ;) >> > > If the human intervention is the problem, then I would advocate > education, rather than attachments, as the solution: after all there is > nothing that would stop that kind of intervention *after* the attachment > has been saved. But in the face of more and more idiotic mail software > out there that mangles messages irredeemably, I will reluctantly agree: > I'm still old fashioned enough to prefer inline quoting, but I have been > known to repost something as an attachment if the inline post gets > mangled. >
:) Nothing beats inline quotes when it comes to readability. But I guess some of the modern GUI clients offer smooth viewing of text attachments. e.g. I think in T-bird you can see the contents of a text attachment separated from the email by a horizontal separator without actually opening it. However I also notice these clients often mess up the MIME types when attaching something; this in turn screws up the archive and confuses email clients on the receiving end[1]. Two examples of how not to do it: 1. <http://thread.gmane.org/gmane.emacs.orgmode/32038> 2. <http://thread.gmane.org/gmane.emacs.orgmode/32038/focus=32118> > Nick > Footnotes: [1] I believe I learnt about the importance of attachment MIME types from you Nick. ;) -- Suvayu Open source is the future. It sets us free.