On Sat, Feb 25, 2006 at 12:20:14AM +0100, Dan Jacobson wrote: > Package: lynx-cur > Version: 2.8.6-17 > Severity: normal > > There is something wrong in what lynx sends e.g., uxterm. > $ lynx -dump http://seba.ulyssis.org/thesis/howto-pinyin.php is fine. > Nothing to do with raw utf-8 vs. &#stuff.
if the dump is fine, then it sounds as if you're talking about the interactive display - I don't see any tildes in that (after setting the display character set to UTF-8, of course). > And why does "=" show > Charset: utf-8 > when "o" shows > Assumed document character set(!): [iso-8859-1______] lynx.cfg says # ASSUME_CHARSET changes the handling of documents which do not # explicitly specify a charset. Normally Lynx assumes that 8-bit # characters in those documents are encoded according to iso-8859-1 # (the official default for the HTTP protocol). When ASSUME_CHARSET # is defined here or by an -assume_charset command line flag is in effect, # Lynx will treat documents as if they were encoded accordingly. # See above on how this interacts with "raw mode" and the Display # Character Set. # ASSUME_CHARSET can also be changed via the 'o'ptions menu but will # not be saved as permanent value in user's .lynxrc file to avoid more chaos. # #ASSUME_CHARSET:iso-8859-1 > > -assume_local_charset=UTF-8 no help, -assume_charset=UTF-8 same. > file:///usr/share/doc/HOWTO/en-html/Unicode-HOWTO-4.html no help. > > w3m works fine. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgpCcOGH52CUO.pgp
Description: PGP signature
