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.
i'm still in trouble with the codepage translation that will be handled on client side with cvsnt 2.5.01.1976. I checked that on server side: all filenames are correct, including the wrongly translated(removed) characters. So both codepages on server and client side supports this characters, only the translation don't supports this. The "cvs -t ver" command tells me that translation is active. On clients that still use cvsnt 2.0.51d don't translate and everything works fine. So i'll deactivate this with client 2.5.01.1976. Is this possible? Or is it possible to create a own translation rule and force the client to use this one? 12:53:36: -> Server codepage is ANSI_X3.4-1968 12:53:36: -> Client codepage is CP1252 12:53:36: -> Server->Client codepage translation is active 12:53:36: -> Server version is CVSNT 2.5.01 (Travis) Build 1976 12:53:36: -> Client version is CVSNT 2.5.01 (Travis) Build 1976 (cvsgui best regards, Alexander Zoernack