Barry Scott wrote:
> maxb said this is an invalid as an issue and I should read the red text
> on
> the issues page. Nothing in the FAQ, No existing issue so I guess I need
> to mail the details to users.
>
> I create three test unicode files on windows using notepad.
> Encoded as UTF-8, UTF-16 LE and UTF-16 BE.
>
> The UTF-8 file was added as text. But both UTF-16 files are
> treated as binary.
>
>> svn add utf8.txt utf16-be.txt utf16-le.txt
> A utf8.txt
> svn: File 'utf16-be.txt' has binary mime type property
>
> I would guess that utf32 files are also treated as binary.
Indeed, it is invalid as an issue at this stage, because it requires
discussion.
For example, I would that UTF-{16,32} are effectively binary files, in many
ways.
They can't be diffed, unless you teach the diff program what a lineend is in
the new format, and they can't be displayed on most terminals, nor easily
shown in email.
They require special editors/viewers, just like MSWord docs require special
editors.
Anyway, that's my opinion.
I think if svn is going to start treating UTF-16 as text, it at least needs
to be taught to diff it properly.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 5 19:54:57 2005