Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-21 Thread Patrick McCarty
On Thu, Jan 21, 2010 at 9:36 PM, Keaton Mowery wrote: > Patrick, > > Thank you for your help! Your intuition was correct: my Pango install > was broken. For anyone experiencing the same issues, the problem was > that fontconfig comes preinstalled on OSX, and installing my own > version broke Pango

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-21 Thread Keaton Mowery
Patrick, Thank you for your help! Your intuition was correct: my Pango install was broken. For anyone experiencing the same issues, the problem was that fontconfig comes preinstalled on OSX, and installing my own version broke Pango's font selection mechanisms. Using the preinstalled version in /u

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-21 Thread Patrick McCarty
On 2010-01-20, Keaton Mowery wrote: > Okay, I think I've tracked it down... Whew, autotools is a mess. > Anyways, here's the short story: > > python-config reports information about the local python install. > Lilypond's configure scripts already use python-config, but in a > slightly different ma

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-20 Thread Tim McNamara
Fonts are an issue with almost all Linux/Unix applications ported into OS X using the Aqua interface. OpenOffice.org doesn't use fonts correctly either (somewhat of a bigger issue in an office suite); NeoOffice corrects this by putting a Java container around OO.o at the cost of performanc

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-20 Thread Keaton Mowery
Okay, I think I've tracked it down... Whew, autotools is a mess. Anyways, here's the short story: python-config reports information about the local python install. Lilypond's configure scripts already use python-config, but in a slightly different manner than my original hack (which is now obsolet

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-19 Thread Patrick McCarty
On 2010-01-14, Keaton Mowery wrote: > Here's the ./configure output: > > http://pastebin.com/m3daee40b Hmm. I don't see anything wrong/unusual about this output. Also, your patch below doesn't affect later behavior, so your font issue is still unresolved. Can you compile LilyPond on different

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Keaton Mowery
Here's the ./configure output: http://pastebin.com/m3daee40b I did modify the configure script to use the python-config program on OSX, the patch is below. I'm fairly sure that this won't change later behavior. Keaton Mowery diff --git a/conf

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Patrick McCarty
On Thu, Jan 14, 2010 at 10:51 AM, Patrick McCarty wrote: > On Thu, Jan 14, 2010 at 10:33 AM, Keaton Mowery wrote: >> Wow, it looks like you were right! Here's the .ps: >> >> https://dl.dropbox.com/u/41619/bad-fonts.ps > > When I get a chance to look at scm/framework-ps.scm more in depth, > I'll t

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Patrick McCarty
On Thu, Jan 14, 2010 at 10:33 AM, Keaton Mowery wrote: > Wow, it looks like you were right! Here's the .ps: > > https://dl.dropbox.com/u/41619/bad-fonts.ps > > Can I force it to use the feta fonts somehow? Not that I know of. I looked at your log of `lilypond --verbose' again, and it appears tha

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Keaton Mowery
Wow, it looks like you were right! Here's the .ps: https://dl.dropbox.com/u/41619/bad-fonts.ps Can I force it to use the feta fonts somehow? Keaton On Thu, Jan 14, 2010 at 8:12 AM, Patrick McCarty wrote: > On 2010-01-14, Keaton Mowery wrote: >> Patrick, >> >> I appreciate the response. Unfortu

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Patrick McCarty
On 2010-01-14, Keaton Mowery wrote: > Patrick, > > I appreciate the response. Unfortunately, I already had to pass in the > --with-ncsd-dir flag in order for make install to work properly. I > hope I have the right font files, though: > > kmow...@morgul /usr/local/Cellar/ghostscript/8.70/share/gh

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-14 Thread Keaton Mowery
Patrick, I appreciate the response. Unfortunately, I already had to pass in the --with-ncsd-dir flag in order for make install to work properly. I hope I have the right font files, though: kmow...@morgul /usr/local/Cellar/ghostscript/8.70/share/ghostscript/fonts $ md5 c059016l.pfb c059036l.pfb c0

Re: LilyPond 2.13.10 (OSX) Font Issues

2010-01-13 Thread Patrick McCarty
On Wed, Jan 13, 2010 at 11:04 PM, Keaton Mowery wrote: > Hello, > > I'm trying to package LilyPond 2.13.10 for a source-based OS X x86 > package manager. It is currently building successfully and producing > output. However, some of the fonts are a bit off, particularly the > time signature. Here'

LilyPond 2.13.10 (OSX) Font Issues

2010-01-13 Thread Keaton Mowery
Hello, I'm trying to package LilyPond 2.13.10 for a source-based OS X x86 package manager. It is currently building successfully and producing output. However, some of the fonts are a bit off, particularly the time signature. Here's an example of what works and what doesn't: https://dl.dropbox.co