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

Re: FW: VS2005 issues (was: TSVN: Problems with BDB file access)

From: Branko Čibej <brane_at_xbc.nu>
Date: 2006-01-25 22:49:07 CET

Jens Peters wrote:
>> No, but with all the VS2005-related problems reported to
>> date, the obvious solution is to scrap that and use VS2003
>> for production.
>>
>
> I tempt to agree. I have followed the discussion on the apache dev list
> wether to use VC6 or VC2005 for the official releases and I would choose VC6
> as well. But regardless I think it should work on other VC's, though I agree
> that the bdb stuff was a real showstopper...
>
> Anyway I digged a little bit into the code and may be I found something (I
> have a c# background, my last line of code in c went back to my final
> examination 5 years ago, please be kind..):
> I have an english WinXp and have set the regional settings for testing
> purposes to german. When I step through the code I see that in
> svn_cmdline_init the actual codepage is read from GetConsoleOuputCP. In my
> case it returns CP437. If I change it hardcoded to CP1252, what I would have
> expected in the first place, the translation from utf8 went fine and I can
> see the german 'Umlaute'. Since the official binaries works fine I don't
> think that there is something wrong with my environment. I don't have VC2003
> or VC6 installed so I can't say which codepage wil be returned there, but I
> doubt it will return something different from VC2005. So I'm not sure that
> this is the right place to look further. Any ideas/comments?
>
No idea. Looks like a serious bug in the library stubs to me.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 25 22:49:38 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.