[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS and unicode

From: Spiro Trikaliotis
Subject: Re: CVS and unicode
Date: Sun, 11 Sep 2005 16:51:06 +0200
User-agent: Mutt/1.5.9i

Hello Christian,

* On Sun, Sep 11, 2005 at 03:07:14PM +0200 Christian Hujer wrote:

> > But that is the way CVS works now. The client *WILL* do this
> > modification.

> No, the windows client will only do this modification if you told the client 
> to do so. You can enable / disable this. The windows cvs client is able to 
> checkout non-"-kb"-files (text files) with LF without converting LF to CR/LF.
> At least this is true for WinCVS.

I don't consider WinCVS (that is, cvsnt) a cvs client. It is cvsnt, not
cvs, although it is compatible to a high degree.

> And afair cvs on Cygwin does not perform any CR/LF conversion at all.

Hm, well... I'm not sure if it is the CVS client on cygwin or cygwin
itself (if installed to utilize CR/LF endings), but on cygwin, this
conversion takes place.

Although CR/LF vs. LF is a problem in itself, I would not recommend
using cygwin and cvs in "LF only" mode. I have done so before, and I
encountered many problems this way, most often these were some garbled
output. It just does not work as it should.

Furthermore, the "natural" ending on Windows machines is CR/LF, if you
like it or not. It does not make much sense to use LF only and be
restricted to some specific editors and other programs which can handle
the LF only. Many programs will convert LF to CR/LF (or, even worse,
will behave erroneously), thus, this is not a good alternative.

BTW: Personally, I would consider a Windows program which cannot handle
CR/LF as broken. It is like I would tell you "I can speak chinese" but
not being able to understand or write even one sentence in it.

Best regards,

Spiro R. Trikaliotis                               

reply via email to

[Prev in Thread] Current Thread [Next in Thread]