On Mon, Feb 15, 2010 at 02:07:21PM -0500, Sándor Halász wrote: > >>>> 2010/02/03 05:24 -0500, Thomas Dickey >>>> > Lynx doesn't detect the codepage for the Windows port - that would be > something useful to submit a patch for. > <<<<<<<< > I suppose you know about this, > mov ax,6601 > int 21h > after which the "active"-codepage number is returned in BX, and the default > in DX, or, in muSoft C,
yes, but iirc, interrupts aren't usable in Windows - only DOS. > union REGS inout; > inout.x.ax = 0x6601; > intdos(inout, inout); > after which it is found in inout.x.bx or inout.x.dx. Under Vista, though, > the same is returned in both registers, integer from the string datum that > goes with (under HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage) value > OEMCP in the registry. It seems to me that neither CHCP nor MODE CON CP > SELECT does anything beyond verifying the operand and keeping it for later > showing. That registry string value (from "Language for non-Unicode > programs") upon booting actually determines which codepage is used when a > command-line window is spawned. > > I am not up to making a patch out of this. I counted on Kaufman s versions. :-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgpmqGsq6mhNV.pgp
Description: PGP signature
_______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
