Update Manuscript generation to work with sibmei

[th-we]

To avoid the need of conflict resolution with merging commits one by one, this pull request supersedes #111, #112, #116 and #117.

This includes changes that were made to the libmei shipping with sibmei. For example, the RemoveChild() method was added with 24f5b43 in 2015, but was never added to the libmei generator.

Goal is that we can generate libmei for sibmei without having to manually merge changes every time.

[ahankinson]

as far as I remember, the libmei. prefix was used to ensure that there weren't any collisions with other libraries, since the method names are fairly generic.

Not sure why the Chr(10) line feed character is being added...

[ahankinson]

Ah, I see -- the \ns are hidden from the GitHub diff...

[th-we]

Can you explain how removing prefixes might cause collisions? The reason to remove them was actually to avoid collisions with other versions of libmei. Sibelius binds the prefix to the file name of the plugin. If we rename the libmei.plg file, then libmei will break, or all the prefixes have to be changed as well. We actually renamed libmei.plg to libmei4.plg in Sibmei to prepare for a MEI 4 release, opening up the possibility to use the MEI 3 version in parallel with a different version of libmei.

Without a prefix, only methods from the same .plg file are used. Or are the concerns about collisions with global ManuScript methods?

[th-we]

I realize that I accidentally applied the "Update dead weblink" commit twice (and reverted it once) while combining the separate pull requests. I can rebase to fix this if necessary.

[ahankinson]

Wouldn't you want to change this line, then, if you've renamed the plugin?

https://github.com/DDMAL/libmei/blob/master/tools/langs/manuscript.py#L883

[ahankinson]

Also, you should add yourself to the AUTHORS.

[th-we]

Wouldn't you want to change this line, then, if you've renamed the plugin?

https://github.com/DDMAL/libmei/blob/master/tools/langs/manuscript.py#L883

As I understand it, the libmei generation should be usable for any version or customization. I would therefore not change the default output name. When used, it can be renamed to anything that is appropriate.

[ahankinson]

I don't understand. So you're wanting to have two different libmei plugins installed (one for v3, one for v4), and you want to generate the libmei code for v4, but you don't want to change the plugin name?

[th-we]

I can use the libmei generator to create a libmei for basically any MEI schema, be it v3, v4 or any customization I like, right? Therefore the default name libmei4.plg would not be generally fitting. The output file can be renamed manually to whatever is suitable for the use case. (The only use case right now of course being to bundle it with a specific version of sibmei.)

ef2ca39 makes sure that libmei will work no matter what its file name is.

[th-we]

As there were some changes in the meanwhile, I'd like to close this pull request and continue on a few separate ones.

#124 #125 #126