On Jan 6, 2005, at 01:41, Branko Čibej wrote:
> Peter N. Lundblad wrote:
>
>> On Wed, 5 Jan 2005, Max Bowsher wrote:
>>
>>
>>> Peter N. Lundblad wrote:
>>> I agree with what you are saying, but what 2194 was saying was
>>> "UTF-16
>>> should be detected as textual".
>>>
>>>
>> Yes, it is more complicated than that, since it is an enconding where
>> a
>> line break is not one or two bytes, and for some other reasons.
>> Still, I
>> think we really need to support other Unicode encodings thatn UTF8,
>> like
>> we support other 8-bit encodings.
>>
> It is much more complicated than that. If we're to treat UTF-16 files
> as text, we have to teach libsvn_diff to do diffs and merges correctly
> on such files, and possibly enhance keyword expansion and newline
> conversion, too.
>
> In short, it's a whole can of worms that probably affects 90% of the
> client-side code.
When the rewrite of the client eventually happens design wide char
support in on day 1 then.
I do not expect a quick fix, but this issue should be nagging at svn
devos.
Barry
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 13:26:23 2005