Re: charset mapping - how to avoid?

Yngvar Folling (yngvar.folling@login.eunet.no)
Fri, 1 Nov 1996 11:03:04 -0500

In article <bZOey8A62EOf092yn@egnatia.ee.auth.gr>,
adia@egnatia.ee.auth.gr (Alejandros Diamandidis) wrote:
> Hello... I've been using yarn for some time now and I think
> it's the best mail/news program there is, only now
> I have a problem with non-ascii characters: I get some messages
> written in iso-8859-1 and others in iso-8859-7 (Latin/Greek).
> I'd like to disable any mapping done by Yarn, because
> it's easier to just load the appropriate font for each message.

[Rest deleted.]

Sorry, I have no solution. I just write this to make sure that whatever
fix Chin makes when charset is commented out of the CONFIG file, the
current behaviour is *unchanged* when it is left in. I've got the line
charset=iso-8859-1 in my CONFIG file, and it works perfectly for me. I
just have experience that when a software update fixes a problem that
does *not* affect me, it sometimes introduces new problems that *do*.

Chin, might it not be a better idea to make the character set
translation such that instead of choosing between several built-in
translation tables, you make the user supply their own? Example tables
for the most common translations (those who are currently built in)
would then be included with the program.

This reminds me that I hope that you eventually translate Subject lines
with =?iso-8859-1?Q? and Quoted-Printable stuff into something readable.

And *please* make the Search functions so that they work with translated
characters as well. I still can't find a way to search for text with
Norwegian national characters in it.

Yngvar