Re: svn prop*-commands not filtering encoding

> subversion properties are byte streams. You could store jpegs in a 
> property if you like to do so.
> That's why properties don't have an encoding specified, unless you do 
> so yourself (for custom properties).
> However: the properties with names that start with 'svn:' are defined 
> as utf8 strings. And the TSVN properties that start with 'tsvn:' are 
> also defined as utf8 strings.
> But that's only the definition - whether you actually pass utf8 
> encoded strings to the functions is up to you.
>
>
OK, with this definition it is only poorly documented. And we've to take 
care for the encoding by our self.

Thanks for clarifying.

Cheers

Torax

-- 
You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/tortoisesvn-dev/92e0ab8a-73d2-4a33-a1f5-525c0ecff4ff%40googlemail.com.