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 email@example.com.
Hello Tony, ... >> 1. CVSNT servers on unix try to run in UTF-8 if the system supports >> this. TH> Yes this has been true for a while. It's the only way to ensure a TH> common protocol - cvsnt clients then translate back to their local TH> codepage as required ... Is the translation done on server or on client side? >> 2. If one moves a repository from WIN32 or cvshome server, the >> codepage of the server has to be overwritten, or the repository >> has to be converted. TH> You'd have to do that anyway for a Win32->Unix or Unix->Win32 change, TH> since the character sets are often different. How to do that? Is there a tool/solution? This should be mentioned in the wiki ('moving a repository')... TH> It's not been an issue for people normally - really only affects TH> the comments. And the Documentation (generated from this comments)... TH> RCS files don't contain codepage information so it's not trivial to TH> convert automatically - you can have comments in multiple languages TH> etc. with no indication of their original character set. Normaly the codepages can be guessed / are known for a particular repository, so a conversion should be possible (even it may be not 100% correct) >> 3. If one overwrites the servers codepage via /etc/cvsnt/PServer >> clients running on the same machine as the server also get this >> codepage forced. .... TH> Shouldn't matter normally though - unix is quite good at handling TH> this stuff. How to understand this? -- Best regards, Richard mailto:richard at wirthware.de