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

2017-06-25 Thread Marc Hohl
Hi Kieren, Am 25.06.2017 um 17:11 schrieb Kieren MacMillan: Hi, Another ten days has passed… I guess I don't understand how the Lilypond development process works. I keep hearing we need people to jump in and learn how to develop/improve Lilypond. I took the initiative, found an issue I

Re: GUB Ghostscript 9.21

2017-06-25 Thread Masamichi Hosoda
>> Phil Holmes: >> ... >>> /usr/bin/ld: cannot find -lfreetype >> ... >> ld cannot find libfreetype.so >> Do you have it installed ? >> Try this: >> $ locate libfreetype.so >> ... >> /usr/lib/i386-linux-gnu/libfreetype.so >> /usr/lib/i386-linux-gnu/libfreetype.so.6 >>

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

2017-06-25 Thread Kieren MacMillan
Hi, Another ten days has passed… I guess I don't understand how the Lilypond development process works. I keep hearing we need people to jump in and learn how to develop/improve Lilypond. I took the initiative, found an issue I thought I could tackle, and offered a solution that appears to

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

2017-06-25 Thread Kieren MacMillan
Hi Marc, Thanks for the quick response. > I think that no response means "yes, submit a patch" in this case. > If you checked your changes and did not find any negative effects, > then submitting a patch is the best way to go IMHO. Okay. > The guidance/mentoring is great in principle, but it

Re: GUB Ghostscript 9.21

2017-06-25 Thread Phil Holmes
When trying to build Gub today, I got the following error: invoking cd /home/gub/NewGub/gub/target/tools/build/ghostscript-9.21 && make CC=cc CCAUX=cc C_INCLUDE_PATH= CFLAGS= CPPFLAGS= GCFLAGS= LIBRARY_PATH= obj/aux/genconf obj/aux/echogs obj/aux/genarch obj/arch.h cc -O2

Re: GUB Ghostscript 9.21

2017-06-25 Thread karl
Phil Holmes: ... > /usr/bin/ld: cannot find -lfreetype ... ld cannot find libfreetype.so Do you have it installed ? Try this: $ locate libfreetype.so ... /usr/lib/i386-linux-gnu/libfreetype.so /usr/lib/i386-linux-gnu/libfreetype.so.6 /usr/lib/i386-linux-gnu/libfreetype.so.6.8.1 ... Regards,

Re: Using/requiring Cairo

2017-06-25 Thread David Kastrup
Han-Wen Nienhuys writes: > On Sat, Jun 24, 2017 at 5:54 PM, David Kastrup wrote: >> Han-Wen Nienhuys writes: >> >>> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: The first step would likely just involve

Re: Using/requiring Cairo

2017-06-25 Thread karl
David Kastrup: ... > I don't see myself able to deal with all potential icky graphics code in > LilyPond, and I don't see anybody else stepping up either. ... Just for the record, I'm interested in icky graphics code. Regards, /Karl Hammar

Re: Using/requiring Cairo

2017-06-25 Thread Han-Wen Nienhuys
On Sun, Jun 25, 2017 at 2:05 PM, David Kastrup wrote: >> I would be much more supportive if you could show some numbers where >> memory/CPU is used right now, and could show some data how much Cairo >> would improve on things. It's quite possible that you are right, but >> then it

PATCHES - Countdown for June 25th

2017-06-25 Thread James
Hello, Sorry for the delay between this and the previous countdown. I should be back on normal schedule now. Here is the current patch countdown list. The next countdown will be on June 28th. A quick synopsis of all patches currently in the review process can be found here:

Re: Using/requiring Cairo

2017-06-25 Thread David Kastrup
k...@aspodata.se writes: > David >> k...@aspodata.se writes: > My point was: >> > Though, my conclusion was that pdf is not better than ps regarding >> > postprocessing, and yes I know that pdf (depending on pdf version) has >> > some features that ps don't have. >> >> But nobody is talking

Re: Using/requiring Cairo

2017-06-25 Thread David Kastrup
Just responding to a minor point: Han-Wen Nienhuys writes: > I suppose that functions like > > https://www.cairographics.org/manual/cairo-Paths.html#cairo-path-extents > > would be a boon. > > I was tickled to reply to your mail, because it was full of complaints >

Re: Using/requiring Cairo

2017-06-25 Thread karl
David Kastrup: ... > Han-Wen Nienhuys writes: ... > > I would be much more supportive if you could show some numbers where > > memory/CPU is used right now, and could show some data how much Cairo > > would improve on things. It's quite possible that you are right, but > > then

Re: Using/requiring Cairo

2017-06-25 Thread karl
David > k...@aspodata.se writes: > > Werner: ... > >> > And my interest was in reading pdf's, so I can write programs to > >> > extract the info I want from pdf's. > >> > >> Have you tried `pdftk' to uncompress a PDF file? It's then almost as > >> readable as a plain PS file (see attachments). >

Re: Using/requiring Cairo

2017-06-25 Thread David Kastrup
k...@aspodata.se writes: > David Kastrup: > ... >> I don't see myself able to deal with all potential icky graphics code >> in LilyPond, and I don't see anybody else stepping up either. > ... > > Just for the record, I'm interested in icky graphics code. There is no shortage in LilyPond and I

Re: Using/requiring Cairo

2017-06-25 Thread Han-Wen Nienhuys
On Sat, Jun 24, 2017 at 5:54 PM, David Kastrup wrote: > Han-Wen Nienhuys writes: > >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >>> What does that mean? Mainly a viable migration strategy where we might >>> be able to drop catering

Re: GUB Ghostscript 9.21

2017-06-25 Thread Phil Holmes
- Original Message - From: To: Sent: Sunday, June 25, 2017 12:13 PM Subject: Re: GUB Ghostscript 9.21 Phil Holmes: ... /usr/bin/ld: cannot find -lfreetype ... ld cannot find libfreetype.so Do you have it installed ? Try this: $ locate

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

2017-06-25 Thread James
Kieren, On Sun, 25 Jun 2017 11:35:37 -0400 Kieren MacMillan wrote: > Hi Marc, > > Thanks for the quick response. > > > I think that no response means "yes, submit a patch" in this case. > > If you checked your changes and did not find any negative effects, > >

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

2017-06-25 Thread Kieren MacMillan
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 > AND that the tracker issue is marked as 'started' 'Accepted'. Is that better? Or at least