Re: Metafont optional parameters

2020-05-30 Thread Werner LEMBERG
> I'd like to add an optional parameter for smuflcode to > fet_beginchar, so that I don't have to take two lines redeclaring > the variable in every glyph. Ideally, it won't have to be optional > once every character has it, but in the meantime, it would help with > testing individual characters

Re: GSoC 2020 update, May 30

2020-05-30 Thread Werner LEMBERG
> I started work on Han-Wen's suggested order of operations. In order > to make the .mf files output a SMuFL code to their log, I needed to > learn Metafont, which proved to be a language as little documented > as it is ingenious. [...] In case you have TeXLive installed, simply type texdoc

Re: Metafont optional parameters

2020-05-30 Thread Carl Sorensen
On Sat, May 30, 2020 at 4:41 PM Owen Lamb wrote: > > Hi all, > > I'd like to add an optional parameter for smuflcode to fet_beginchar, so > that I don't have to take two lines redeclaring the variable in every > glyph. Ideally, it won't have to be optional once every character has it, > but in the

Re: GSoC 2020 update, May 30

2020-05-30 Thread Carl Sorensen
On Sat, May 30, 2020 at 4:34 PM Owen Lamb wrote: > > Hi all. Sorry for the radio silence the past couple days. I got rather > overwhelmed trying to learn Metafont on my own, and the schedule I set up > for myself broke down rather quickly. I'll do my best to give my next > weekly report on time (i

Metafont optional parameters

2020-05-30 Thread Owen Lamb
Hi all, I'd like to add an optional parameter for smuflcode to fet_beginchar, so that I don't have to take two lines redeclaring the variable in every glyph. Ideally, it won't have to be optional once every character has it, but in the meantime, it would help with testing individual characters' ne

GSoC 2020 update, May 30

2020-05-30 Thread Owen Lamb
Hi all. Sorry for the radio silence the past couple days. I got rather overwhelmed trying to learn Metafont on my own, and the schedule I set up for myself broke down rather quickly. I'll do my best to give my next weekly report on time (i.e. on Friday). Since I gave an update earlier this week, I

Re: new procedure with GitLab CI

2020-05-30 Thread Jonas Hahnfeld
Am Freitag, den 29.05.2020, 22:47 +0200 schrieb David Kastrup: > So I lean towards the following process modeled upon our old one: > > No push to master except by automation. Staging is unprotected and gets > scheduled runners. People ultimately rebase and push there once they > get Patch-push s

Re: new procedure with GitLab CI

2020-05-30 Thread Jonas Hahnfeld
Am Freitag, den 29.05.2020, 19:22 +0200 schrieb Han-Wen Nienhuys: > On Fri, May 29, 2020 at 7:04 PM Valentin Villenave > wrote: > > On 5/27/20, Jonas Hahnfeld wrote: > > > No, "rebase" is currently manual (with "merge when pipeline succeeds" > > > being automatic). This has been clearly communic

Re: new procedure with GitLab CI

2020-05-30 Thread Jonas Hahnfeld
Hi Valentin, Am Freitag, den 29.05.2020, 19:03 +0200 schrieb Valentin Villenave: > On 5/27/20, Jonas Hahnfeld wrote: > > No, "rebase" is currently manual (with "merge when pipeline succeeds" > > being automatic). This has been clearly communicated, sorry if you > > missed that. > > Hey Jonas, he