[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS and unicode
From: |
Pierre Asselin |
Subject: |
Re: CVS and unicode |
Date: |
Sat, 10 Sep 2005 23:53:00 +0000 (UTC) |
User-agent: |
tin/1.6.2-20030910 ("Pabbay") (UNIX) (NetBSD/2.0 (i386)) |
Christian Hujer <address@hidden> wrote:
> [ ... ] The CRLF byte sequences are:
> ASCII: 0x0D 0x0A.
> UTF-8: 0x0D 0x0A.
> UTF-16 LE: 0x0D 0x00 0x0A 0x00.
> UTF-16 BE: 0x00 0x0D 0x00 0x0A.
> CVS will not interfer with any of these.
> UTF-16LE sequence will be split within the LF char. But since the next line
> will be split at exactly the same point, this is not a problem for line
> diffs.
An UTF-16 file can contain octet sequences like (xx 0D)(0A yy) that
CVS will mistake for line endings. It will confuse diff, and if
a Windows client strips the "0D" upon commit and a Unix client
tries to update, the contents will look seriously scrambled...
--
pa at panix dot com
- CVS and unicode, Yves Dorfsman, 2005/09/05
- Re: CVS and unicode, Sergei Organov, 2005/09/06
- Re: CVS and unicode, Christian Hujer, 2005/09/07
- Re: CVS and unicode, Arno Schuring, 2005/09/08
- Re: CVS and unicode, Christian Hujer, 2005/09/10
- Re: CVS and unicode, Spiro Trikaliotis, 2005/09/10
- Re: CVS and unicode, Christian Hujer, 2005/09/10
- Message not available
- Re: CVS and unicode,
Pierre Asselin <=
- Re: CVS and unicode, Christian Hujer, 2005/09/11
- Re: CVS and unicode, Spiro Trikaliotis, 2005/09/11
- Re: CVS and unicode, Christian Hujer, 2005/09/11
- Re: CVS and unicode, Larry Jones, 2005/09/11
- Re: CVS and unicode, Christian Hujer, 2005/09/11
- Re: CVS and unicode, Arno Schuring, 2005/09/11
- Re: CVS and unicode, Christian Hujer, 2005/09/12
- Re: CVS and unicode, Spiro Trikaliotis, 2005/09/13
- Re: CVS and unicode, Larry Jones, 2005/09/12
- Re: CVS and unicode, Christian Hujer, 2005/09/12