Yves Dorfsman, In CVS a Unicode file has to be a Binary file (-kb) - which prevents merging, diffs, etc etc. If you do not define it as -kb then eventually the file will be corrupted.
CVSNT for Linux/Unix/Mac/Windows is free (GPL - just like CVS) but supports the -ku type (unicode) which allows efficient storage, diff's, merges etc - just like a text file but as unicode. http://march-hare.com/cvspro/ If you run the CVSNT server in unicode mode (still a little experimental) then the server and client will translate the filenames between the server and client codepages. If you would like to contribute to the open source project, they may be contacted via the newsgroup: http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt or news://news.cvsnt.org/support.cvsnt If you have any questions about CVS Professional Support please do not hesitate to contact me. Regards, Arthur Barrett -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yves Dorfsman Sent: 06 September 2005 00:17 To: [email protected] Subject: CVS and unicode Hi, Has anybody run into problem with GNU CVS and unicode ? I have made a few tests (with UTF8) and so far it worked, but some of my users are saying they did run into problem with some files. I can see how some legal UTF8 characters could be confused as control code/binary. Does anybody have extensive experience with this ? Thanks. Yves. ---- Yves Dorfsman [EMAIL PROTECTED] http://www.cuug.ab.ca/dorfsmay http://www.SollerS.ca _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
