Re: UTF-8 practically vs. theoretically in the VFS API

Robin Rosenberg
2004-02-18T12:35:12Z

On Wednesday 18 February 2004 13.05, Tomas Szepe wrote:
> On Feb-18 2004, Wed, 12:59 +0100
> Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
>
> > On Wednesday 18 February 2004 12.49, Tomas Szepe wrote:
> > > Would you _please_ read the lkml FAQ and stop posting e-mails with lines
> > > longer than 80 characters? Thank you.
> >
> > As soon as someone asks nicely... I thought any decent mail client simply
> > wrapped the lines.
>
> 1) Quite the contrary. Any _decent_ mail client will _not_ wrap the lines.
>
> 2) A mail client that will wrap the lines will make your posts look like
this:
>
> <cut>
> Having to put up with the existence of Windows day in and out is the reason
I'm
> still on
> an eight-bit encoding. Sorry for not explaining the REAL problem, but only
a
> partial
> problem. I need to support all kinds of clients on Windows with protocols
that
> convey no
> character set info. With samba that's no problem. Having to put up with a
Unix
> world running
> <cut>

That's what happens when the sender wraps the lines at column 80 and your
client wraps at 72 (or similar situation), just another reason not to wrap
when sending and let the users client do whatever the user think is fine.

In order not to wrap and destroy information I have the autowrap feature off
when composing mail, becase wrapped and cut stack traces, cuts from log files
etc are a pain.

BTW The 80 character rule is only mention wrt to signatures.

-- robin