| 2009-03-10 09:36:42 |
Timmie |
bug |
|
|
added bug |
| 2009-03-18 09:44:52 |
Timmie |
bug |
|
|
added attachment 'bzr_encode_test.zip' (self contained example) |
| 2009-03-20 01:50:07 |
Martin Pool |
bzr: status |
New |
Incomplete |
|
| 2009-04-07 11:16:54 |
Timmie |
bzr: status |
Incomplete |
Confirmed |
|
| 2009-04-07 11:17:16 |
Timmie |
bzr: assignee |
|
mbp |
|
| 2009-04-07 11:46:32 |
Ian Clatworthy |
tags |
|
log |
|
| 2009-04-08 05:29:08 |
Martin Pool |
bzr: importance |
Undecided |
Medium |
|
| 2009-04-08 05:29:08 |
Martin Pool |
bzr: assignee |
mbp |
|
|
| 2009-04-08 05:29:32 |
Martin Pool |
summary |
log output should be saved in user defined encoding |
redirecting log output to a file produces the wrong encoding on win32 |
|
| 2009-04-08 05:30:37 |
Martin Pool |
description |
When saving the log output to a file, this should be saved in UTF-8 encoded form.
Please also refer to:
https://answers.edge.launchpad.net/bzr/+question/63601 |
"bzr log > log.out" on win32 where the commit messages contain non-ascii characters seems to produce invalidly encoded output. It works correctly on Linux, and it produces the correct output in a cmd.exe window.
----------------
When saving the log output to a file, this should be saved in UTF-8 encoded form.
Please also refer to:
https://answers.edge.launchpad.net/bzr/+question/63601
|
|
| 2009-04-08 05:30:37 |
Martin Pool |
tags |
log |
log win32 |
|
| 2009-04-08 10:56:05 |
Timmie |
attachment added |
|
changelog_test.txt http://launchpadlibrarian.net/25011603/changelog_test.txt |
|
| 2009-04-09 02:25:25 |
Martin Pool |
summary |
redirecting log output to a file produces the wrong encoding on win32 |
redirecting log output to a file produces cp850 on win32 |
|
| 2009-04-21 11:18:09 |
Martin Pool |
summary |
redirecting log output to a file produces cp850 on win32 |
want an option to set the output encoding, especially on win32 |
|
| 2009-07-09 03:41:40 |
Martin Pool |
description |
"bzr log > log.out" on win32 where the commit messages contain non-ascii characters seems to produce invalidly encoded output. It works correctly on Linux, and it produces the correct output in a cmd.exe window.
----------------
When saving the log output to a file, this should be saved in UTF-8 encoded form.
Please also refer to:
https://answers.edge.launchpad.net/bzr/+question/63601
|
Sometimes people want to produce output in an encoding that's not their system default, or to produce squashed output from strict commands or vice versa. It would be good if there was an option to do this.
-------------
"bzr log > log.out" on win32 where the commit messages contain non-ascii characters seems to produce invalidly encoded output. It works correctly on Linux, and it produces the correct output in a cmd.exe window.
----------------
When saving the log output to a file, this should be saved in UTF-8 encoded form.
Please also refer to:
https://answers.edge.launchpad.net/bzr/+question/63601
|
|
| 2009-07-09 03:41:40 |
Martin Pool |
tags |
log win32 |
unicode win32 |
|
| 2010-05-15 06:16:08 |
Martin Pool |
bzr: assignee |
|
Martin Pool (mbp) |
|
| 2010-05-15 06:16:10 |
Martin Pool |
bzr: status |
Confirmed |
In Progress |
|
| 2010-08-06 19:01:19 |
John A Meinel |
bzr: status |
In Progress |
Fix Released |
|
| 2010-08-06 19:01:19 |
John A Meinel |
bzr: milestone |
|
2.2.0 |
|
