[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: eol-style and utf-16

From: engelbert gruber <engelbert.gruber_at_gmail.com>
Date: Tue, 31 Oct 2017 12:17:09 +0100

sorry one more

On 30 October 2017 at 21:57, engelbert gruber <engelbert.gruber_at_gmail.com>
wrote:

checking in a file with eol-style native on unix : eol = 0x0a
> checking it out on windows : 0x0a is replaced by 0x0d 0x0a
>
> when the file is in utf-16 : eol ist 0x00 0x0a
> and when checked out on windows this becomes : 0x00 0x0d 0x0a
>
> which breaks utf-16 as far as i understand it
>
> possible fixes:
>
> * get utf-## aware
> * add a charsize property
> * document it
> * recommend eol-style a nonnative eol-style: LF CR or CRLF
>
>
* turning of eol-style is an option, but not in general, as subversion
comes with eol-style native
  (i like to stick with defaults, to ease setting up systems and because
subversion-maintainers
  are more knowledgable than me)

setting svn:mime-type to 'application/octet-stream' shouldn't be necessary
if
http://help.collab.net/index.jsp?topic=/faq/svnbinary.html

  Currently, Subversion only looks at the first 1024 bytes of the file; if
any of the bytes are zero,
  or if more than 15 percent are not ASCII printing characters, then
Subversion calls the file binary.

is correct. by this utf-16 will always be binary.
mine was a csv-file, but the problem might be that it was imported from a
CVS-repo

cheers

> e
>
Received on 2017-10-31 12:24:02 CET

This is an archived mail posted to the Subversion Users mailing list.