> Unfortunately I have not managed to get to the bottom of how
> or why subversion <-> httpd is mangling the password and what
> (if anything) subversion (or neon or serf?) could change to
> fix this...
It is not about mangling, it is about character encoding.
About 20 years after the birth of unicode (the encoding to
rule them all :-) there are still way too many programmers
around who are not even aware of the fact that there is
something like an encoding or worse, different encodings
to distinguish and to choose from.
And if you write program code or english texts, you don't see
any differences most of the time. If your keyboard does not have
keys that map to anything beyond Unicodepoint 128,
you'll never have problems with passwords.
The problem with passwords is that you normally can't see them.
So you can't see that there is some garbage where you expected
a pound sign.
I found this article
on how subversion treats encoding for file names
(once you think about it, you know that this is an issue).
It seems to use UTF-8 internally throughout.
I didn't understand references to collab.net in this article, though.
So I would bet that subversion translates your password from
Windows Western Europe (code page 1252) to UTF-8 and the others
copy them verbatim.
Received on 2012-04-26 15:22:40 CEST