[cvsnt] Re: Unwanted translated socket error message

[Wu Yongwei]

Thanks, Tony, for replying.

Tony Hoyle wrote:
>>I was often annoyed by the rubbish error message if a network error
>>occurred.  (Well, not really rubbish error messages, but Chinese messages
>>in a context that does not like Chinese, e.g., a CP437 console, or a
>>UTF-8 Vim.)  Now I downloaded the CVSNT 2.5.02.2099 source and found
> 
> There are *far* too many error messages to start translating them all
> manually.

No, not many. And a sock_strerror function containing 51 mappings is 
already available in GPL:

http://cvsweb.xfree86.org/cvsweb/*checkout*/cvs/windows-NT/sockerror.c?rev=HEAD

If you are worried with copyright issues, I am even willing to write a 
new version based on manually testing every socket error code on a 
English Windows XP box.

> And what are you going to do about filenames?  If you're working in
> chinese then you need your ANSI codepage to be chinese too for that.

If I used Chinese names with CVSNT, I wouldn't use a CP437 console. To 
work reliably in a multi-locale environment, it is important not to use 
non-ASCII characters in file names, otherwise some files cannot be 
opened by non-Unicode applications (still there are many) in some locales.

> If your calling program is not using the current ANSI codepage then fix
> your program - cvsnt is doing the right thing.

I dare say you do have your points. However, I think I have some points 
too. If CVSNT were a GUI application, I might never have asked for the 
change at all. Since it is not ...:

1) Using a non-default code page (like CP437) is allowed and normal 
under Windows, esp. considering that Windows will force the code page to 
437 if a DOS application (like edit, arj, f-prot, etc.) is invoked. Some 
applications, like hiew, works well only under CP437.

2) All messages in CVSNT is in English. Why should the error messages be 
an exception? I was really expecting all English messages. I cannot find 
a workaround to make it English.

3) CVS is already doing this (this might be the last `feature' I like 
CVS better than CVSNT).

4) Fixing other applications is more difficult than changing CVSNT in 
this case, and there might be too many applications to `fix'. For one 
thing, I even do not know how to detect the `ANSI' code page in Vim 
scripting (there are more things to do than that if I want to make the 
Chinese message correct in a UTF8-encoding Vim with a CVS integration 
script).

> Tony

Thank you again for reading and pondering on this issue.

Best regards,

Yongwei