page widthEric Ulevik eau at fast.fujitsu.com.auThu Nov 11 02:19:50 UTC 1999
------=_NextPart_000_0D1C_01BF2C47.6F2B6BC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Obligatory on-topic observation: Can't I read HTML email in Squeak? If not, should be easy, right? ----- Original Message -----=20 From: Peter Hatch=20 To: squeak at cs.uiuc.edu=20 Sent: Thursday, 11 November 1999 1:12 pm Subject: Re: page width=20 I sure hope not. I hate to sound atavistic here, but I just don't see = any benefit from all of this fancy colored text in email. The emails I = get from some of the folks that work in my company are just ludicrous. = There's 1 line of information, and then 10 lines of colorful multi-font = signature. I find it to be simply disruptive.... Of course, that's just me (living in my little *nix corner of the = world). And, of course, this is totally off topic :-) > In the long run, people will use HTML. >=20 > LaTeX or other invented formats aren't sufficiently better (better = =3D > meaning less features in this case). > ----- Original Message -----=3D20 > From: Lex Spoon=3D20 > To: squeak at cs.uiuc.edu=3D20 > Sent: Wednesday, 10 November 1999 8:51 pm > Subject: Re: page width >=20 >=20 > Agreed. Many readers can handle the un-wrapped text, but why =3D > pointlessly be a headache for those that can't? There's a clear = standard =3D > 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 = =3D > email to get the nice paragraph refilling behavior. Enriched text is = =3D > like LaTeX: one line-end makes a soft break, and two line-ends make = a =3D > hard break. Smart recieving programs can then feel free to = automatically =3D > refill paragraphs, and dumb receiving programs will still get = something =3D > that looks okay (assuming the sending program formats to 72 or so = =3D > characters per line). > I'll try and send this message as text/enriched, so people can see = how =3D > it works.... > Lex >=20 >=20 >=20 > Rick Zaccone wrote: > Well, my mail reader doesn't wrap incoming =3D > messages either. I think > it's best to send mail in a format that = most =3D > likely to look good to > everyone. > > 1. Wrap outgoing text. > > 2. = =3D > Don't use tabs. Unix expands them to 8 spaces, Mac and Windows to > = 4 =3D > spaces. > > 3. Don't use accented characters. > > 4. Don't use HTML. = > > =3D > etc. > > Rick > -- > zaccone at bucknell.edu=3D20 >=20 ------=_NextPart_000_0D1C_01BF2C47.6F2B6BC0 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>Obligatory on-topic observation: Can't I read HTML email in = Squeak?</DIV> <DIV> </DIV> <DIV> If not, should be easy, right?</DIV> <DIV> </DIV> <DIV>----- Original Message ----- </DIV> <BLOCKQUOTE=20 style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: = 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px"> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A href=3D"mailto:phatch at mojowire.com" = title=3Dphatch at mojowire.com>Peter Hatch</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> Thursday, 11 November = 1999 1:12=20 pm</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: page width </DIV> <DIV><BR></DIV>I sure hope not. I hate to sound atavistic here, but I = just=20 don't see any benefit from all of this fancy colored text in email. = The emails=20 I get from some of the folks that work in my company are just = ludicrous.=20 There's 1 line of information, and then 10 lines of colorful = multi-font=20 signature. I find it to be simply disruptive....<BR><BR>Of course, = that's just=20 me (living in my little *nix corner of the world).<BR><BR>And, of = course, this=20 is totally off topic :-)<BR><BR><BR><BR>> In the long run, people = will use=20 HTML.<BR>> <BR>> LaTeX or other invented formats aren't = sufficiently=20 better (better =3D<BR>> meaning less features in this = case).<BR>> -----=20 Original Message -----=3D20<BR>> From: Lex Spoon=3D20<BR>> To:=20 squeak at cs.uiuc.edu=3D20<BR>> Sent: Wednesday, 10 November 1999 8:51 = pm<BR>> Subject: Re: page width<BR>> <BR>> <BR>> Agreed. = Many=20 readers can handle the un-wrapped text, but why =3D<BR>> = pointlessly be a=20 headache for those that can't? There's a clear standard =3D<BR>> = for Internet=20 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 = =3D<BR>> email=20 to get the nice paragraph refilling behavior. Enriched text is = =3D<BR>> like=20 LaTeX: one line-end makes a soft break, and two line-ends make a = =3D<BR>>=20 hard break. Smart recieving programs can then feel free to = automatically=20 =3D<BR>> refill paragraphs, and dumb receiving programs will still = get=20 something =3D<BR>> that looks okay (assuming the sending program = formats to=20 72 or so =3D<BR>> characters per line).<BR>> I'll try and send = this=20 message as text/enriched, so people can see how =3D<BR>> it = works....<BR>>=20 Lex<BR>> <BR>> <BR>> <BR>> Rick Zaccone wrote: > Well, = my mail=20 reader doesn't wrap incoming =3D<BR>> messages either. I think > = it's best=20 to send mail in a format that most =3D<BR>> likely to look good to = >=20 everyone. > > 1. Wrap outgoing text. > > 2. =3D<BR>> = Don't use=20 tabs. Unix expands them to 8 spaces, Mac and Windows to > 4 = =3D<BR>>=20 spaces. > > 3. Don't use accented characters. > > 4. Don't = use=20 HTML. > > =3D<BR>> etc. > > Rick > -- >=20 zaccone at bucknell.edu=3D20<BR>> <BR></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_0D1C_01BF2C47.6F2B6BC0--
More information about the Squeak-dev mailing list |