Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1463 Save File and UnicodeDecodeError happens

Release_1.3.32
fixed-and-released
None
macosx
1
2013-10-13
2013-10-06
zhu zhaohua
No

When I save the file, error happens, and open the log file, I can see the error information, see follows:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 0: ordinal not in range(128)
Traceback (most recent call last):
File "taskcoachlib/thirdparty/smartdatetimectrl.pyo", line 1522, in OnLeftUp
File "taskcoachlib/thirdparty/smartdatetimectrl.pyo", line 1803, in
init
File "taskcoachlib/thirdparty/smartdatetimectrl.pyo", line 1586, in
init__
File "taskcoachlib/thirdparty/smartdatetimectrl.pyo", line 1808, in Fill
File "taskcoachlib/thirdparty/smartdatetimectrl.pyo", line 1828, in GetExtent
File "wx/_gdi.pyo", line 3752, in GetTextExtent
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 0: ordinal not in range(128)

I guess that it happens as I save the file as a Chinese name.

Discussion

    • assigned_to: Jérome Laheurte
     
  • No, Unicode filenames should work. This doesn't happen while saving but when drawing the date/time picker; I'm looking into it.

     
  • A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.

    If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.

    Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
    Thanks, Task Coach development team

     
  • This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?

    Thanks, Task Coach development team