Since 3.5.2 non ascii chars missing about canto-curses HOT 11 CLOSED

In red encircled should be a char (and they existed in the past).
And it happens for every feed

from canto-curses.

This isn't canto or Python breakage AFAICT, I can see those characters just fine with latest canto-curses and Python 3.5.2 here on Arch and even using Golem.de feeds.

Things I would try, although they're longshots:

• check locale, /etc/locale.gen, etc. to make sure your terminal locale didn't change. Canto uses LC_ALL, and it should probably be a UTF-8 locale regardless of base language.
• check that the locale has been generated (sudo locale-gen)
• try canto-curses in a known good terminal, like uxterm or urxvt (both work here)

If these don't work it would be interesting to know for certain that downgrading to Python 3.5.1 fixes it, or if other rich console apps (like elinks) are having the same issue.

from canto-curses.

Happens with every terminal and locales are generated.
But the LC_ALL seems to be case.
Everything is set with the locale of choice. LC_ALL is empty.. The hell?

from canto-curses.

To make it even more curios. Downgrading to 3.5.1 and the chars appear again with the same locale settings

from canto-curses.

Did setting LC_ALL fix it on 3.5.2?

from canto-curses.

Nope. Chars are still missing then, hm

from canto-curses.

Looking through the 3.5.2 changelog, here's a shot in the dark: what does this command output on both versions?

python -c 'import sys; print(sys.stdout.encoding, sys.stdout.errors)'

Here I get "UTF-8 strict"

from canto-curses.

For both versions the same result:

$ python --version
Python 3.5.1
~ $ python -c 'import sys; print(sys.stdout.encoding, sys.stdout.errors)'
UTF-8 strict
~ $ python --version                                                     
Python 3.5.2
~ $ python -c 'import sys; print(sys.stdout.encoding, sys.stdout.errors)'
UTF-8 strict

Maybe it's an error within the i686 package

from canto-curses.

Possible, I'm totally 64 bit here.

from canto-curses.

And doesn't happen for me on armv7h too.
So, just i686 until now

from canto-curses.

After the python 3.6 update on i686 the non ascii chars still are missing, but this time "placeholder" like "you used the wrong encoding to decode this stuff" appear.
But as armv7h and my new x86_64 machine show it totally fine, it's imo not worth to track the issue any longer. So closing it

from canto-curses.