[PATCH] Commit and log commands: strings encodings

[John A Meinel]

Alexander Belchenko wrote:
> Robey Pointer пишет:
>> On 24 Nov 2005, at 7:43, Alexander Belchenko wrote:
>>> This patch provide 2 new global options:
>>> --input-encoding or -i
>>> --output-encoding or -o
>>>
>>> Output encoding used for encoding log message.
>>
>> Could we just support flags for overriding the input and output 
>> encodings into UTF-8, and then rely on iconv to do more complex 
>> encoding?
>>
>> $ bzr log --utf8 | iconv -f utf-8 -t iso-8859-15
>>
>> Just thinking out loud -- it would be nice to avoid tackling every 
>> problem that another tool has solved for us.
> 
> I disagree.
> Windows has not built-in iconv utility, so it need to download
> separately (or bundled in distributive as svn does?). On the other hand
> Python have all this functionality inside. I beleive these options
> (--input-encoding and --output-encoding) will be useful for IPC and
> using bzr by external tools. But I can add and --utf8 option if you
> think that `-outf8` is long typing ;-)

I also think that python has decent handling of encodings, so we don't
need to use iconv for the extra work.

And I'm for a patch which sets the input and output encoding.

However, I would not use '-i' and '-o' for this. -i and -o are short
flags that are desirable for lots of options, and I don't think forcing
the encoding is an option that should generally be supplied.

John
=:->

> 
> Alexander
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051201/5e7f02ea/attachment.pgp