[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: VS2005 issues (was 1.4.0-rc1 tarballs up for testing/signing)

From: Branko Čibej <brane_at_xbc.nu>
Date: 2006-06-10 02:11:45 CEST

D.J. Heap wrote:
>> Yes, I do have a US Windows XP, but your binaries for 1.3.2 seem to
>> work fine (I see the umlaut or whatever it is) and if I force the
>> output encoding to CP1252 while debugging then it works also. Very
>> strange...for some reason I'm getting CP437 from VC2005 binaries but I
>> don't understand how that could be since GetConsoleCP is a Win32 API
>> (not a C runtime API). I wonder if there is some preprocessor version
>> definition or something in VC2005 that changed and is affecting it?
>>
>
>
> Hmm, Python 2.4 with the Win32 extensions also returns CP437:
>
> C:\Projects>python
> Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)]
> on win32
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import win32console
>>>> win32console.GetConsoleOutputCP()
> 437L
>>>>
>
> So why do your binaries work?
>
> DJ
I'm a genius? ;)

I have no idea. I do believe Python 2.4.x is usually compiled with
VS.NET, so *maybe* that affects how APR behaves. I'm scared to even
imagine what kind of heavy machinery it takes to screw up that badly,
though ...

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 10 02:14:26 2006

This is an archived mail posted to the Subversion Dev mailing list.