Re: [Issue #3947] fixing \huge et al.

Hi James, >> 'Accepted'. Is that better? Or at least sufficient? > No. I only filter on 'Started' Okay. >> null > Needs to be 'New'. Okay. > You can always go in and change these fields yourself manually. Okay. Thanks for the help! Kieren. Kieren MacMillan,

Re: Using/requiring Cairo

Paul writes: > I can't speak to the technical questions, but I see the appeal of this > idea. Cairo looks like a mature, well-supported, and widely-used > library. One side effect is that most free software PDF viewers use Cairo for their rendering these days, so if we

Re: Using/requiring Cairo

Paul writes: > I can't speak to the technical questions, but I see the appeal of this > idea. Cairo looks like a mature, well-supported, and widely-used > library. > > https://en.wikipedia.org/wiki/Cairo_%28graphics%29 > > Interestingly, "Cairo uses hardware acceleration >

Micro release feature list

Awesome Devs, I'm wondering if there's a semi-convenient way to look through the 2.19.* micro releases to see which features were added at which point. Any suggestions for getting the info this way? It's not a critical thing, I'm just curious to see when things came to be. I'm certainly aware of

Re: Using/requiring Cairo

I can't speak to the technical questions, but I see the appeal of this idea. Cairo looks like a mature, well-supported, and widely-used library. https://en.wikipedia.org/wiki/Cairo_%28graphics%29 Interestingly, "Cairo uses hardware acceleration

segfault with 2.18.2 from Debian 9.0 testing

Hi all, in the german forum a user reported a segfault. If you understand german please read: https://lilypondforum.de/index.php/topic,70.0.html It's too much to refer here in all details. In short: He tried to compile horn.ly from

Re: Micro release feature list

Il giorno lun 26 giu 2017 alle 21:46, kieren_macmillan kieren_macmillan ha scritto: I look for "Fixed__2_19_x" in the issue tracker. Another way is entering the lilypond-git directory and then launch gitk (or similar GUI tools, like gitg), where you'll see the

Re: Micro release feature list

On Mon, Jun 26, 2017 at 1:52 PM, Federico Bruni-2 [via Lilypond] < ml+s1069038n204131...@n5.nabble.com> wrote: > Il giorno lun 26 giu 2017 alle 21:46, kieren_macmillan kieren_macmillan > <[hidden email] > > ha scritto: > > I look for "Fixed__2_19_x"

True Hand-engraved Dashed Slurs

Greetings, Devs! I have always wondered why dashed slurs look the way they do, especially when compared to the Barenreiter snippets found in the essay. The current dashes look better than they used to, but I still think they look a bit odd compared to the fairly uniform thickness of the

Re: Micro release feature list

Hi Abraham, I look for "Fixed__2_19_x" in the issue tracker. Hope that helps! Kieren. -- Original Message -- From: Abraham Lee Date: June 26, 2017 at 2:45 PM Awesome Devs, I'm wondering if there's a

Re: segfault with 2.18.2 from Debian 9.0 testing

Thomas Morley writes: > Hi all, > > in the german forum a user reported a segfault. > > If you understand german please read: > https://lilypondforum.de/index.php/topic,70.0.html > It's too much to refer here in all details. > > In short: > He tried to compile > horn.ly

Re: True Hand-engraved Dashed Slurs

Abraham Lee writes: > Greetings, Devs! > > I have always wondered why dashed slurs look the way they do, especially > when compared to the Barenreiter snippets found in the essay. The current > dashes look better than they used to, but I still think they look a bit

Re: True Hand-engraved Dashed Slurs

David Kastrup writes: > Abraham Lee writes: > >> Greetings, Devs! >> >> I have always wondered why dashed slurs look the way they do, especially >> when compared to the Barenreiter snippets found in the essay. The current >> dashes look better than they

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

Hello, Sorry, I come after the push. A. In order to give this nice and long-wanted (also by users other than me) feature some visibility, could it be documented in the Notation Reference as well (NR 1.8.3 Fonts)? So the users will not only be able to use it, but also know how it (finally)

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

On 26 June 2017 at 09:32, Xavier Scheuer wrote: > > Hello, > > Sorry, I come after the push. > > A. In order to give this nice and long-wanted (also by users other > than me) feature some visibility, could it be documented in the > Notation Reference as well (NR 1.8.3 Fonts)?

Re: [Issue #3947] fixing \huge et al.

On Sun, 25 Jun 2017 21:12:49 -0400 Kieren MacMillan wrote: > Hi James, > > > I am sure you know the process > > Actually, I *don't*. This will be my first patch. > > > make sure that there is a tracker issue > >