For supporting fonts, we probably want to express them as Font Name + Font Size (and maybe bold, italic, ..., not entirely sure). That should be the most portable representation. I don't think livesplit-core itself needs to be able to provide a list of all the fonts available. I think the UI can do that. For the browser we probably want to just provide a list of common fonts and allow providing a custom font name, as there doesn't seem to be any API (other than a hack through flash) to actually query all of the system's fonts. In the desktop versions we can use some native APIs to query them. So actually, maybe it does make sense to do that in livesplit-core, in a livesplit-font library or something.