Re: UTF-8?

Gopi Sundaram <[email protected]>
Newsgroups gmane.mail.pine.general
Message-ID <Pine.GSO.4.64.0611030919040.728@aldebaran>
On Tue, 31 Oct 2006, Matt Ackeret wrote:

> How do I make pine use UTF-8?

I've been using unpatched Pine for several years successfully with UTF-8 
support. Here's what you need:

1) A terminal that supports UTF-8. This means it should be able to 
display UTF-8 characters correctly, and send them correctly when you 
input them.

2) iconv

Once you have those two, do this:

Set Pine's character-set to utf-8 in (M)ain (S)etup (C)onfig

Create a bunch of display filters, one for each charset that you receive 
messages in. They should look like this:

     _CHARSET(iso-8859-1)_ /usr/bin/iconv -f iso-8859-1 -t utf-8
     _CHARSET(iso-8859-15)_ /usr/bin/iconv -f iso-8859-15 -t utf-8

That tells Pine to launch iconv to transcode other charsets into utf-8 
so that your terminal will display them correctly. Check the iconv man 
page to see which charsets for which it supports transcoding.

And that's all!

Here are the downsides:

1) For composing e-mail, Pico will get confused, since it doesn't 
support UTF-8. This means that your cursor will lead the text as you 
type it, and when you go to edit text, the cursor is not really over the 
character that you think it is. Use of an alternate editor is 
recommended.

2) Your message index will still show garbled subject lines. However, 
Pine is still smart enough to tell you what charset each subject is in, 
so you can use this little trick to peek:

     http://www.zrox.net/Mail/Pine/iaq.html#filterindex

3) Quote-coloring is lost on transcoded messages.

Patched Pine might solve these issues, but this gets me close enough.

Hope this helps.

-- 
Gopi Sundaram
http://www.zrox.net/Mail/Pine/
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.