Yes, it seems to. If you manually add UTF-16 file - it will be saved
as "octet-stream". But in my case it was usual source file .cpp. And
one time, in a moment it became UTF-16LE encoded by MS Visual Studio -
without any notices. Yes - it still .cpp file, and - (because recent
windows works well with unicode) it looked the same in other editors -
Notepad, for example. And - it was correctly commited to SVN and
worked fine during months - untill the very moment when I try to make
a patch from "mixture" of files. By the way - since it wasn't placing
originally UTF-16 file into repository, but changing the encoding of
already existing file - svn doesn't assign the "octed-binary" mime to
this file.
But - anyway - I think it would be well at least recognize unicode
files and warn about them. If usual works (NOT hacking) cause an error
- I think this thing needs to be assisted from developers. Isn't it?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-17 13:06:37 CEST