[no subject]

[owner-lynx-dev]

[10.100.5.180])
        by relay1.ntu-kpi.kiev.ua (Postfix) with SMTP id 2D62B19D38
        for <address@hidden>; Tue,  4 Jun 2002 21:16:19 +0300 (EEST)
Date: Tue, 4 Jun 2002 21:16:16 +0300
From: "Gleb V. Kotelnitskyy" <address@hidden>
To: address@hidden
Subject: lynx-dev log facility limitations
Message-ID: <address@hidden>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Sender: address@hidden
Precedence: bulk
Reply-To: address@hidden
X-Mailing-List: lynx-dev

i've found that there is some <subj> in Lynx Version 2.8.4rel.1 (17 Jul
2001)
they consist of logging 
key (null)
instead of desired non-englesh characters

so i 've token a look on LYKeymap.c, and have fond there piece of code
regarding my problem

in function LYKeycodeToString
  if (!named) {
          if (c > ' ' && c < 0177)
          sprintf(buf, "%c", c);
          else if (upper8 && c > ' ' 
                && c <= 0377 
                && c <= LYlowest_eightbit[current_char_set] ) // and this line 
i'm
wondering about
        sprintf(buf, "%c", c); 
        else if (c < ' ') sprintf(buf, "^%c", c|0100); 
        else if (c >= 0400)                     //and this oerator i've 
commented out to achieve
logging of non-englesh chars
                sprintf(buf, "key-%#x", c);
        else return 0; } 

        a've made some changes in this part of code so it fits mu
        particular purpose, but i wonder what was the purpose of such
limitations



; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden