For `merge --preview` I think we should do the same as for `diff`, e.g. use mbcs encoding on Windows.
For `log -p` I'm inclined to use terminal_encoding instead of mbcs, because there is other unicode output encoded in terminal_encoding.
The hardest thing is `send`. I think by default there is should be `utf-8` because it supposed to be bzr (machine) readable.
For `diff`, `log -p`, `merge --preview` and `send` I would like to introduce new command-line option --path-encoding to control the encoding of filenames in diff headers.
It seems my patch won;t be accepted to 2.1, so introducing new option is fine for bzr.dev, IMO.
For `merge --preview` I think we should do the same as for `diff`, e.g. use mbcs encoding on Windows.
For `log -p` I'm inclined to use terminal_encoding instead of mbcs, because there is other unicode output encoded in terminal_encoding.
The hardest thing is `send`. I think by default there is should be `utf-8` because it supposed to be bzr (machine) readable.
For `diff`, `log -p`, `merge --preview` and `send` I would like to introduce new command-line option --path-encoding to control the encoding of filenames in diff headers.
It seems my patch won;t be accepted to 2.1, so introducing new option is fine for bzr.dev, IMO.