Subject: i18n Support

From: S Bharathi <[email-masked]>
Date: Mon, 31 Dec 2001 16:44:15 +0530 (IST)

Hello,
   If any plan to include i18n support in Pine.
  
   If yes, Anybody is currently working in this area ?

Regards,
Bharathi S.

Happy 2002 :-)
--
 _   _   S. Bharathi    [email-masked] (BSB-340)
(_  |_)  Prj Associate, IndLinuX Developement Team,    (4458904)
 _)*|_)  LLI Lab,       IIT-Madras, INDIA - 600036.
         Visit us at    http://www.tenet.res.in

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Bob Rasmussen <[email-masked]>
Date: Mon, 31 Dec 2001 10:45:30 -0800 (PST)

>    If yes, Anybody is currently working in this area ?

For the uninitiated, "i18n" is "internationalization"  - "i" then 18 letters
then "n".

I have done some work on this, but have received no replies to my previous
questions on this list about others doing the same. Here is my status:

* 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.

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

* I access Pine using Anzio (Windows telnet client), which can accept UTF-8
coming from the host.

* This works for the body text of messages. It also works for passthrough
print.

* There is some built-in conversion capability, but it appears that it is
being used only for search logic.

* 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.

* I have done nothing for:
   a) translating Pine's prompts and messages.
   b) translating incoming keystrokes.
   c) adjustment of word break and line break logic
   d) case conversion
   e) sort order

* Other notes:
   a) It would be nice to remove the character set warning message.
   b) I believe there are some places where Pine treats characters in the
hex-80 to hex-9F range as control characters. But in some charsets, such as
Windows-1252, there are legitimate displayable characters in these locations.

Hope this helps.

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

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