Open raphaelbastide opened 11 years ago
I'm not certain how much would be applicable if I've switched from FontForge to Glyphs.app.
This structure is not related to the software used at all. It is just a proposal for a standard. Of course it is compatible with Glyphs.app.
I meant, stuff like the JSON file. Is that something that works with fontforge, or is that for use elsewhere?
Definitely open to a better folder structure though. :D
FONTINFO.json is a file I wrote myself, it is not related to fontforge. It contains all the informations for a -maybe utopic- large independant database of typefaces. With this kind of identity informations, it can be easy to search and browse by license, similar fonts, authors… It ts the interface for the folder structure and can link to the download package, github repository etc… I also need feedback about this idea so feel free to critic and share your questions.
Oh! I understand now. Sounds like a good idea. BTW, Any specific reason you use .ufo for your source?
The Unified Font Object (UFO) is a cross-platform, cross-application, human readable, future proof format for storing font data.
I chose it because standards are powerful. If you work with Glyphs.app and me with Fontforge, we can share the source and contribute to the same project \o/
I like this. I think I should try switching the sources this weekend or next then.
Returning to this item: cleaned up directory and added a stable fork. I'll look into new directory structures soon. Just have other things to fix first.
My attempts to switch to UFO have been a failure so far, so I'm pushing that out for later.\
I am experimenting a folder structure for open source typefaces.
You can see it in action here: https://github.com/raphaelbastide/Avara
There is some some details such as a FONTINFO.json, a /documentation folder and a design-guide.txt you can be interested in. Let me know if you want me to apply this structure to your project.