[Zubersoft]

Well, that's not quite right. SVG files are just text files with drawing instructions. So a library has to be used to make sense of that and convert it into a rendered image. The library that is handling that determines how fonts are handled. Most of them provide a way for the application code to be a "font provider", so that when the SVG has the name of a font listed, it asks the application to provide the font for that name, otherwise it falls back to default behavior (which can be different on every platform and/or framework). I'm just not providing fonts for names that aren't recognized. I handle the most basic, standard fonts (serif, sans-serif, cursive and fantasy on Android, and monospace), but I'm not doing any font loading beyond that at the moment. The abc2svg library generates a svg file that contains font names like "text" and "music" which are not standard fonts. The "music" font is an embedded music font that has to be extracted from the base64 encoding (none of the Android, Windows or iOS SVG libraries even supported that, so I had to modify them to correctly handle embedded fonts), and "text" doesn't map to any standard font at all. So I handle "text" by using sans-serif. At the moment, I mapped sans-serif to a different font (Finale Maestro which is open source), but I'm going to go back to "Roboto" for that since it's a true sans-serif font, and I've just modified the Roboto font to insert sharp and flat symbols for those characters. 

Text File Settings don't apply to abc files, and if you have an abc segment in a ChordPro file, that doesn't change what font is used for the abc file or anything of that sort.

Mike