Closed scottsilverlabs closed 10 years ago
Okay, I can do that. Although, how do you want to handle user generated fonts? (if we are supporting that)
Looks like the MANIFEST.in does not support symbolic links.. After doing some research it would involve quite the workaround to work seamlessly. Maybe we can have a defined dictionary of aliases or something similar instead?
Yeah. As simple (and very useable) fix could be to allow files (not directories) in the font directory of the form "foo.lnk", or some such. So in the code, given the user selected font_name="foo", you'd just:
So.. create a different implementation of symbolic links.. Would it be better to do it your way and have separate files for each symbolic link (although can't do .lnk because windows uses that for shortcut files) or should we have a single "aliases" file that the API that uses as a lookup table?
I implement .font files instead of .lnk
For the function text():