Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: st: How to "format" Statalist posts
From
Lucas <[email protected]>
To
[email protected]
Subject
Re: st: How to "format" Statalist posts
Date
Mon, 2 Sep 2013 17:41:53 -0700
Gmail is not always effective. I use gmail. Whenever I submit
something I always write it with reasonable looking lines and breaks
only at the end of paragraphs. But sometimes I get my posts from the
list and find that every other line has only about 10 characters on
it. It could be because I have set my screen's default fontsize a
certain way and this messes with the gmail. But if I set it any
smaller I'll go blind trying to read material.
As you should see, my last few e-mails to the listserv had no problem.
But, I never know what's gonna happen. I know of no way to be able to
know for sure what my e-mails look like before I send them. Until I
find such a way, please accept my apologies for any future
disjointedness.
Sam
On Mon, Sep 2, 2013 at 4:53 PM, Nicole Boyle <[email protected]> wrote:
> I'm not an expert by any means, but I wonder if the email client is the issue.
>
> Those that post from their iPad/iPhone with the "Sent from my
> iPad/iPhone" use the default Mail client. And the trailing text in
> your iPad post (I'm referring to the 1st link you provided in your
> last post) was posted through Gmail, which is a server that seems to
> have successfully resulted in non-trailing posts, at least according
> to the experiences of Nick and me.
>
> Also, your perceived association between text trailing posts and
> iDevices might even be an attenuated one due to the issue of bounced
> emails that you mentioned (no opportunity to submit a text trailing
> post if you can't even post to begin with).
>
> We could always conduct a fantastically biased study, wherein
> Statalisters could self-report their email clients and whether or not
> text trailing in their posts was an issue.
>
> Nicole
>
> On Mon, Sep 2, 2013 at 3:36 PM, Richard Williams
> <[email protected]> wrote:
>> At 06:04 PM 9/2/2013, Nick Cox wrote:
>>>
>>> The Statalist advice is that people do pay attention to the content
>>> and presentation of their posts. That's in their own best interests.
>>> For example, I recently deleted a post that was so badly presented
>>> that I doubted that a second reading would make clear what the poster
>>> had in mind.
>>>
>>> But what you refer to seems a product of what mailer you use. Yet I
>>> notice that you use gmail, at least for Statalist, just as I do. That
>>> seems to produce reasonable line breaks in continuous prose without
>>> needing attention. I need to be more careful if presenting code, but
>>> otherwise I don't think gmail is problematic.
>>> Nick
>>> [email protected]
>>
>>
>> Conversely, I notice that when I and others post using our iPads, it may
>> look ok on my email programs but on the web paragraphs turn into one long
>> line (at least with my browser). Here are two examples:
>>
>> http://www.stata.com/statalist/archive/2013-08/msg00074.html
>>
>> http://www.stata.com/statalist/archive/2013-09/msg00057.html
>>
>> I also find that my messages sometimes bounce when using my iPad, and I
>> don't really know why. My iPad is convenient but I suspect I should avoid it
>> when posting to Statalist.
>>
>>
>>> On 2 September 2013 21:04, Nicole Boyle <[email protected]> wrote:
>>> > What is the correct way to "format" plain text posts to Statalist? I
>>> > notice that Statalist contributors that don't manually insert line
>>> > breaks (perhaps as demonstrated in this very sentence I'm writing now)
>>> > have text trailing horizontally into infinity. These posts, IMHO, are
>>> > not very reader-friendly.
>>> >
>>> > However, I've also tried to preemptively circumvent this issue by
>>> > inserting line breaks (via carriage return), but things often don't
>>> > work out quite like they should; line breaks occasionally seem to
>>> > appear in places I didn't put them, thereby introducing a different
>>> > type of reader-unfriendliness.
>>> >
>>> > Here's an example that may (or may not, since I won't know until this
>>> > is permanently posted) demonstrate this, using the previous paragraph:
>>> >
>>> > "However, I've also tried to preemptively circumvent this issue by
>>> > inserting line breaks via carriage return), <CARRIAGE RETURN>
>>> > but things often don't work out quite like they should; line breaks
>>> > occasionally seem to <CARRIAGE RETURN>
>>> > appear in places I didn't put them, thereby <CARRIAGE RETURN>
>>> > introducing a different type of reader-unfriendliness."
>>> >
>>> >
>>> > So, any tips on how to better post to Statalist?
>>> >
>>> > Thanks,
>>> > Nicole
>>
>>
>> -------------------------------------------
>> Richard Williams, Notre Dame Dept of Sociology
>> OFFICE: (574)631-6668, (574)631-6463
>> HOME: (574)289-5227
>> EMAIL: [email protected]
>> WWW: http://www.nd.edu/~rwilliam
>>
>>
>> *
>> * For searches and help try:
>> * http://www.stata.com/help.cgi?search
>> * http://www.stata.com/support/faqs/resources/statalist-faq/
>> * http://www.ats.ucla.edu/stat/stata/
> *
> * For searches and help try:
> * http://www.stata.com/help.cgi?search
> * http://www.stata.com/support/faqs/resources/statalist-faq/
> * http://www.ats.ucla.edu/stat/stata/
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/faqs/resources/statalist-faq/
* http://www.ats.ucla.edu/stat/stata/