-
Notifications
You must be signed in to change notification settings - Fork 5
Home
Welcome to the Byzscribe wiki!
This project has been put on hold as I've been working on some other things. I do intend to return to it, but I think that the best way to proceed is to switch from font-based rendering, which is limiting us in terms of positioning, to vector-based rendering. As such, this project in its current form will probably not receive any additional updates.
Latest Feature: The auto hyphenator format has been changed in order to better facilitate some revisions to text positioning. A demonstration of the new format can be seen in How to Use.
Byzscribe Design Intentions This is a short summary of the intent behind Byzscribe.
Why Racket? Why use the Racket language?
See the issues page for a list of things that need to be done. That being said, here are the three highest priority issues:
-
Beginning programmers: Add all the neumes from the various included fonts. Test them to see if there are any orthographic errors. For now, don't define any special aliases besides the neume's name, as aliases will probably be removed. The format for neumes uses + for neume composition and - for neume variants. Please only define neumes that are in the included font files: don't create shortcuts for common compositions, as that is what the editor program will do.
-
People who understand fonts: Distribute the fonts in only a single format. Currently Windows needs the OpenType fonts, but the original TTF fonts work fine on Mac and Linux and actually render more clearly on those two platforms. Honestly, I don't yet know enough about fonts to figure this out.
-
Experienced programmers: While Byzscribe produces images suitable for viewing on a screen, they aren't adequate when printing. We need a way to render to a vector format like SVG or PDF. Please see this issue for some ideas.