RE: svn commit: r917772 - in /subversion/trunk/subversion/bindings/javahl: native/ src/org/apache/subversion/javahl/callback/ src/org/tigris/subversion/javahl/ tests/org/apache/subversion/javahl/

Bert Huijben wrote on Tue, 2 Mar 2010 at 09:39 +0100:
> > Maybe the svn:date we can presume a UTF-8 character set, but the
> > svn:author, svn:log we shouldn't.
>
> For the svn:* properties we currently define we declared that they
> always use utf-8 and use '\n' as line ending. Clients are responsible
> for handling the conversions. See svn_prop_needs_translation() for
> more details. (Since 1.6 we even validate this on the filesystem or ra
> layer).
>

The validation of properties is done in the repos layer, actually.
The FS layer doesn't assume that properties are in UTF-8. (It does
assume/enforce that pathnames inside the repository are in UTF-8.)

> For other properties and svn:* we haven't defined yet, we can't assume
> anything. Users might have their MP3 collection stored in them ;-)
> (Most clients I know use these same normalization rules on all
> properties they edit. E.g. TortoiseSVN doesn't support editing
> properties with Windows style line endings)
>
> Bert
>
>
Received on 2010-03-02 10:19:11 CET