Ph. Marek wrote:
>>>> Read the docs: the svn:log property is documented and the docs clearly
>>>> state that the encoding must be utf-8.
>>> Yes, but *why* was UTF8 chosen? They could've used UCS-16, ASCII, EBCDIC or
>>> something else. "It works"!
>> Why do you even care why utf8 was chosen?
> and B): because of *compatibility*. If you wrote a new OS, would you call the
> function that's used to open files "open", or would you name
> it "GetHandleForAFile"?
> There've been *existing users* for these properties. Changing them would have
> broken their data.
> That's* not nice.
The svn:log property is documented as an *internal* property for
Subversion, not to be used directly by other applications. The only way
to use those is via the Subversion API.
Those who think they can do whatever they want with internal data (like
you) will lead to them having broken applications.
Don't blame others for not being nice if you're not even willing to
follow their rules.
>>> Did you never use a hex-editor on some 3rd party programs?
>> I do all the time.
> So you do? Why? Because if I read you correctly that's not the right way, is
> it? Why do you do this? For your private use?
Can you explain why using a HEX-Editor is 'not the right way'? You have
no idea what I'm using those for.
I guess for you the only way to use a hex-editor is to hack another
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-06 12:45:30 CEST