Re: Proposal for supporting WC file content encoding

To elaborate:

>Julian Foad wrote:
>
>> [...] To help describe the goals, it might be helpful to include
>> some "use cases", i.e. realistic concrete examples (like transcripts)
>> that demonstrate the various ways in which the user can interact with
>> this feature.

>[...] I saw that
>people were also requesting text support for UTF-16 and UTF-32, but t that
>it was argued that Subversion basically dealt with text as byte-oriented character data.

The use case here is that with this proposal, you could support UTF-16 just like any other encoding (even EBCDIC, if iconv or apr_iconv allows), as text, with the diff and merge (and other bonuses like HTTP viewing), as desired.

-Jesper

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 29 10:59:35 2006