> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
> Sent: zondag 1 september 2013 0:21
> To: Edoardo Pinci
> Cc: users@subversion.apache.org
> Subject: Re: SVN commit line ending handling
>
> On Aug 31, 2013, at 05:29, Edoardo Pinci wrote:
>
> > I periodically receive this kind of errors since a long time.
> >
> > X:\>svn commit -m "BLA BLA" itextsharp.dll iTextSharp.xml
> > Sending iTextSharp.xml
> > Sending itextsharp.dll
> > Transmitting file data ..
> > svn: E135000: Commit failed (details follow):
> > svn: E135000: While preparing 'iTextSharp.xml' for commit
> > svn: E135000: Inconsistent line ending style
> > svn: E720032: Additional errors:
> > svn: E720032: Transaction '1718-1ca' cleanup failed
> > svn: E720032: Can't remove file 'Depot\db\txn-protorevs\1718-1ca.rev':
> The process cannot access the file because it is being used by another
> process.
> >
> > Question 1: Is there a way to have SVN normalize line ending on commit
by
> itself?
>
> It seems svn:eol-style is set on this file. If you set svn:eol-style on a
file (to
> any supported value), Subversion requires that the file have consistent
line
> endings before you commit it. You or your tools must do this; Subversion
will
> not.
Not only that: Subversion also assumes that your file is ascii-like text
e.g. UTF-8.
UTF-16 (or UCS-2) doesn't work in that context as it usually has a lot of
'\0' bytes and a bytewise completely different eol marker.
Bert
