Comment 2 for bug 77657

On ke, 2007-01-03 at 12:20 +0100, Wouter van Heyst wrote:
> Robert thought it wasn't sane to deal with a filename not decodable in
> the user encoding, where I just wanted that exact byte sequence checked
> in. At the very least that means the filename will be unintelligible on
> windows, macosx, or in any other encodings. Worse, it might not even
> check out at all. This is a general problem we also encounter with the
> illegal characters for fat, upper/lower case clashes or files called
> con.txt on windows.

I understand that point, but in contexts where I as a user am not
concerned with the interoperability of my filenames with other systems
than Unix, I wish I would be able to use them with bzr as well.

If the restriction stays in bzr, it should at least be prominently
documented in the manual page. Oh, and the error message could be
better, too. :)

--
"Quack, damn you!" -- Jamie Hyneman