Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi Tony, thank you very much for this background information. I installed the latest cvsnt-2.0.60, but could not choose ssl as protocol during installation. However, I installed all protocols and also installed the server and had to reboot. At startup, I got a message asking me if I want to rename the "Program" directory to "Program1". That scared me a lot - I installed cvsnt into "Program Files". Now :ssl: did not work at all, so I went back to the old version 2.0.51d. Is :ssl: gone? Do I have to use :ext: now? Don't know. So I feel uneasy about cvsnt - I guess I just wait for the next stable release. Thanks again Dietrich Uninstall did not get rid of the scary question, though! "Tony Hoyle" <tmh at nodomain.org> wrote in message news:cn83u2$9d5$1 at paris.nodomain.org... > Dietrich Schmidt wrote: >> Hi, >> >> problem summary: checking out a file with german Umlaute on Windows from >> a Linux CVS server scrambles the filename. > > CVS is inherently ANSI with its filename processing. With 2.0.51 both > client and server must be using exactly the same codepage otherwise the > output will be scrambled for characters >127. > > 2.0.58 client/server has a translation mode which maps between client > codepage and server codepage (this works best if the server is in UTF8, as > that can support any character). To activate this use the -o option on > the cvs client command line. > > Tony