Plugin displays <?> "Character not found" character in Avogadro2 menu entries in Windows 10

[Ineluki80]

Source: The menu entries "Configure ..." and "Get xtb ..." use the single unicode character "…"
Problem: Menues in Windows 10 show this character as "�"
Solution: Replace "…" with "..." three consecutive dots in config.py : 201 and install.py : 155

[matterhorn103]

This is done to match the other menu items in Avogadro, which have been standardized to use the ellipsis character rather than three full stops/periods. So I'll be keeping it as is.

Obviously the fact that it is displayed incorrectly is a problem that needs fixing, though.

I assume that other menu options with … display correctly for you?

In which case there is some problem in the way that Avogadro gets the options json from plugins. Presumably down to the character encoding used at various stages.

[Ineluki80]

Indeed, Avogadro's native menu items show correctly.
But I was able to fix the problem: Inserting the following code in config.py line 41 should do the trick.
sys.stdout.reconfigure(encoding='utf-8')

On Windows, all output to the console (as in print) seems to be automatically converted to CP1257.
See https://stackoverflow.com/questions/3597480/how-to-make-python-3-print-utf8

[matterhorn103]

Thanks for digging on this. Seems like it should be an easy fix.

It would be better to fix this on Avogadro's side of things though, as all plugins are going to be behaving the same on Windows.

[Ineluki80]

Are you going to open the forum thread or shall I do it ?

[matterhorn103]

I opened an issue but you're welcome to start the forum thread!

[ghutchis]

I mean, it's definitely a faster fix to tweak the script. Probably using fromLocal8Bit is needed to interpret the Python script results: https://doc.qt.io/qt-6/qstring.html#fromLocal8Bit

[matterhorn103]

True. I added the fix for now.

@Ineluki80 I would appreciate you testing the plugin again. Then I'll make a 0.2.1 release.

[Ineluki80]

Works beautifully now.