You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The essential problem here is that a unicode string (in python 3) is interpreted as a string that is a series of bytes (in the c-api). I believe that the solution, especially for the old, 256 character non-unicode aware fonts, is to convert the incoming string into a latin-1 encoded bytes object, which should be easily used as a uchar *.
This is likely a unicode issue somewhere.
In Py2.x, results are as expected. In Py3.x, the high ascii characters are not printed as expected.
excerpted and modified from test_font_pcf.py
Incorrect:
![incorrect](https://camo.githubusercontent.com/3e70f018a6bf8e7ba426e2d0627c4baadce54c5ea42d9b7afb943d0f4639c294/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f31393739322f323031353237352f61303135623435652d383762362d313165332d393038662d3766646561336464386464392e706e67)
![correct](https://camo.githubusercontent.com/fbd826e9a8e494bbdbb90317f30a0b934ffeef6918289ff2562ab643b13f8dcb/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f31393739322f323031353238312f63613137623463382d383762362d313165332d386161362d3930313664316334623833612e706e67)
Correct:
The generated temp fonts are the same, It appears to be an issue in the rendering.
This was reported in IRC by AleXoundOS, hoisted here to document.
The text was updated successfully, but these errors were encountered: