[Top][All Lists]

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

Re: CVS and unicode

From: Mark D. Baushke
Subject: Re: CVS and unicode
Date: Tue, 06 Sep 2005 08:58:58 -0700

Hash: SHA1

Yves Dorfsman <address@hidden> writes:

> > CVSNT for Linux/Unix/Mac/Windows is free (GPL - just like CVS) but
> > supports the -ku type (unicode) which allows efficient storage, diff's,
> > merges etc - just like a text file but as unicode.
> >
> >
> > If you run the CVSNT server in unicode mode (still a little
> > experimental) then the server and client will translate the filenames
> > between the server and client codepages.
> Any reason why the GNU CVS project is staying away from integratig
> unicode ?

My recollection is that the divergence from some of the borrowed GNU
projects (GNU DIFF and GNULIB) to support UNICODE was kind of large.

Recently, GNULIB has started to provide more support of multi-byte
characters, so it may not be as big a deal as it once was.

Personally, I'd rather see the forked GNU DIFF code in CVS updated to a
more recent vintage before possibly forking it again for UNICODE
support. I don't have time to do either of those right now, so I'll let
someone else worry about it.

Much of the CVSNT code has moved from C89 to C++, so it is not
necessarily a direct patch. For example, the CCodepage package functions
used by CVSNT are generally available functions in C89 libraries...

The CVSNT code is still a bit experimental and I would rather see the
code more stable before trying to re-implement in CVS, so that the
client/server would be interoperable for CVSNT and CVS.

> Is this intentional, or just because nobody's done it ?

Nobody has done it. However, it will want another audit done of the code
path handling for safety to avoid any of the unicode pathname games that
have abused other protocols and programs that were early unicode

> Would it'd be worth starting to work on this ?

Contributions of patches greatfully accepted.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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