Re: GSoC 2020: backwards compatibility

[Carl Sorensen]

On Tue, Aug 25, 2020 at 11:19 AM Owen Lamb <owendlamb@gmail.com> wrote:

> Hi all!
>
> Daniel drew my attention to the fact that my work doesn't keep backwards
> compatibility with other fonts encoded in the LilyPond manner, such as
> Gonville. He made a good point--it's definitely worth it to continue
> supporting the old format until Emmentaler reaches a reasonable SMuFL or
> "extended SMuFL" state that we can officially recommend be used by other
> fonts.
>
> That said, it would be difficult for me to bring backwards compatibility
> back before Friday (or Monday, if it comes to that).
>
> Werner (and the community in general), is backwards compatibility important
> enough that I should try to take care of it before the deadline?
>

I think backwards compatibility is important enough that we should probably
have it before merging the code into master.  In my opinion, it would be
best if LilyPond would work with the 'old' Emmentaler (and hence any of the
older fonts as well).

I don't think it's necessary to do it before the deadline, as long as you
will commit to do it afterwards.

I believe you can successfully pass GSoC with a branch that is not yet
merged into master.  And as long as it's available on GitLab, we have it to
use.

But since I'm not your mentor, I don't complete your evaluation.

Thanks for all your hard work!

Carl