Re: [PATCH] no-outline-stencil backend property

Knut Petersen writes: > Am 24.01.2017 um 14:49 schrieb David Kastrup: >> What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended

Re: [PATCH] no-outline-stencil backend property

Knut Petersen writes: > Am 24.01.2017 um 14:49 schrieb David Kastrup: >> What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended

Re: [PATCH] no-outline-stencil backend property

Knut Petersen writes: > Am 24.01.2017 um 14:49 schrieb David Kastrup: >> What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended

Re: [PATCH] no-outline-stencil backend property

Am 24.01.2017 um 14:49 schrieb David Kastrup: What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended to bypass outlining. Probably by just containing _two_ stencils:

Re: [PATCH] no-outline-stencil backend property

Knut Petersen writes: > Hi David! > >> What a steaming heap of something. So your code would likely have >> worked in LilyPond 2.16. I think it would make sense to create a new >> type of stencil expression explicitly intended to bypass >> outlining. Probably by just

[PATCH] no-outline-stencil backend property

Hi David! What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended to bypass outlining. Probably by just containing _two_ stencils: one for typesetting, one for outlining.