programming error message with bookparts and page-turn-breaking
Dear list,
When I use a lilypond file structured similarly to the following minimal
example, I get a programming error message thrown when compiling:
programming error: found a page-turnable place which was not breakable
The resulting file does look correct, with the bookparts seperated and
the other pages structured with the optimal turning algorithm. I was
just wondering if I was missing something to alleviate the error, as
usually when one of these pops up I realized it's due to a small error
in the file.
Thanks,
-Will
\version "2.24.0"
\paper {
page-breaking = #ly:page-turn-breaking
}
\book {
\bookpart {
\markup { title page here }
}
\bookpart {
\score {
\relative c' {
\repeat unfold 1024 c8
}
}
}
}
--
+ -- +
|William Rehwinkel - Oberlin College and |
| Conservatory '24 |
| will...@williamrehwinkel.net |
| PGP key: |
| https://williamrehwinkel.net/static/pubkey.txt |
+ -- +
OpenPGP_signature
Description: OpenPGP digital signature
Re: Programming error message
- Original Message - From: "Keith OHara" To: Sent: Monday, December 10, 2012 12:06 AM Subject: Re: Programming error message Eluze gmail.com> writes: Phil Burfitt wrote > programming error: cannot evaluate "head-separation-default" in module > I had previously been running 2.13.17 without any problems until I > decided > to update to 2.17.7 (first uninstalling 2.13.17) a few weeks back. This > is > when the errors appeared. I can't reproduce that (I have w7) - can you run this batch as a command-line-command and maybe add -V(verbose) and then copy the whole log!? I looked up "head-separation-default" in the code. It was formerly used in 'paper-defaults-init.ly' but had been unused for a while, then completely removed by version 2.13.40 Somehow, your simple scores are referring to variables from an old version of Lilypond. Maybe you have an old copy of 'paper-defaults-init.ly' in the directory holding your scores ? (If you have files with the same names as LilyPond's startup files, stored with your score, she will think you want to use your custom versions instead of the files that came with lilypond.) If that is the problem, probably adding -drelative-includes=#t to your batch file will solve it. (And tell us, however you do solve it.) Thank you to you and Eluze for your help Turns out the problem was caused by Windows Vista ownerships (and a pain that is). Although I am the only user on my computer, and with administrative privileges, I'm not the administator. When I was using 2.13.17 I made an entry in the paper-alist in paper.scm for a Kindle paper size. Uninstalling that version of lilypond didn't remove paper.scm (different ownership) and it remained invisible to all but a few text editors - which was how I discovered it. Installing a later version of lilypond produced two copies of paper.scm (with different ownerships) and every time I ran lilypond it would run the older version of paper.scm. Deleting the older copy of paper.scm solved the problem. Sorry for the noise. Regards, Phil. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
Eluze gmail.com> writes: > Phil Burfitt wrote > > > programming error: cannot evaluate "head-separation-default" in module > > I had previously been running 2.13.17 without any problems until I decided > > to update to 2.17.7 (first uninstalling 2.13.17) a few weeks back. This is > > when the errors appeared. > I can't reproduce that (I have w7) - can you run this batch as a > command-line-command and maybe add -V(verbose) and then copy the whole log!? > I looked up "head-separation-default" in the code. It was formerly used in 'paper-defaults-init.ly' but had been unused for a while, then completely removed by version 2.13.40 Somehow, your simple scores are referring to variables from an old version of Lilypond. Maybe you have an old copy of 'paper-defaults-init.ly' in the directory holding your scores ? (If you have files with the same names as LilyPond's startup files, stored with your score, she will think you want to use your custom versions instead of the files that came with lilypond.) If that is the problem, probably adding -drelative-includes=#t to your batch file will solve it. (And tell us, however you do solve it.) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
Phil Burfitt wrote
> \version "2.17.8"
> {
> c' d' e' f'
> }
>
> on Windows Vista
>
> I run the code by file drag and drop to a desktop shortcut to a .bat file
> which contains the following..
>
> lilypond -dno-strip-output-dir -dpaper-size=\"a4\" -fpdf %1
>
> I had previously been running 2.13.17 without any problems until I decided
> to update to 2.17.7 (first uninstalling 2.13.17) a few weeks back. This is
> when the errors appeared. I then uninstalled 2.17.7 and installed 2.16.
> but
> had the same problem. Today I have installed 2.17.8, but the problem
> persists. Despite these error messages, all files I have tried (with
> necessary convert.ly) have compiled successfully.
I can't reproduce that (I have w7) - can you run this batch as a
command-line-command and maybe add -V(verbose) and then copy the whole log!?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Programming-error-message-tp137384p137397.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
\version "2.17.8"
{
c' d' e' f'
}
on Windows Vista
I run the code by file drag and drop to a desktop shortcut to a .bat file
which contains the following..
lilypond -dno-strip-output-dir -dpaper-size=\"a4\" -fpdf %1
I had previously been running 2.13.17 without any problems until I decided
to update to 2.17.7 (first uninstalling 2.13.17) a few weeks back. This is
when the errors appeared. I then uninstalled 2.17.7 and installed 2.16. but
had the same problem. Today I have installed 2.17.8, but the problem
persists. Despite these error messages, all files I have tried (with
necessary convert.ly) have compiled successfully.
Phil.
- Original Message -
From: "Eluze"
To:
Sent: Sunday, December 09, 2012 4:47 PM
Subject: Re: Programming error message
Phil Burfitt wrote
I'm receiving the following error messages with versions 2.16, 2.17.7 and
2.17.8 for all scores, even a minimal score, although scores continue to
compile successfully...
Parsing...
programming error: cannot evaluate "head-separation-default" in module
"#
", setting to "0"
continuing, cross fingers
programming error: cannot evaluate "foot-separation-default" in module
"#
", setting to "0"
continuing, cross fingers
Any ideas?
can you state more precisely which code, which OS, how you installed
LilyPond, how you invoke LilyPond, … (here all these versions work as
expected!)
Eluze
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
Phil Burfitt wrote > I'm receiving the following error messages with versions 2.16, 2.17.7 and > 2.17.8 for all scores, even a minimal score, although scores continue to > compile successfully... > > Parsing... > programming error: cannot evaluate "head-separation-default" in module > "# > > ", setting to "0" > continuing, cross fingers > programming error: cannot evaluate "foot-separation-default" in module > "# > > ", setting to "0" > continuing, cross fingers > > > Any ideas? can you state more precisely which code, which OS, how you installed LilyPond, how you invoke LilyPond, … (here all these versions work as expected!) Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Programming-error-message-tp137384p137385.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Programming error message
I'm receiving the following error messages with versions 2.16, 2.17.7 and 2.17.8 for all scores, even a minimal score, although scores continue to compile successfully... Parsing... programming error: cannot evaluate "head-separation-default" in module "#", setting to "0" continuing, cross fingers programming error: cannot evaluate "foot-separation-default" in module "#", setting to "0" continuing, cross fingers Any ideas? Regards, Phil. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Sun, Feb 28, 2010 at 1:13 PM, Tim McNamara wrote: > > On Feb 28, 2010, at 12:54 PM, Patrick McCarty wrote: >> >> What if we output a message like this instead: >> >> warning: invalid UTF-8 string found at row 3, column 10 >> >> I think this would be easier to implement. > > From the relatively naive user perspective, this would be very helpful. > Since Emacs can be set to show the line the cursor is in, this would make > tracking down the cause of the problem much easier. Thanks for your feedback. This is a little more involved than I was anticipating, so I've added a tracker issue: http://code.google.com/p/lilypond/issues/detail?id=1023 -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Feb 28, 2010, at 12:54 PM, Patrick McCarty wrote: On 2010-02-28, Werner LEMBERG wrote: I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? Yes, thanks. I assume that it is not possible to add the offending text string to the warning message since a Pango warning is not visible to lilypond... Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. It would be very simple to check for invalid UTF-8, since we can use GLib's g_utf_validate() function. In fact, Pango uses this same function in pango_layout_set_text(). Unfortunately, it would be much more complicated (I think) to output the offending string, since we would have to convert an arbitrarily encoded string to UTF-8, and then display it along with the warning/error. And this assumes we are dealing with a UTF-8 locale. What if we output a message like this instead: warning: invalid UTF-8 string found at row 3, column 10 I think this would be easier to implement. From the relatively naive user perspective, this would be very helpful. Since Emacs can be set to show the line the cursor is in, this would make tracking down the cause of the problem much easier. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
> It would be very simple to check for invalid UTF-8, since we can use > GLib's g_utf_validate() function. In fact, Pango uses this same > function in pango_layout_set_text(). Good to know. > What if we output a message like this instead: > > warning: invalid UTF-8 string found at row 3, column 10 This is probably even better than outputting the problematic string. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On 2010-02-28, Werner LEMBERG wrote: > > > I neglected to mention that in recent 2.13 versions, the warning > > messages for invalid character encoding look like this: > > > > (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to > > pango_layout_set_text() > > > > These warnings are generated by Pango. > > > > Is this an improvement? > > Yes, thanks. I assume that it is not possible to add the offending > text string to the warning message since a Pango warning is not > visible to lilypond... Perhaps it makes sense to add a UTF-8 checker > to lilypond just for that. It would be very simple to check for invalid UTF-8, since we can use GLib's g_utf_validate() function. In fact, Pango uses this same function in pango_layout_set_text(). Unfortunately, it would be much more complicated (I think) to output the offending string, since we would have to convert an arbitrarily encoded string to UTF-8, and then display it along with the warning/error. And this assumes we are dealing with a UTF-8 locale. What if we output a message like this instead: warning: invalid UTF-8 string found at row 3, column 10 I think this would be easier to implement. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Feb 28, 2010, at 1:56 AM, Patrick McCarty wrote: On 2010-02-27, Werner LEMBERG wrote: I don't see any non-ASCII characters in my file. Oh, I take that back now that I scrutinize closer... I have © in the input file. Well, that's easy to get rid of. And doing so eliminates the glyph complaint from Lilypond. Wow, eight or so complaints from one character! Any chance to add to the warning message a few words like This error most likely happens if you are using the wrong input encoding. Are you using UTF-8 encoding for your input file? IMHO there are too many questions on this list w.r.t. this warning message. I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? I haven't used 2.13 yet but I think that would be an improvement. It's nice when the error warnings provide interpretable information to the end user; usually these are written to be understandable just by the developers. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Sun, Feb 28, 2010 at 09:36:34AM +0100, Werner LEMBERG wrote: > > Perhaps it makes sense to add a UTF-8 checker > to lilypond just for that. This would certainly cut down on the number of questions asking "how do I write an accented character?". OTOH, it might prompt confusion about how to save files in utf-8 in all sorts of editors, but this can be dealt with in the newbie documentation. I think such a checker would be a good idea. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
> I neglected to mention that in recent 2.13 versions, the warning > messages for invalid character encoding look like this: > > (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > > These warnings are generated by Pango. > > Is this an improvement? Yes, thanks. I assume that it is not possible to add the offending text string to the warning message since a Pango warning is not visible to lilypond... Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On 2010-02-27, Werner LEMBERG wrote: > > >> I don't see any non-ASCII characters in my file. Oh, I take that back now > >> that I scrutinize closer... I have © in the input file. Well, that's easy > >> to get rid of. And doing so eliminates the glyph complaint from Lilypond. > >> Wow, eight or so complaints from one character! > > Any chance to add to the warning message a few words like > > This error most likely happens if you are using the wrong input > encoding. Are you using UTF-8 encoding for your input file? > > IMHO there are too many questions on this list w.r.t. this warning > message. I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
>> I don't see any non-ASCII characters in my file. Oh, I take that back now >> that I scrutinize closer... I have © in the input file. Well, that's easy >> to get rid of. And doing so eliminates the glyph complaint from Lilypond. >> Wow, eight or so complaints from one character! Any chance to add to the warning message a few words like This error most likely happens if you are using the wrong input encoding. Are you using UTF-8 encoding for your input file? IMHO there are too many questions on this list w.r.t. this warning message. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Fri, Feb 26, 2010 at 8:50 PM, Tim McNamara wrote: > > On Feb 26, 2010, at 9:23 PM, Patrick McCarty wrote: > >> On Fri, Feb 26, 2010 at 4:16 PM, Tim McNamara >> wrote: >>> >>> On Feb 26, 2010, at 3:35 PM, Patrick McCarty wrote: Also, which LilyPond version are you using? I've been working on a lot of Pango/text issues lately, so some of the error messages have changed form in recent 2.13 versions. >>> >>> This was 2.12.2-1 on Mac OS X 10.4.11. I get Pango complaints all the >>> time >>> with Lilypond but they seem to have no effect whatsoever on the output. >> >> Well, I can't test anything on OS X 10.4, but whenever I test LilyPond >> with simple .ly files on OS X 10.5 or 10.6, I don't see any of the >> FT_Get_Glyph_Name warning messages. >> >> Not unless my test file contains non-ASCII characters and is not saved in >> UTF-8. > > I don't see any non-ASCII characters in my file. Oh, I take that back now > that I scrutinize closer... I have © in the input file. Well, that's easy > to get rid of. And doing so eliminates the glyph complaint from Lilypond. > Wow, eight or so complaints from one character! Yeah, Pango is very picky about the character encoding. > I still get: > > (process:1754): Pango-WARNING **: Error loading GDEF table 28333 > > (process:1754): Pango-WARNING **: Error loading GSUB table 28333 > > (process:1754): Pango-WARNING **: Error loading GPOS table 28333 > > But as I say I've never noticed any problem in the output. This looks a lot like the (closed) issue here: http://code.google.com/p/lilypond/issues/detail?id=752 I think these particular warnings were fixed after the recent update to Pango for the official LilyPond builds. 2.12.3 *might* contain these fixes, I'm not sure. But I'm pretty sure they are harmless, as you've observed. >> Have you looked over this documentation page? >> >> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Text-encoding > > It looks familiar so I must have skimmed it at one point. Unfortunately > there is so much documentation that it would take about a year to read it > all in detail. > > Thanks! You're welcome. By the way, you can still use the copyright symbol if you want, just as long as you save your files with UTF-8 encoding. I have used the copyright symbol in some of my past compositions, so it should work. -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Feb 26, 2010, at 9:23 PM, Patrick McCarty wrote: On Fri, Feb 26, 2010 at 4:16 PM, Tim McNamara wrote: On Feb 26, 2010, at 3:35 PM, Patrick McCarty wrote: Also, which LilyPond version are you using? I've been working on a lot of Pango/text issues lately, so some of the error messages have changed form in recent 2.13 versions. This was 2.12.2-1 on Mac OS X 10.4.11. I get Pango complaints all the time with Lilypond but they seem to have no effect whatsoever on the output. Well, I can't test anything on OS X 10.4, but whenever I test LilyPond with simple .ly files on OS X 10.5 or 10.6, I don't see any of the FT_Get_Glyph_Name warning messages. Not unless my test file contains non-ASCII characters and is not saved in UTF-8. I don't see any non-ASCII characters in my file. Oh, I take that back now that I scrutinize closer... I have © in the input file. Well, that's easy to get rid of. And doing so eliminates the glyph complaint from Lilypond. Wow, eight or so complaints from one character! I still get: (process:1754): Pango-WARNING **: Error loading GDEF table 28333 (process:1754): Pango-WARNING **: Error loading GSUB table 28333 (process:1754): Pango-WARNING **: Error loading GPOS table 28333 But as I say I've never noticed any problem in the output. If your file *is* saved in UTF-8, please post it to the list so I can inspect it. Since I edit my .ly files in Emacs and don't have it set to save in UTF-8, I assume the default is plain ASCII. I might have been getting these warnings for a while and just hadn't seen them as they are below the bottom of the buffer as it is displayed in Emacs. The strange thing to me is that you are not seeing any problems in the output. Have you looked over this documentation page? http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Text- encoding It looks familiar so I must have skimmed it at one point. Unfortunately there is so much documentation that it would take about a year to read it all in detail. Thanks! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Fri, Feb 26, 2010 at 4:16 PM, Tim McNamara wrote: > > On Feb 26, 2010, at 3:35 PM, Patrick McCarty wrote: >> >> Also, which LilyPond version are you using? I've been working on a >> lot of Pango/text issues lately, so some of the error messages have >> changed form in recent 2.13 versions. > > This was 2.12.2-1 on Mac OS X 10.4.11. I get Pango complaints all the time > with Lilypond but they seem to have no effect whatsoever on the output. Well, I can't test anything on OS X 10.4, but whenever I test LilyPond with simple .ly files on OS X 10.5 or 10.6, I don't see any of the FT_Get_Glyph_Name warning messages. Not unless my test file contains non-ASCII characters and is not saved in UTF-8. >> If your file *is* saved in UTF-8, please post it to the list so I can >> inspect it. > > Since I edit my .ly files in Emacs and don't have it set to save in UTF-8, I > assume the default is plain ASCII. I might have been getting these warnings > for a while and just hadn't seen them as they are below the bottom of the > buffer as it is displayed in Emacs. The strange thing to me is that you are not seeing any problems in the output. Have you looked over this documentation page? http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Text-encoding -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Feb 26, 2010, at 3:35 PM, Patrick McCarty wrote: On Fri, Feb 26, 2010 at 1:04 PM, Tim McNamara wrote: Here's the programming error I mentioned in my other post. It is repeated about seven or eight times: programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file /Applications/LilyPond.app/Contents/Resources/share/lilypond/ current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers The output seems to be unaffected and there is nothing missing from the printed score. Warnings like these often occur when a file is not saved in UTF-8. Also, which LilyPond version are you using? I've been working on a lot of Pango/text issues lately, so some of the error messages have changed form in recent 2.13 versions. This was 2.12.2-1 on Mac OS X 10.4.11. I get Pango complaints all the time with Lilypond but they seem to have no effect whatsoever on the output. If your file *is* saved in UTF-8, please post it to the list so I can inspect it. Since I edit my .ly files in Emacs and don't have it set to save in UTF-8, I assume the default is plain ASCII. I might have been getting these warnings for a while and just hadn't seen them as they are below the bottom of the buffer as it is displayed in Emacs. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "Programming error" message
On Fri, Feb 26, 2010 at 1:04 PM, Tim McNamara wrote: > Here's the programming error I mentioned in my other post. It is repeated > about seven or eight times: > > programming error: FT_Get_Glyph_Name () error: invalid argument > continuing, cross fingers > programming error: Glyph has no name, but font supports glyph naming. > Skipping glyph U+, file > /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf > continuing, cross fingers > > The output seems to be unaffected and there is nothing missing from the > printed score. Warnings like these often occur when a file is not saved in UTF-8. Also, which LilyPond version are you using? I've been working on a lot of Pango/text issues lately, so some of the error messages have changed form in recent 2.13 versions. If your file *is* saved in UTF-8, please post it to the list so I can inspect it. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
"Programming error" message
Here's the programming error I mentioned in my other post. It is repeated about seven or eight times: programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file /Applications/LilyPond.app/Contents/ Resources/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers The output seems to be unaffected and there is nothing missing from the printed score. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Harp Pedals - "programming error" message
On 20-Sep-05, at 1:37 AM, Mehmet Okonsar wrote:
When I insert such a long markup:
--
_\markup { \large \bold {C} \natural \bold {D} \flat \bold {E} \sharp
\bold
{F} \flat \bold {G} \natural \bold {A} \flat \bold {B} \sharp}
--
I got the following message (but the score compiles fine)
-
programming error: script direction not yet known
Please send a complete example. My guess it that you are trying to
define
foo=_\markup{}
when you should do
foo=\markup{}
...
c4_\foo
but without seeing the source file, I can't really tell.
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Harp Pedals - "programming error" message
When I insert such a long markup:
--
_\markup { \large \bold {C} \natural \bold {D} \flat \bold {E} \sharp \bold
{F} \flat \bold {G} \natural \bold {A} \flat \bold {B} \sharp}
--
I got the following message (but the score compiles fine)
-
programming error: script direction not yet known
-
what's that?
Best Regards,
Mehmet Okonsar, pianist-composer
www.okonsar.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
