On Wed, 3 Feb 2010, Kristopher Kycia wrote:
Not sure this is a compilation issue anymore... I think this is a DOS issue... By default DOS has an ASCII table with all of the characters (or most - some newer Windows ones would not be supported). This sounds like it has something to do with the fact that Lynx does not know what to do (in the case of the language). I think the configuration defaulting to US-ASCII is hinting that it is pickup the default ASCII table. But the problem is that it is using "7 bit approximation" (whatever the hell that means...) Somehow this is leading to the wrong characters mapping to the wrong ASCII values.
DOS does. But what's running in Windows isn't DOS, and will behave differently.
fwiw (Code Page Identifiers) http://msdn.microsoft.com/en-us/library/dd317756(VS.85).aspx (CHCP) http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chcp.mspx?mfr=true The latter doesn't hint that Unicode codepage is supported in Windows. Lynx doesn't detect the codepage for the Windows port - that would be something useful to submit a patch for. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net _______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
