> 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.
Makes sense. > 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. Any reason why the GNU CVS project is staying away from integratig unicode ? Is this intentional, or just because nobody's done it ? Would it'd be worth starting to work on this ? 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
