12-02-2023, 02:24 PM
I posted in another thread about this, but when I tried to replace # and b with the unicode equivalents, the spacing between characters got really messed up. With the Android default font (Roboto) it created a gap between the chords and the sharp/flat characters that was unacceptable. Based on the screenshots above, it sure looks to me like the chord pro specification is using an entirely different font in each case - not just substituting the ascii characters with the unicode equivalents. For users that want the accidentals rendered in a nicer way, I need to add support for more fonts (including custom fonts).
Mike
Mike