Graham Percival wrote:
Brett Duncan wrote:
I don't have a ~/.fonts, but there is an XML doc: ~/.fonts.conf
I do have a ~/.fontconfig - a folder with some 28 files in it, and
there is also a ~/.fonts.cache-1
Two possible ideas:
- Try removing (or renaming) those files and running lilypond ag
Brett Duncan wrote:
I don't have a ~/.fonts, but there is an XML doc: ~/.fonts.conf
I do have a ~/.fontconfig - a folder with some 28 files in it, and there
is also a ~/.fonts.cache-1
Two possible ideas:
- Try removing (or renaming) those files and running lilypond again.
- create a ~/.font
Graham Percival wrote:
Brett Duncan wrote:
Mats Bengtsson wrote:
Have you checked if ps2pdf calls the Ghostscript version included
with the
LilyPond distribution or any other Ghostscript version on your machine
(I don't know any details on how the LilyPond installation looks on
a Mac)?
>
ps
Ed Catmur escreveu:
> On Tue, 2007-02-20 at 19:42 +1100, Brett Duncan wrote:
>> Mats Bengtsson wrote:
>>> I looked at the .ps file that Brett sent me, and couldn't notice
>>> anything strange
>>> there. The problems seems somehow to be related to the Verdana TrueType
>>> font that's used for the c
On Tue, 2007-02-20 at 19:42 +1100, Brett Duncan wrote:
> Mats Bengtsson wrote:
> > I looked at the .ps file that Brett sent me, and couldn't notice
> > anything strange
> > there. The problems seems somehow to be related to the Verdana TrueType
> > font that's used for the chord names, but I don't
Brett Duncan wrote:
Mats Bengtsson wrote:
Have you checked if ps2pdf calls the Ghostscript version included with
the
LilyPond distribution or any other Ghostscript version on your machine
(I don't know any details on how the LilyPond installation looks on a
Mac)?
>
ps2pdf is calling GPL Ghos
Mats Bengtsson wrote:
Brett Duncan wrote:
I am completely baffled by this problem. I've checked all the
instances of the Verdana font I can find on my laptop, and they all
check out okay. Maybe there's another instance of the font somewhere
I can't find. I thought maybe the wrong version of
Brett Duncan wrote:
I am completely baffled by this problem. I've checked all the
instances of the Verdana font I can find on my laptop, and they all
check out okay. Maybe there's another instance of the font somewhere I
can't find. I thought maybe the wrong version of GS was being
triggered
Mats Bengtsson wrote:
I looked at the .ps file that Brett sent me, and couldn't notice
anything strange
there. The problems seems somehow to be related to the Verdana TrueType
font that's used for the chord names, but I don't understand why your
Ghostscript
(which should be the one included in
I looked at the .ps file that Brett sent me, and couldn't notice
anything strange
there. The problems seems somehow to be related to the Verdana TrueType
font that's used for the chord names, but I don't understand why your
Ghostscript
(which should be the one included in the LilyPond distributi
Graham Percival wrote:
I don't know exactly what the deal is, but I've heard that lilypond
.ps files (perhaps only since 2.10?) use some features of postscript
that only very recent ghostscript versions can handle. The
ghostscript that's built into Preview is too old. That's why we
distribut
Brett Duncan wrote:
Graham Percival wrote:
If I specify Postscript for the output, the resulting PS file will
not open in Preview (nor for that matter in GraphicConverter, which
reports the file as corrupt). However, the PS file *will* open in
KGhostView and KPDF (both running in XDarwin) an
Graham Percival wrote:
Brett Duncan wrote:
A little more experimenting reveals a few more things - if I specify
PNG for the output instead of the default PDF, there are no errors
and the PNG image is fine.
That makes sense; it's ghostscript that's broken.
If I specify Postscript for the outp
Brett Duncan wrote:
A little more experimenting reveals a few more things - if I specify PNG
for the output instead of the default PDF, there are no errors and the
PNG image is fine.
That makes sense; it's ghostscript that's broken.
If I specify Postscript for the output, the resulting PS fil
Graham Percival wrote:
Brett Duncan wrote:
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Sorry, I can't duplicate on my machine -- which is also 2.11.18,
10.4.8... on a Macbook
Brett Duncan wrote:
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Sorry, I can't duplicate on my machine -- which is also 2.11.18,
10.4.8... on a Macbook instead of Macbook pro,
In making some changes to a file I had created with LP 2.8, it
unexpectedly broke under 2.10.14.
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Here's a small example of what doesn
17 matches
Mail list logo
