[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] French accents

From: Thomas Dickey
Subject: Re: [Lynx-dev] French accents
Date: Tue, 16 Feb 2010 16:49:23 -0500
User-agent: Mutt/1.3.27i

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;
> = 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

Attachment: pgpP_ERCGJnPi.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]