© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Please check first. It IS a bug within optparse since we’re not passing Unicode data directly to optparse, thus cannot control what kind of string is passed. We simply let gettext replace messages with translations before outputting which is why optparse fails unable to handle non-ASCII strings here.