Comment 3 for bug 472161

Lon story short: the bzr ftp transport don't support unicode paths.
The root cause is that some ftp servers don't support them either and even the ftp
spec if far from clear about UTF8 support.
I'll mark this bug as affecting bzr too as that's where the bug should/could be fixed but bzr itself
uses only ascii file names for its own purposes.

It should be possible to fix the issue in bzr though but until then, the best you can do is:
1) avoid using non-ascii filenames (sorry for that :-/)
2) ensure your ftp server supports unicode filenames and report anything relevant in this bug

By relevant I mean at least: OS/version where the ftp server runs, what ftp server it is,
a log of successful dialog between the client and the server for such a file, any format will do as long as
it makes it clear what format is used to exchange the filename between the client and the server (presumably utf8).