Mats Bengtsson wrote:
Hi,
I just tried the 2.9.15-1 package in Windows and now an old favourite
bug has reappeared. When you run LilyPond from the command prompt, it
works the same as when you double-click on a .ly file, namely that
no printouts appear on stdout/stderr and that an extra
Hi,
how does
\char #integer
work? (See chapter 8.1.6 of the LilyPond Guide.) Whenever I use something like
copyright = \markup { \char #169 }
or
copyright = \markup \char #169
the corresponding *.ly file does not compile, although the logfile does
Ben Hoefer wrote:
Hi,
how does
\char #integer
work? (See chapter 8.1.6 of the LilyPond Guide.) Whenever I use something like
copyright = \markup { \char #169 }
or
copyright = \markup \char #169
the corresponding *.ly file does not compile, although
Quoting Han-Wen Nienhuys [EMAIL PROTECTED]:
Mats Bengtsson wrote:
Hi,
I just tried the 2.9.15-1 package in Windows and now an old favourite
bug has reappeared. When you run LilyPond from the command prompt,
it works the same as when you double-click on a .ly file, namely that
no printouts
Quoting Han-Wen Nienhuys [EMAIL PROTECTED]:
Mats Bengtsson wrote:
- Unless you include dos versions of ps2pdf, the font paths in
.psfonts (when fs-font-load=#t) should use windows style separators.
Of course, you could claim that users of lilypond-book should use
cygwin, but in my opinion,
Mats Bengtsson wrote:
Quoting Han-Wen Nienhuys [EMAIL PROTECTED]:
Mats Bengtsson wrote:
- Unless you include dos versions of ps2pdf, the font paths in
.psfonts (when fs-font-load=#t) should use windows style separators.
Of course, you could claim that users of lilypond-book should use
