> Remember: We used the hardcoded name "Emmentaler" at various places > for --bigpdfs, and --use-encodings still needs and uses that portion > of the old code.
Before remembering something, I need to know it in the first place. Sounds like something we should get rid off in the long run.
Yes. I never used an alternative music font, and I don't have the details how the Authors implement them. This morning I wrote to Abraham Lee.
Nevertheless, for 2.21+ I would want to move to a different default, so it makes sense to bikeshed the naming of the option(s) such that we only need to flip the default at some point of time. Scripts should already be able to explicitly decide which side of the default they want to end up with (and will then do so regardless of whether the default has been flipped).
Regarding the naming of the option, I'd prefer to have something oriented around the actual use characteristics rather than the internal details.
Does that sound like something you can agree with?
Yes. That sounds reasonable. If you know a better name for the option I'd happy to start sed.
> - Someone probably will propose to add ghostscript as a git > submodule to the lilypond tree and to add some patches.
I doubt we could reasonably afford the ongoing cost of even a small fork. So as long as we can coordinate efforts with upstream, that seems vastly preferable.
We'll talk about that in some months ;-) https://codereview.appspot.com/325630043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
