I think you are correct, it is simplified Chinese. Actually reading
your links below UTF-8 seems to make more sense, and I think that it
will have the same end result. =20
Just a note, I did some looking into this awhile back and did a blanket
change to all streams to use UTF-8 (i.e. file encoding and commands
exchanged between the cvs servers). This was bad. It seems that the
cvs server is only able to accept commands in ASCII format but is able
to handle text files in different formats. So I guess I am saying if it
is reasonably easy to separate the two handlers (file and command send/
receive) then maybe we can change the file transfer to optionally use
UTF-8 and keep the command send/ receive as is. From what I understand
this also means that files/ directories are not sent in UTF-8 format, as
they are sent as part of the cvs command.
To answer the second half of this, I have not done extensive testing
with other cvs servers to see if they support Chinese lettering. It may
be worth sending YuSong an email as I think he has had experience with
> -----Original Message-----
> From: Nicklas Norling [mailto:exinor@...]=20
> Sent: October 16, 2004 11:57 AM
> To: sharpcvslib-developers@...
> Subject: [Sharpcvslib-developers] GB2312 support
> Hello szyusong.
> I've seen your email on the subject of supporting GB2312 (simplified=20
> chinese I think?).
> I have a few questions. I'm I correct in thinking you are=20
> interested in=20
> the content of the
> files and not file names or directory names? The CVS protocol only=20
> supports old ASCII
> 7-bit (ISO 646) http://www.cvsnt.org/cvsclient/Filenames.html.
> The proposed changes to the code default encoding would if I=20
> correctly encode
> every files content with GB2312, as that what you are=20
> suggesting? The CVS standard regarding file content=20
> transmissions are described in=20
> I think there might possible be a gap when it comes to UTF-8=20
> transmission, but I'm not
> entierly sure yet (need to understand more of the current=20
> code). If the text transfer was to support UTF-8 would that=20
> fit your demands=20
> with GB2312?
> Does any other CVS server/client support GB2312 correctly?
> This SF.net email is sponsored by: IT Product Guide on=20
> ITManagersJournal Use IT products in your business? Tell us=20
> what you think of them. Give us Your Opinions, Get Free=20
> ThinkGeek Gift Certificates! Click to find out more=20
> Sharpcvslib-developers mailing list=20