Closed manenko closed 11 years ago
What happens if you get rid of str() all together? I'm not sure any of those str() calls are necessary. I'm used to languages where the mindset is to enforce type safety before continuing on, but the Python way appears to be just to let it go and if it fails it fails. Removing the str() calls all together might make more sense.
They are not necessary and removing 'str' should fix unicode support.
Can you provide me with your template test case that is failing so I can make sure my fix solves your issue?
Could you push this fix to support unicode strings?
Hello,
I tried to use i18n and non-ASCII symbols for _previouslabel, _nextlabel, etc. and got UnicodeEncodeError:
The problem is in code like this: previous_label = str(kwargs.get("previous_label", "←"))
I replace str with unicode and everything works fine.