page width
Eric Ulevik
eau at fast.fujitsu.com.au
Thu Nov 11 02:02:18 UTC 1999
------=_NextPart_000_0D00_01BF2C44.FC1BECB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In the long run, people will use HTML.
LaTeX or other invented formats aren't sufficiently better (better =
meaning less features in this case).
----- Original Message -----=20
From: Lex Spoon=20
To: squeak at cs.uiuc.edu=20
Sent: Wednesday, 10 November 1999 8:51 pm
Subject: Re: page width
Agreed. Many readers can handle the un-wrapped text, but why =
pointlessly be a headache for those that can't? There's a clear standard =
for Internet email, and trying to muscle in a new one just isn't polite.
In the long run, people should probably use "enriched text" in their =
email to get the nice paragraph refilling behavior. Enriched text is =
like LaTeX: one line-end makes a soft break, and two line-ends make a =
hard break. Smart recieving programs can then feel free to automatically =
refill paragraphs, and dumb receiving programs will still get something =
that looks okay (assuming the sending program formats to 72 or so =
characters per line).
I'll try and send this message as text/enriched, so people can see how =
it works....
Lex
Rick Zaccone wrote: > Well, my mail reader doesn't wrap incoming =
messages either. I think > it's best to send mail in a format that most =
likely to look good to > everyone. > > 1. Wrap outgoing text. > > 2. =
Don't use tabs. Unix expands them to 8 spaces, Mac and Windows to > 4 =
spaces. > > 3. Don't use accented characters. > > 4. Don't use HTML. > > =
etc. > > Rick > -- > zaccone at bucknell.edu=20
------=_NextPart_000_0D00_01BF2C44.FC1BECB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>In the long run, people will use HTML.</DIV>
<DIV> </DIV>
<DIV>LaTeX or other invented formats aren't sufficiently better (better =
meaning=20
less features in this case).</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:lex at cc.gatech.edu" title=3Dlex at cc.gatech.edu>Lex =
Spoon</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:squeak at cs.uiuc.edu"=20
title=3Dsqueak at cs.uiuc.edu>squeak at cs.uiuc.edu</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, 10 November =
1999 8:51=20
pm</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: page width</DIV>
<DIV><BR></DIV>Agreed. Many readers can handle the un-wrapped text, =
but why=20
pointlessly be a headache for those that can't? There's a clear =
standard for=20
Internet email, and trying to muscle in a new one just isn't =
polite.<BR>In the=20
long run, people should probably use "enriched text" in their email to =
get the=20
nice paragraph refilling behavior. Enriched text is like LaTeX: one =
line-end=20
makes a soft break, and two line-ends make a hard break. Smart =
recieving=20
programs can then feel free to automatically refill paragraphs, and =
dumb=20
receiving programs will still get something that looks okay (assuming =
the=20
sending program formats to 72 or so characters per line).<BR>I'll try =
and send=20
this message as text/enriched, so people can see how it=20
works....<BR>Lex<BR><BR><BR><BR>Rick Zaccone =
<?zaccone at bucknell.edu>wrote:=20
> Well, my mail reader doesn't wrap incoming messages either. I =
think >=20
it's best to send mail in a format that most likely to look good to =
>=20
everyone. > > 1. Wrap outgoing text. > > 2. Don't use =
tabs. Unix=20
expands them to 8 spaces, Mac and Windows to > 4 spaces. > > =
3. Don't=20
use accented characters. > > 4. Don't use HTML. > > etc. =
> >=20
Rick > -- > zaccone at bucknell.edu </BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0D00_01BF2C44.FC1BECB0--
More information about the Squeak-dev
mailing list
|