On 1 November 2011 20:01, Adi Roiban <email address hidden> wrote:
> Maybe trying C and if failed then try UTF-8 would help, but a way for
> users to control and configure the filesystem encoding is desirable.
That's the point of this bug.
> After I removed that file from my bzr branch, bzr is working again, but
> the bzr status is not displaying the right filename.
>
> $ rm test_data/users_files/test_user/test_file\310\233.txt
> $ bzr st
> removed:
> test_data/users_files/test_user/test_file?.txt
If you're using a C (ascii) locale, bzr will only write ascii to
stdout, so it is replacing the accented character with '?'.
On 1 November 2011 20:01, Adi Roiban <email address hidden> wrote:
> Maybe trying C and if failed then try UTF-8 would help, but a way for
> users to control and configure the filesystem encoding is desirable.
That's the point of this bug.
> After I removed that file from my bzr branch, bzr is working again, but users_files/ test_user/ test_file\ 310\233. txt users_files/ test_user/ test_file? .txt
> the bzr status is not displaying the right filename.
>
> $ rm test_data/
> $ bzr st
> removed:
> test_data/
If you're using a C (ascii) locale, bzr will only write ascii to
stdout, so it is replacing the accented character with '?'.