Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-29 Thread Werner LEMBERG
> Here's another stab at glyphnames.json.txt, given all this new information: > > glyphnames.json is a part of the Standard Music Font Layout > (SMuFL) specification, version 1.3. It was retrieved from > https://github.com/w3c/smufl on 29 Aug 2020, and is licensed under > the W3C Final

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-29 Thread Owen Lamb
On Sat, Aug 29, 2020 at 3:09 AM Werner LEMBERG wrote: > > > So, glyphnames.json.txt would look like this? > > > > glyphnames.json, created by Daniel Spreadbury, was retrieved from > > https://github.com/w3c/smufl on DD Mon . It is licensed under > > the W3C Community Contributor

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-29 Thread Werner LEMBERG
> So, glyphnames.json.txt would look like this? > > glyphnames.json, created by Daniel Spreadbury, was retrieved from > https://github.com/w3c/smufl on DD Mon . It is licensed under > the W3C Community Contributor License Agreement and the W3C Final > Specification Agreement. Looks

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-29 Thread Owen Lamb
On Mon, Aug 24, 2020 at 1:07 AM Werner LEMBERG wrote: > * Who has written the file `glyphnames.json`? It lacks a copyright > header. If this is a non-lilypond file copied verbatim, please add > a separate file (say, `glyphnames.json.txt`) that gives all the > details: author, origin,

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-24 Thread Werner LEMBERG
> I've reordered and rebased my code, and it is now up to date with > the current master. I've just published the new branch to GitLab as > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's only > nine commits now, instead of over a hundred, and they're ordered in > a way that's

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-24 Thread Werner LEMBERG
>> At the same time, I'll write docs for my work. I figure I'll make >> nine documentation commits, one for each code change commit. Hmm. Maybe I've misunderstood you. What's actually missing are documentation strings *within* the commits. For example, the commit Add smufl data to feta

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-24 Thread Urs Liska
Am Montag, den 24.08.2020, 09:06 +0200 schrieb Werner LEMBERG: > > I've reordered and rebased my code, and it is now up to date with > > the current master. I've just published the new branch to GitLab > as > > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's > only > > nine

Re: GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-24 Thread Werner LEMBERG
> I've reordered and rebased my code, and it is now up to date with > the current master. I've just published the new branch to GitLab as > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's only > nine commits now, instead of over a hundred, and they're ordered in > a way that's

GSoC 2020 update: (hopefully) final commits made; testing time

2020-08-24 Thread Owen Lamb
Hi all! First, an apology--I thought the project was due today, the 23rd, but it's actually due next week, on the 31st. Tomorrow is just the first day I can submit the project. Well, better to err on the side of caution! I'd like to finish things up at least three days before the Monday