Eric Gillespie <epg@pretzelnet.org> writes:
> > Last I heard, someone really is using binary property values...
>
> Undoubtedly. Nevertheless, Subversion *is* useful to a large
> class of people without this feature. Therefore it should be
> post-1.0.
If I recall correctly, the issue is not about supporting binary
property values, but about ceasing to assume them (that is, to know
their mime-type and do UTF8 conversion on them where possible). The
fact that some people are already using binary properties means that
we can't just start unconditionally converting between native encoding
and UTF8, because then we'd corrupt those people's data. So we need
something more sophisticated, something that indicates when it's
appropriate to convert and when it's not, for an arbitrary user
property. That is the feature that has been punted to Post-1.0 -- not
binary props, but non-binary props :-).
None of which needs to affect issue #1025, of course. We need to
escape those property values for XML whether they're binary or not.
We might as well escape them as though they're binary, so that we
don't have to worry about that RA layer when we're figuring out what
to do about property policy from a user perspective.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 5 00:56:11 2003