Need to fix encoding issues that cause the pop-up for reporting errors to users to crash

[mpourmpoulis]

Occasionally when trying to report errors, some encoding issue happens in the pop up either does not appear or appears without the information it should have. The console Is also often polluted with stuff like

Parse Error: #x27;NoneType&#x27; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: 27;NoneType&#x27; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: 7;NoneType&#x27; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: #x27; code: Unknown entity
Parse Error: #x27; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: 27; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: 7; object has no attribute &#x27;string&#x27;</p> code: Unexpected character
Parse Error: #x27; code: Unknown entity
Parse Error: #x27;string&#x27;</p> code: Unexpected character
Parse Error: 27;string&#x27;</p> code: Unexpected character
Parse Error: 7;string&#x27;</p> code: Unexpected character
Parse Error: #x27; code: Unknown entity
Parse Error: #x27;</p> code: Unexpected character
Parse Error: 27;</p> code: Unexpected character
Parse Error: 7;</p> code: Unexpected character
Parse Error: #x27; code: Unknown entity

Need to fix this at some point

[mpourmpoulis]

after some experimenting, it turns out that this problem only appears when the error message Contains quotes that are escaped html.escape in a manner which the HTML engine does not like.

Fortunately,These problem has already appeared on the sublime forum can be solved by simply adding quote = False Parameter.