[PATCH] Commit and log commands: strings encodings

[John A Meinel]

Robey Pointer wrote:
> 
> On 1 Dec 2005, at 11:03, Alexander Belchenko wrote:
> 
>> John A Meinel пишет:
>>> 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.
>>
>> '-i' and '-o' is used in docutils as encoding options.
>> We discuss this options earlier, see:
>> http://lists.ubuntu.com/archives/bazaar-ng/2005q3/003106.html
>>
>> Just FYI, I found only 3 commands in current bzr.dev that have options
>> started at 'o' or 'i':
>>
>> * `pull` have option `overwrite`
>> * `ls` have option `ignored`
>> * `selftest` have option `one`
> 
> 
> There are only a handful of meaningful one-letter options, though, so we
> don't want to use them all up.
> 
> It sounds like maybe Windows has the same problem as python 2.4 on OS X:
> the correct encoding can't always be guessed.  In which case maybe it
> makes sense to expose an environment variable to override it.  Something
> like
> 
> $ export BZR_ENCODING=en_US.UTF-8
> $ bzr do-stuff...
> 
> Is anyone opposed to that?
> 
> robey
> 
> 

I think we would need BZR_INPUT_ENCODING and BZR_OUTPUT_ENCODING (with
perhaps the default of BZR_ENCODING)

But I think it is nicer than always suppling -o/-i

John
=:->


-------------- 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/2bcdb7db/attachment.pgp