On Jan 5, 2005, at 10:50 AM, Max Bowsher wrote:
> 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.
As an additional data point, almost all text editors on Mac OS X can
read UTF-16 (and presumably other UTF variants as well). In addition,
many of the files used in day-to-day development of Mac OS X software
are UTF-16 files (e.g. .plist and .strings files). Having UTF-16
support in subversion would be a major improvement for Mac OS X.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 6 18:07:19 2005