[PATCH 0 of 6] Win32 installer updates

Sune Foldager cryo at cyanite.org
Mon Feb 9 02:58:48 CST 2009


The default Windows console font only handles legacy code pages, no matter
what 'chcp' commands and similar are issued. Thus without changing the font,
chcp settings are ignored for display purposes. You need to change to Lucida
Console (the other possible font) to see the effect of chcp 1252 (which
switched the charset to "almost latin1"), for instance. It works fine for me
in that combination.

-- Sune.


Pascal Quantin <pascal.quantin at gmail.com> writes:

>> Okay... ISO-8859-1 puts 'ø' in byte 248, but code page 437 (old DOS 
>> codepage, with no support for 'æ', 'ø', 'å') and code page 850 both 
>> puts a '°' sign there. In CP850 the 'ø' replaces '¢' from CP437.
>>
>> So you could try with da_DK.cp850 to see if that makes 'ø' appear.
>>
>> I used these tables to reconstruct what was happening:
>>
>>  http://en.wikipedia.org/wiki/Code_page_850
>>  http://en.wikipedia.org/wiki/Code_page_437
>>  http://en.wikipedia.org/wiki/ISO_8859-1
>
> Hi,
> it didn't change the character displayed: I still have the '°' sign 
> displayed instead of 'ø' (still working fine in msys).

Weird... could you try with a small program like this:

  print "0xF8:", chr(0xF8), "ISO-8859-1"
  print "0x9B:", chr(0x9B), "CP850"

One of those bytes ought to be a 'ø'...

--
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC
(Secure Multiparty Computation) to Python. See: http://viff.dk/.




More information about the Mercurial-devel mailing list