> First, I updated the .mf files' fet_beginchar functions to take a
> SMuFL name (or a SMuFL name and a SMuFL-style alternate name)
> instead of a codepoint, and made sure the python scripts knew how to
> deal with it.
>
> I then split smufl-map.scm into two files: name-conversion.scm,
> which m
Hi all!
The last couple weeks were pretty stressful, which I'm sure you'll be able
to tell from the list archive. However, in the past couple days I have been
able to make up for much of the time lost.
Last week, I made plans for changing LilyPond's internal treatment of
glyphs--namely, that SMuF
Hi all,
I'm currently trying to fix broken links in the documentation.
What is the correct way of supplying fixes for the translated documents?
Can they be fixed directly in master, or should I prepare MRs against
the 'translation' branch?
Cheers,
Michael
Hello,
Here is the current patch countdown list. The next countdown will be on
July 4th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!207 langdefs: remove unused double_punct_char_sep - Han-Wen Nienhuys
On Wed, Jul 1, 2020 at 2:03 PM Jean Abou Samra wrote:
> The Contributor's Guide (10.5.1) clearly states that "Python code should
> use PEP 8". So, I'd like to be sure everyone agrees on the following points
> which are part of applying this PEP:
to me it's a no-brainer to introduce automatic form
