[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking c
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem |
Date: |
Tue, 20 May 2014 12:58:30 +0000 |
Comment #23 on issue 3778 by address@hidden: SVG backend: tempo marking
collides with stem
http://code.google.com/p/lilypond/issues/detail?id=3778
A grep for "backend" leads to the following in lily/pango-font.cc
(Pango_font::text-stencil):
bool to_paths = music_strings_to_paths;
/*
Backends with the utf-8-string expression use it when
1) the -dmusic-strings-to-paths option is set
and `str' is not a music string, or
2) the -dmusic-strings-to-paths option is not set.
*/
if (has_utf8_string && ((to_paths && !music_string) || !to_paths))
{
// For Pango based backends, we take a shortcut.
SCM exp = scm_list_3 (ly_symbol2scm ("utf-8-string"),
ly_string2scm (description_string ()),
ly_string2scm (str));
Box b (Interval (0, 0), Interval (0, 0));
b.unite (dest.extent_box ());
return Stencil (b, exp);
}
return dest;
Could this be related?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, (continued)
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem,
lilypond <=
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/23