No error for me on OSX 10.6 with various recent lilyponds.  FWIW, here
is my standard copyright header, which searches the include paths for
the eps file:

\version "2.19.16"

copyrightDate = #(strftime "%Y" (localtime (current-time)))
copyright = \markup \center-column {
                    \vspace #4
                    \teeny 
                    {"This edition is licensed under a Creative Commons
Attribution-ShareAlike 4.0 International Licence." }
                    \raise #1.0 \concat {
                        \teeny {"© " \copyrightDate " myname <myemail>
" }
                        \general-align #Y #CENTER {
                            \epsfile #X #10 #(ly:find-file
"creativecommons_by-sa.eps")
                        }
                        \teeny {"
http://creativecommons.org/licenses/by-sa/4.0/"}}}


On Fri, 2015-08-07 at 07:31 +0200, Jacques Menu wrote:

> Hello Kyle,
> 
> No error for me on OS X 10.4.4 with LP 2.19.22.
> 
> JM
> 
> > Le 7 août 2015 à 02:04, Kyle Shaw <kylebs...@gmail.com> a écrit :
> > 
> > Hi all:
> > 
> > It appears that \epsfile works on Windows but not on Mac. 
> > 
> > 
> > Compiling:
> > 
> > \version "2.18.2"
> > 
> > \markup \epsfile #X #20 #"logo.eps"
> > 
> > ... results in:
> > 
> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 
> > -dDEVICEHEIGHTPOINTS=841.89 -
> > dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -
> > sOutputFile=./document.pdf -c.setpdfwrite -fdocument.ps)' failed (256)
> > 
> > fatal error: failed files: "/var/folders/gv/z8_2c5sn5gb2jqnv0yxqch7h0000gn/
> > T/frescobaldi-
> > c959yf/tmp5uZHGR/document.ly"
> > 
> > I've already seen this bug report from one of the LP 2.15 incarnations:
> > 
> > https://code.google.com/p/lilypond/issues/detail?
> > id=2772&q=%5Cepsfile&colspec=ID%20Type%20Status
> > %20Stars%20Owner%20Patch%20Needs%20Summary
> > 
> > Stepping through that process doesn't seem to work for me either. 
> > 
> > Anyone found a work around for \epsfile on Mac OSX since LP 2.15? 
> > Does any one know of any 
> > changes made to LP since 2.15 that may have corrected the aforementioned 
> > bug?
> > 
> > Thanks in advance
> > 
> > 
> > _______________________________________________
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to