Benjamin W. Bohl
Benjamin W. Bohl
**Is your feature request related to a problem? Please describe.** In various projects using Edirom Online, there has always been a need to customise the exact query location within MEI...
A first draft for the easy ways of customising, e.g. via edition-specific CSS should be provided. And maybe some hints to advanced possibilities.
As pointed to in https://github.com/music-encoding/music-encoding/issues/602 @key.sig.mixed is no longer available in MEI v4. A way of encoding mixed key signatures should be provided in the guidelines.
It would be great if it was possible to use the loadlink() syntax as described in https://github.com/Edirom/Edirom-Online/wiki/Links-to-Edirom-Online-and-its-content in the target attributes of the navigatorDefinition in the edirom-edition XML, e.g., to...
- [ ] refer to them as customizations _not_ profiles - [ ] use names as defined in customization XMLs in branch: https://github.com/music-encoding/music-encoding/tree/customizationDocs
- [ ] only run on compiled ODDs ca mei-source / uncompiled ODD - [ ] unify naming of variables and parameters with build.xml - [ ] promote some variables...
- [ ] introduce naming conventions (properties, targets,…) - [ ] create macros or reusable targets - [ ] modularize for better overview - [ ] use antcontrib foreach to...
This way one could, e.g., build everything for the neumes customization
This PR fixes the issues raised by the pureOdd-precheck.