Summary: | bugzilla-tool hates Tor Arne Vestbø | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Adam Barth <abarth> | ||||
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ddkilzer, eric, vestbo | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Adam Barth
2009-08-02 00:52:30 PDT
The wisdom of the web says this should fix it: - print line.replace("NOBODY (OOPS!)", reviewer), + print line.replace("NOBODY (OOPS!)", reviewer.encode("utf-8")) Created attachment 33951 [details]
Patch v1
Reviewed by NOBODY (OOPS!).
* Scripts/bugzilla-tool:
(set_reviewer_in_changelog): Made sure reviewer is properly
encoded when calling replace().
---
2 files changed, 11 insertions(+), 1 deletions(-)
Comment on attachment 33951 [details] Patch v1 Clearing review flag on attachment: 33951 Committing to http://svn.webkit.org/repository/webkit/trunk ... M WebKitTools/ChangeLog M WebKitTools/Scripts/bugzilla-tool Committed r46700 M WebKitTools/ChangeLog M WebKitTools/Scripts/bugzilla-tool r46700 = eb267d44bd231e0ebd2bff224253aeef38af6591 (trunk) No changes between current HEAD and refs/remotes/trunk Resetting to the latest refs/remotes/trunk http://trac.webkit.org/changeset/46700 All reviewed patches have been landed. Closing bug. Does bugzilla 3.0 now have everything encoded as utf8 now? You would think in this modern world we wouldn't have to re-encode everything all the time. ;) (In reply to comment #5) > Does bugzilla 3.0 now have everything encoded as utf8 now? You would think in > this modern world we wouldn't have to re-encode everything all the time. ;) We're using Bugzilla 3.2, and yes, the UTF-8 encoding option is enabled for bugs.webkit.org. The other thing I just realized is that I landed the patch with "old" version of this tool, and it worked just fine. Maybe it's related to Adam's local setup? (In reply to comment #6) > The other thing I just realized is that I landed the patch with "old" version > of this tool, and it worked just fine. Maybe it's related to Adam's local > setup? It's possible. I just use a mac. Maybe the system version of python needs an upgrade? I've never touched my system version of python, and I've not had trouble. But this change is also fine. :) |