Subject: Re: i18n Support

From: S Bharathi <[email-masked]>
Date: Wed, 2 Jan 2002 16:45:54 +0530 (IST)

Hello Sir,

Thanks for reply, 

On Mon, 31 Dec 2001, Bob Rasmussen wrote:

> On Mon, 31 Dec 2001, S Bharathi wrote:
> >    If any plan to include i18n support in Pine.
> >    If yes, Anybody is currently working in this area ?
> 
> * I have configured Pine to use "display-filters", such that messages on
> certain charsets are sent through "iconv" (available in Linux) to translate to
> UTF-8.

  What is display-filters ? I have no idea about it.

> * I patched Pine so that it does not clear-screen before and after using a
> display-filter.

   I did some modification in pine4.33 with Gettext for I18N. Whatever i
did is only for menu and error mesg . Nothing for Encoding because i have
very less knowledge about it.  

> * I have not yet figured out how to make Pine translate headers, such as the
> "From:" and "Subject:" lines, according to their embedded charset identifiers.
> In fact, these can sometimes confuse the UTF rendering in Anzio. This is the
> highest priority for me.

  Yes, I am also having same problem and Refresh probelm in keymenu.

> Regards,
> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.

 If you need i will send the scr shot of modified pine, pico & pilot.

Thank you,
-- 
 _   _   S. Bharathi    [email-masked] (BSB-340)
(_  |_)  Prj Associate, IndLinuX Developement Team,    (4458904)
 _)*|_)  LLI Lab,       IIT-Madras, INDIA - 600036.

---

From: Bob Rasmussen <[email-masked]>
Date: Wed, 2 Jan 2002 09:45:53 -0800 (PST)

>   What is display-filters ? I have no idea about it.

This is a feature built into Pine (for Unix) that lets you send certain
messages through a Unix filter before being displayed. See the ".pinerc". For
instance, mine reads:

display-filters=_charset(big5)_ ~/viewutf8 big5,
    _charset(windows-1250)_ ~/viewutf8 windows-1250,
    _charset(windows-1251)_ ~/viewutf8 windows-1251,
    _charset(windows-1252)_ ~/viewutf8 windows-1252,
    _charset(windows-1253)_ ~/viewutf8 windows-1253,
    _charset(windows-1254)_ ~/viewutf8 windows-1254,
    _charset(windows-1255)_ ~/viewutf8 windows-1255,
    _charset(windows-1256)_ ~/viewutf8 windows-1256,
    _charset(windows-1257)_ ~/viewutf8 windows-1257,
    _charset(us-ascii)_ ~/viewutf8 windows-1252,
    _charset(iso-8859-1)_ ~/viewutf8 iso-8859-1,
    _charset(iso-8859-2)_ ~/viewutf8 iso-8859-2,
    _charset(iso-8859-3)_ ~/viewutf8 iso-8859-3,
    _charset(iso-8859-4)_ ~/viewutf8 iso-8859-4,
    _charset(iso-8859-5)_ ~/viewutf8 iso-8859-5,
    _charset(iso-8859-6)_ ~/viewutf8 iso-8859-6,
    _charset(iso-8859-7)_ ~/viewutf8 iso-8859-7,
    _charset(iso-8859-8)_ ~/viewutf8 iso-8859-8,
    _charset(iso-8859-9)_ ~/viewutf8 iso-8859-9,
    _charset(gb2312)_ ~/viewutf8 gb2312,
    _charset(koi8-r)_ ~/viewutf8 koi8-r

The "viewutf8" is a one-line script that reads:
   iconv --from-code=$1 --to-code=utf-8

So for instance, if Pine is displaying a message with a charset of gb2312
(Chinese), it sends it through iconv (included with Linux, available for
others) to convert it to UTF-8 (Unicode), which the telnet client can display.

Regards,

personal e-mail: [email-masked]
 company e-mail: [email-masked]
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com

---

From: S Bharathi <[email-masked]>
Date: Fri, 4 Jan 2002 17:07:08 +0530 (IST)

> .pinerc File:

>     _charset(windows-1250)_ ~/viewutf8 windows-1250,
   [ snip ]

> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.

Very Nice Feature. :)

Kindly give your suggestions to proceed my work. 
How to apply the modification i doing for P4.33 to New Versions ?

Thank you,
Regards,
Bharathi S.

---

From: Bob Rasmussen <[email-masked]>
Date: Mon, 7 Jan 2002 21:36:42 -0800 (PST)

> How to apply the modification i doing for P4.33 to New Versions ?

There are some automated ways of comparing files ("diff") and merging the
changes into a new file, that will work IF there are not changes in the newly
released versions in the same area. My own approach is just to comment my
changes in such a way that I can grep for them, and then reapply them
manually.

Regards,