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
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: lilypond-user@gnu.org
Sent: Monday, December 10, 2012 12:06 AM
Subject: Re: Programming error message
Eluze eluzew at gmail.com writes:
Phil Burfitt wrote
programming error: cannot evaluate head-separation-default
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
#module 4483e90, setting to 0
continuing,
, … (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
convert.ly) have compiled successfully.
Phil.
- Original Message -
From: Eluze elu...@gmail.com
To: lilypond-user@gnu.org
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
.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
Eluze eluzew at 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
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,
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
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
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
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
On Sun, Feb 28, 2010 at 1:13 PM, Tim McNamara tim...@bitstream.net 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
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
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
On Fri, Feb 26, 2010 at 1:04 PM, Tim McNamara tim...@bitstream.net 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
On Feb 26, 2010, at 3:35 PM, Patrick McCarty wrote:
On Fri, Feb 26, 2010 at 1:04 PM, Tim McNamara
tim...@bitstream.net 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
On Fri, Feb 26, 2010 at 4:16 PM, Tim McNamara tim...@bitstream.net 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
On Feb 26, 2010, at 9:23 PM, Patrick McCarty wrote:
On Fri, Feb 26, 2010 at 4:16 PM, Tim McNamara
tim...@bitstream.net 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
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
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
21 matches
Mail list logo
