SOLUTION: 2.4.5 failure with Slackware-current (teTeX 3.0, espgs-8.15rc2)

In an earlier post, I noted that 2.4.5 would not run with Slackware-current. The problem is in the install of the lilypond-2.4.5/tex directory. In the makefile, gs is called like so: echo 'ISOLatin1Encoding pstack' \ | gs -sDEVICE=nullpage -quiet - \ | sed 's|/minus|/

2.4.5 failure with Slackware-current

Hi: I've just compiled lilypond 2.4.5 under Slackware current -- this is Slackware 10.1 with tetex-3.0 and espgs-8.15-rc2. When I run lilypond on any simple file: GNU LilyPond 2.4.5 Processing `rnjig.ly' Parsing... Interpreting music... [8][16][24] Preprocessing graphical objects... Calculating

Re: Problem building 2.5.9 web docs

Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: Did that. Now it's giving me "/invalidfont in findfont". I've got the latest ec-fonts installed, and just in case, I remade all of lilypond. Where to go from here? Read up on ghostscript font inst

Re: Problem building 2.5.9 web docs

Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: I built 2.5.9 according to instructions -- when I try to build the webdocs, lilypond hangs when building les-neriedes.ly. When I try to compile the same file manually, it hangs at the ps2pdf step. upgrade to ghostscript 8.x Did that. Now it's givi

Problem building 2.5.9 web docs

Hi: I apologize if this has been covered; I've had no luck finding it in the archives. I built 2.5.9 according to instructions -- when I try to build the webdocs, lilypond hangs when building les-neriedes.ly. When I try to compile the same file manually, it hangs at the ps2pdf step. Not sure w

Old text/font bug resurfaces

Hello: The lilypond source at the end of this message demonstrates a bug that was gone, but seems to have resurfaced in 2.2.1. Basically a pdf font bug, it's described in the tagline. Thanks, Doug \version "2.2.0" \header { texidoc = "Only a melody." tagline = "If I get rid of one of the

set makeprg error in /vim/compiler/lilypond.vim

Hi: In the lilypond.vim file under /usr/local/share/lilypond/2.2.0/vim/compiler, there's this line: set makeprg=lilypond $* it should (at least with vim 6.2.x) be: set makeprg=lilypond\ $* Small difference, but it won't work otherwise. Thanks, Doug _

2.1.34: Instrument name in header messes w/justification

Possible bug: if you specify the instrument name in the \header block, it can throw off the justification of the music. Setting raggedright to ##f doesn't fix this; and the problem is stranger than that. - Doug \version "2.1.34" \header { title = "Suite No. 3" composer = "J.S. Bach" inst

convert-ly problem

Hi: I'm seeing the following in most cases with convert-ly (note: all of these cases worked find with 2.1.32): convert-ly (GNU LilyPond) 2.1.34 Processing `popsong.ly' ... Applying conversions: 2.1.23, 2.1.24, 2.1.25, 2.1.26, 2.1.27, 2.1.28, 2.1.29, 2.1.30, 2.1.31, 2.1.33, Traceback (most rece

Odd artifact using 2.1.32

Getting an odd artifact with this score (see below) using 2.1.32. A small vertical line gets drawn under the score. If I only override TextScript #'padding once, there is no problem. If I only use one of the markup tags, no problem. See the tagline in the score for more info. It's possible I'm

minor typo in INSTALL.txt

In the Vim mode section, the filetype directives that read: augroup filetypedetect au! BufRead,BufNewFile *.ly setfiletype lilypond augroup should read: augroup filetypedetect au! BufRead,BufNewFile *.ly setfiletype lilypond augroup END Minor, but somewhat anno