Which answers why the list strips HTML out, but the reason we should compose in
plain text is so we see what our readers will see. The stripping sometimes
makes the result nearly impossible to read and deters people from wading in to
give an answer. In addition, some HTML editors act like word processors and do
things like substitute curly quotes in place of normal quotes, which gives R
fits in examples.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnew...@dcn.davis.ca.us> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
On September 8, 2015 5:03:31 AM PDT, Marc Schwartz <marc_schwa...@me.com> wrote:
>
>> On Sep 8, 2015, at 6:53 AM, Witold E Wolski <wewol...@gmail.com>
>wrote:
>>
>> Hi Jeff,
>>
>> Indeed there was something about plain-text in the r-help posting
>> guide although I can't find it there anymore.
>> https://www.r-project.org/posting-guide.html
>>
>> Is it still an requirement?
>
><snip>
>
>Witold,
>
>See the first bullet in the “Technical details of posting” section:
>
>"No HTML posting (harder to detect spam) (note that this is the default
>in some mail clients - you may have to turn it off). Note that chances
>have become relatively high for ‘HTMLified’ e-mails to be completely
>intercepted (without notice to the sender).”
>
>
>Regards,
>
>Marc Schwartz
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
