Forwarded message: > From [EMAIL PROTECTED] Mon Dec 20 10:14:10 1999 > Date: Mon, 20 Dec 1999 12:07:09 +0200 > From: sig <[EMAIL PROTECTED]> > X-Mailer: The Bat! (v1.36) UNREG / CD5BF9353B3B7091 > Reply-To: sig <[EMAIL PROTECTED]> > Organization: UCT > X-Priority: 3 (Normal) > Message-ID: <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: suggestion about charsets unknown by lynx > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > > Hello dickey, > > i have pages in KOI8-U charset (KOI8-Ukrainian). > The Lynx 2.8.2, which i use doesn't support this charset, > but it's not very differs from KOI8-R (only 6 characters). > > My Unix terminal configured to treat the KOI8-U as KOI8-R, > all characters, needed for KOI8-U charset is correctly viewed > on screen. > > But Lynx don't accept this charset and give me only two > choises: save page to file, or cancel :( > > i know the ways, how to avoid this problem, but each of them > is brain-damaged (like adding new charset to Lynx source code or to > refuse using KOI8-U for my HTML-documents). > > The simplest way, i see, is to give a user the third choice, when > Lynx don't know the charset: > > 1. download in file > 2. cancel > 3. view in charset, which user can select - this will be good > replacement for -assume_unrec_charset command option. > > Also it's would be good if i would be able in lynx.cfg file > to add my own charsets to threat them as > other, already known charset. > > Best regards, > sig mailto:[EMAIL PROTECTED] > > -- Thomas E. Dickey [EMAIL PROTECTED] http://www.clark.net/pub/dickey
