Re: Don't define _i18n to _T...

> >This is wrong, because _T is a way for switching between
> >non-UNICODE builds and UNICODE builds, not for nls,
> >Such define avoids supporting nls for WinCvs.
> 
> Does that cause any real problem?

Not at all ;) It is simply wrong.


> WinCvs doesn't support UNICODE build(.snip.)

Yes. And shouldn't, if we won't give up supporting win9x.


> I am not able to support any particular version so it can only 
happen if
> there is a person to maintain. So if you are ready for such 
commitment I
> would simply give you the write access to the repository so you 
could apply
> the changes ;)

Ah, thank you. Actually we are glad if so, because `my particular 
version' is currently:
#ifdef JP_STRING
    cvs_err("..."); // Japanese string(multi-byte)
#else
    cvs_err(_i18n("error..."));
#endif

When I am ready, I will ask you. (Though I can't do so rapidly ;)

> How big is the change? Does it require some changes to CVSNT
(cvs.exe) binary
> as well?

If the meanings is `preparing nls', the changes will be:
* add libintl Library
* change project file for using libintl
* add the preference for changing locale
* (maybe it require some changes to installer if we will support 
  default message catalogs.)

Of cource, to complete the work we have to replace any string
which we want to translate any languages to _i18n().

# I have no patch for current CVSNT but for cvs2ntlib.dll of WinCvs 
# 1.2 age. And I can't maintain current CVSNT because my developping 
# environment are still VC6.




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/