On stacked neumes that act like ligatures (ison-apostrophos and stacked apostrophoi) lyrics are currently centered. This seems normal for Greek words/syllables, but in English we should consider having the lyric centered under the primary neume (which will be slightly to the left) and adding a connector (dash or underscore) after it.

If this renderer can be very fast, it can also be the basis of a browser-based WYSIWYG editor

master branch:

        <neumes>
            bare apos_apos
        </neumes>
        <neumes color="#cf232b">
            gorgUR
        </neumes>
        <neumes>
            olig
        </neumes>
        <lyrics>
            set _
        </lyrics>

bnml-restructure branch:

            <syllable>
                <lyric>set</lyric>
                <neume-group>
                    <neume>bare</neume>
                    <neume type="primary">apos</neume>
                </neume-group>
            </syllable>
            <syllable>
                <lyric>_</lyric>
                <neume-group>
                    <neume>apos</neume>
                    <neume type="chronos">gorgUR</neume>
                </neume-group>
            </syllable>
            <syllable>
                <lyric>_</lyric>
                <neume-group>
                    <neume>olig</neume>
                </neume-group>
            </syllable>

Currently the header and footer can only be set once. If it is set twice, Kassia uses the second set of header/footer for every page in the PDF.

This will make Kassia BNML files much more human-readable and human-writable, and will also provide the amount of abstraction necessary to be able to incorporate other people's fonts, which aren't structured the same way that Kassia's own fonts are.

PHASE 0: Starting point

• Finalize KA New Stathis so we have a stable starting point
  • Consider using "Byzantine Musical Symbols" Unicode block

PHASE 1: Implement the shorthand

• Create abstractneume class
• Replace the chars in neume_dict.py with the shorthand neume names
• Translation layer to convert shorthand abstract neumes into font's chars
  • Read a font's fontconfig.yaml file for char assignments
  • For every neume, replace it with its char counterpart and rebuild the neumes_list

PHASE 2: KA New Stathis-based char shorthand

• Translation layer to convert KA New Stathis chars to shorthand abstract neumes

PHASE 3: Proper syntax

• Translation layer to convert shorthand abstract neumes into proper abstract neumes
  • For everything in the shorthand form, translate to proper
  • For everything in proper, translate to proper+positioning info
• Translation layer from proper abstract to concrete (font chars)
  • Read fontconfig.yaml for char assignments
  • For every neume combination, substitute it with the chars specified in fontconfig (if the given combination is defined therein)
  • For every neume, replace it with the chars specified in fontconfig
  • Create a stacking engine to spatially-align combinations that weren't defined in fontconfig

Should have a global setting in defaults (top of bnml score) and then allow override at individual tag.

Sometimes Kassia makes a large space after a dropcap. This is hard to reproduce, but it seems to happen when a score only takes up one line. Perhaps it's related to line justification, which doesn't always happen when a score is only one line long.

From @ilizol:

Could be better to change
digorg -> gorg2
trigorg -> gorg3
?

Same with haple
dipl -> hapl2
trip -> hapl3
tetr -> hapl4
?

We do specify kentimata as ken2, and we discussed naming kentima as ken1, so the suggestion for hap1, hap2, hap3 would be consistent with ken2. On the other hand, diple, triple, etc. do have their own names in Byzantine Notation (they aren't really referred to as "2 haples" or "3 haples") and keeping with diple, triple, etc. would be more consistent with their names in the Unicode block. @barudaret might have to weight in on this.

Kassia currently separates neumes and syllables, so that the neumes can be a whole body of text and the syllables can also be a whole body of text, rather than either being broken into pieces and paired together with their corresponding symbols from the other camp.

@ilizol requested that kassia use a key:value pair, similar to the syntax of https://github.com/muraiki/byzscribe