[MERGE] Make annotate behave in a non-ASCII world

Aaron Bentley aaron.bentley at utoronto.ca
Wed Jul 11 20:20:17 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Goffredo Baroncelli wrote:
> this class returns always an unicode string. If the string passed to this 
> wrapper is an internal bazaar [meta]data (as user name or path which are 
> unicode string), the data are stored "as is". If the data is a string, the 
> data are _decoded_ with the selected encoding, then it is stored. 
> 
> Any thougts

I think this is backwards.  You frequently don't know what the encoding
of your data is, e.g. with patches.  An even if you do know, it may vary.

It's much saner to turn unicode into the terminal encoding, which we
always do know.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGlS1x0F+nu1YWqI0RAtoVAJ4oHrD3XZFJ72k9QAfw9NNZVoL0tACfQSM/
iHnQr7JVpytmw+TvKS6Iw3g=
=l3Im
-----END PGP SIGNATURE-----



More information about the bazaar mailing list