2012-09-22 05:26 AEST by Glen Starrett - If you put the line "cvs --utf8" in the user's .cvsrc file in HOME, CVS Suite
will NOT treat all commands as utf8.  

Also, .cvsrc does not like being unicode.  If you try to create .cvsrc at a
unicode command prompt (cmd /u) with a simple command like "echo cvs --utf8 >
.cvsrc" the file will be created as unicode and not understood by CVS.

2012-09-22 05:30 AEST by Glen Starrett - Sample output:

>>>>
C:\Documents and Settings\Administrator\My Documents\cs\test4a>type "%HOMEPATH%\
.cvsrc"
cvs --utf8
status -q

C:\Documents and Settings\Administrator\My Documents\cs\test4a>cvs status
? ??? xiàngxíngzì.txt
? ??? zhishìzì.txt
? stat.txt
cvsntsrv server: Examining .
cvsntsrv server: warning: 指事字 zhÇshìzì.txt is not (any longer) pertinent

File: no file 指事字 zhÇshìzì.txt          Status: Entry Invalid
cvsntsrv server: warning: 象形字 xiàngxíngzì.txt is not (any longer) perti
nent
File: no file 象形字 xiàngxíngzì.txt              Status: Entry Invalid

C:\Documents and Settings\Administrator\My Documents\cs\test4a>cvs --utf8 status

? stat.txt
cvsntsrv server: Examining .
File: 指事字 zhǐshìzì.txt  Status: Up-to-date
File: 象形字 xiàngxíngzì.txt       Status: Up-to-date
<<<<

FYI, I confirmed that the cvsrc is being found / used.  If I change the first
line in .cvsrc to "cvs --utf8 -H", the commands all output help.  Also, it's
contents are listed in a trace.