P1tr

factoids plugin cannot handle non-ASCII chars

Bug #210478 reported by Michael Otteneder
2
Affects Status Importance Assigned to Milestone
P1tr
Invalid
Medium
Chris Ortner
P1tr beta

Bug Description

If somewhere in a factoid a non-ASCII char is present the plugin gets flakey. It does not output the strings containing the non-ASCII chars.

Michael Otteneder (m-otteneder)
Changed in p1tr:
assignee: nobody → c-ortner
importance: Undecided → Medium
Revision history for this message
Chris Ortner (c-ortner) wrote :

Will be doing it in time.

Changed in p1tr:
milestone: none → beta
status: New → In Progress
Revision history for this message
Chris Ortner (c-ortner) wrote :

This issue seems to be platform dependent. On Linux, using Python 2.5.2, and LANG=en_US.UTF-8 everything is fine:
[18:52] <mrc_001> *P1tr is böse
[18:52] <p1tr> Memorized.
[18:52] <mrc_001> *P1tr? 10-10
[18:52] <p1tr> [10] p1tr is böse
It is possible that Mac has a strange pov concerning encodings.

Changed in p1tr:
status: In Progress → Invalid
Revision history for this message
Michael Otteneder (m-otteneder) wrote :

In the current revision it is working on mac too.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.