On 2005-08-24 12:40:13 +0200, Servatius.Brandt@fujitsu-siemens.com wrote:
> 1st problem:
>
> I have an XML file in UTF-16 encoding, little endian. It starts with
> a BOM FFFE at the beginning of its first line, which is:
>
> <?xml version="1.0" encoding="UTF-16"?>
>
> The "svn add" command sets the property svn:mime-type to
> application/octet-stream. I consider this a bug. It prevents the "svn
> diff" command from working. The problem is on a Windows system, and the
> file has CRLF line endings.
afaik svn doesnt handle utf-16 yet. so far i know utf-16 can have
sequences which look like binary to svn though that is the safer way.
> 2nd problem:
>
> To work around the first problem, I can change the svn:mime-type to
> text/xml,
> then the "svn diff" works fine. But it is not possible to set the
> svn:eol-style to CRLF, which is the line endings style used by the file.
same as above... if you set an explicit EOL style svn will on commit
unify all lineendings to "\n" in the file before uploading it the
repository. on checkout the CRLF will be restored. to be on the safe
side svn does a binary check again. and so the same problem as mentioned
above kicks in. if you file is CRLF anyway, you dont need to set this
property.
hope this helps
darix
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 24 13:33:02 2005