Almost 100% of fonts come wrapped in some way (binary zip, gzip, archive, executable, behind ten acknowledgement and/or pay clicks, etc. ) and have several types OTF, TTF, etc. All permutations of possibilities would be impossible to code. Most OS's deal with the screen themselves, so unless a front end is going to deal with the font as shapes, the system has to be made aware of the font before it is useful to the front end.
Success will be much more likely if Crosswire starts hosting quality opensource fonts that are able to display troublesome scripts (non UTF8 Vietnamese for example). That is, only allow URLs local to a repository in some standardized way.
________________________________ From: David Haslam <dfhmch@goog...> Subject: [sword-devel] FontURL as a suggested .conf property
It might be useful to also have a configuration file property called FontURL, such that the user does not need to resort to search engines to go and find the specified font.
Front-end developers might then make use of this property, by making it a hotlink when module information is displayed. It would then be just a single click away.
The suggestion may require further elaboration (e.g. to cope with different operating system requirements).