Comment 7 for bug 1022593

Revision history for this message
Daniel Manrique (roadmr) wrote :

Looks like changing the explicit "ascii" decoding on line 47 so it uses utf-8 instead may solve this problem. I'll try to get a fix submitted in a while.

I'll set this to triaged. Thanks for the info!