> Why not simply grab the text, paste it into the email and go from
> there. You know the email client at the other end was probably coded in
> the last decade and could probably display it without any problems.

        Because it would be difficult to differentiate what Olin was quoting and
what he was writing. You want to spend the time to add a '>' in front of
every line??

> > But there's no upside at all to using long lines in plain text
> > **especially** in a resume where you want to do everything possible to
> > minimize the chance of it looking like a mess at the other end.
>
> Well I don't agree. It cuts both ways. There is absolutely NOTHING
> worse than taking a piece of text that has carriage returns or any
> other line feed character at the end and try to bring it into a page
> layout application, word processor or html editor.
>
> Sure there are utilities that can strip these out, but if you've only
> got a few pages to do, you figure you may as well sit there and try to
> do a search & replace or edit them out manually. Then you have to edit
> anyway.

        There is a "convention" when it comes to plain text: 80 columns or less.
Whether you AGREE or not doesn't matter, you'll piss off alot of people by
giving them a text file with text that goes beyond 80 columns. And when you
are looking for a job, pissing off people is never a good idea.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads