Does not support the aardwolf UTF-8 extended ascii map

[blockda]

So close.
Must set options->system encoding->UTF8
on aardwolf: maptype <anything but 0>

result with side by side by running tags on/off and maptype toggling; running the aardwolf scripts for the map miniwindow.

I think it is the default font not actually monospacing those characters. Its... off..

[fiendish]

Oh wow. Look at those corners. That's worse than just not monospacing.

[blockda]

It's not, not monospacing them? Whatever is happening, its bad. If I'm not wrong, android amalgamates fonts for you, so you say, draw with this font, and if it doesn't have a glyph it will fall back to other fonts installed on the system instead of drawing a blank box. So what is above here may be a mix of monospaced font.

Attached here is what DejaVuSansMono.ttf looks like, appears to be working fine.

The map miniwindow plugin does nothing to change the selected font so it defaults to the system monospace font. I think I can get that script alone to pull in the main window font option (so the one that is accessible) or I can make it a front facing option editable from the options menu. Maybe both?

[fiendish]

android amalgamates fonts for you, so you say, draw with this font, and if it doesn't have a glyph it will fall back to other fonts

Oh, brutal. That behavior totally makes sense for (probably) most applications. For whatever it's worth, in MUSHclient I check to see if the chosen font can display the desired characters and then print a warning message if it can't. It catches incompatible fonts at least, but it doesn't fix bad font metrics. A lot of fonts still look terrible because something prints with slightly the wrong width.