OK. To debug this is beyond my capabilities, sorry. Hopefully, I
find time to dive into lilypond's Scheme details, but currently I
have no time to do that; right now I'm pretending to be Joe User.
No problem. I've done a bit more investigating, and I think I know
what's going on; I'll
Maybe the solution is to show the modification of nested-alist
properties *other* than spacing alists.
For example, fret-diagram-details is a nested alist. And TextSpanner
has bound-details as a nested alist. So is harp-pedal-details. And
Stem 'details.
There are probably more, as well.
Using a recent LilyPond Emmentaler font on the gnome canvas or
pangocairo drawing area, some characters fail to display, such
as accidentals.flat (charcode 57626 0xE11A) which is overridden
by a euro symbol.
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org
Freelance IT
On 11/2/10 2:09 AM, Jan Nieuwenhuizen jann...@gnu.org wrote:
Using a recent LilyPond Emmentaler font on the gnome canvas or
pangocairo drawing area, some characters fail to display, such
as accidentals.flat (charcode 57626 0xE11A) which is overridden
by a euro symbol.
Since we're playing in
On 2010/11/02 11:58:20, Carl wrote:
Maybe the solution is to show the modification of nested-alist
properties
*other* than spacing alists.
I like that idea.
Showing one or more of these in order to demonstrate the various
methods might
be more useful than using the spacing alists which
On 2010/11/02 11:58:20, Carl wrote:
Maybe the solution is to show the modification of
nested-alist properties *other* than spacing alists.
[...]
Showing one or more of these in order to demonstrate the
various methods might be more useful than using the
spacing alists which are set in a
On 2010/11/02 18:18:12, Mark Polesky wrote:
On 2010/11/02 11:58:20, Carl wrote:
Maybe the solution is to show the modification of
nested-alist properties *other* than spacing alists.
[...]
Showing one or more of these in order to demonstrate the
various methods might be more useful than
LGTM. One comment.
THanks,
Carl
http://codereview.appspot.com/2767043/diff/11001/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
Since we're playing in a non-coordinated area of the display space, how do
we ensure that we don't have this same problem show up again in six months
when somebody else has a special character they want to add so some font
(like the rewind icon at 0xE58D you mention in the patch)?
Indeed.
On 2010/11/01 18:35:14, Trevor Daniels wrote:
I'm happy with the changes to vocal.itely, although ragged-right could
also be
removed in many (maybe all) of the @lilyponds.
Aye, [ragged-right] should be removed from (almost?) all @lilypond. But
this patch is too big already.
Thanks, pushed.
(trying to make this as painless as possible...)
Renaming proposals, round 2:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
inter-staffnonstaff-staff
inter-loose-line nonstaff-nonstaff
On 11/2/10 2:56 PM, Mark Polesky markpole...@yahoo.com wrote:
(trying to make this as painless as possible...)
Renaming proposals, round 2:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
Hi Ian,
This patch still isn't working for me with Guile 1.9.13. Guile 1.8 is
fine.
I posted some inline comments for you below.
Unfortunately, I'm not sure what to suggest for a fix. Could this be a
bug in Guile 1.9 ?
Thanks,
Patrick
Mark Polesky wrote Tuesday, November 02, 2010 8:56 PM
Renaming proposals, round 2:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
inter-staffnonstaff-staff
I'd go with Carl's suggestion of
14 matches
Mail list logo
