Re: OT: TECH: Unicode email clients (was Re: OT: Corpses, etc. (was: Re: Gender in conlangs (was: Re: Umlauts (was Re: Elves and Il

On Tue, 4 Nov 2003, Paul Bennett wrote:

> On 4 Nov 2003 at 1:43, Tristan McLeay wrote:
>
> > What client are you using?
>
> Pegasus Mail http://www.pmail.gen.nz/
>
> I've been using it since early DOS versions, and it IMO it kicks
> complete ass. It is, except for the teensy issue of Unicode support,
> just about 100% funcitonally complete.
Well, in this modern word, Unicode support is an important feature in my
books :)

> > Does it actually have a Unicode setting?
>
> No. It ís capable of handling just about any 8-bit format you care to
> throw at it, but it simply isn't capable of handling Unicode
> encodings.
>
> > it might help to turn it on if it does.
>
> Ya think? ;-)
Well, when you said it supported WGL-4, I kinda assumed it did and you had
it disabled or something, because the message you sent was in ISO-8859-1.

> > The Listserv is converting your mail
> > from quoted-printable to 8-bit (iso8859-1 i.e. Latin 1), but it seems to
> > leave UTF-8 messages alone.
>
> I don't know that there's I lot I can do to change the behaviour of
> the listserv.
No, I was talking about if you can send your messages in Unicode. And I've
also got messages in Win1252 intact (though I can't read the
Windows-specific characters).

> > That looks more like something trying to be the Windows-specific encoding
> > rather than either UTF-8 or Latin-1
>
> That's what I said. It can do WGL4, but not Unicode.
WGL4 is just a subset of Unicode. I'm talking about Windows' superset of
ISO-8859-1.

> > (the second character I got was
> > control-capital-u-acute, though in replying it seems to be
> > control-capital-z).
>
> What do you mean by "control"? To me, "control" in this context means
> "subtract 64 from the ASCII value", but I suspect that's not what you
> mean.
I mean I got a single character that took up two spaces in this
fixed-width font, the first space consisting of ^ and the second
consisting of the character I described.

> Oh, and FWIW, in your reply, the e-acute and s-caron came back to me
> unscathed.
You're running a broken email client then. The e-acute should've been
fine, but not the s-caron because I didn't give you a message in a charset
that included it :)

--
Tristan.

Reply