On Fri, Jun 10, 2011 at 07:05:34AM +, Keith OHara wrote:
Janek WarchoĊ lemniskata.bernoullego at gmail.com writes:
The change is almost certainly due to new beam collision algorithm.
I'm forwarding this message to the development team so that they will
know about this issue.
I'm not
On 6/11/11 1:56 AM, Mark Polesky markpole...@yahoo.com wrote:
Carl, I have a tiny tiny tiny nitpick:
In your latest commit (0475fb3) I think you should wrap
--enable-double in an @option block:
@option{--enable-double}
Without it, the two hyphens become an en-dash, and command-line
2.15.1 has fontforge 20110222. I'll upload 2.14.1 with the same
fontforge unless anybody screams in the next 24 hours.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 6/11/11 9:34 AM, Graham Percival gra...@percival-music.ca wrote:
2.15.1 has fontforge 20110222. I'll upload 2.14.1 with the same
fontforge unless anybody screams in the next 24 hours.
AFAICS, there's no problem with 20110222. I don't think you need to worry
about waiting.
Carl
On Sat, Jun 11, 2011 at 09:39:07AM -0600, Carl Sorensen wrote:
On 6/11/11 9:34 AM, Graham Percival gra...@percival-music.ca wrote:
2.15.1 has fontforge 20110222. I'll upload 2.14.1 with the same
fontforge unless anybody screams in the next 24 hours.
AFAICS, there's no problem with
On 6/11/11 9:42 AM, Graham Percival gra...@percival-music.ca wrote:
On Sat, Jun 11, 2011 at 09:39:07AM -0600, Carl Sorensen wrote:
On 6/11/11 9:34 AM, Graham Percival gra...@percival-music.ca wrote:
2.15.1 has fontforge 20110222. I'll upload 2.14.1 with the same
fontforge unless anybody
I'm saying this because Werner has been using 20110222 for a long
time, [...]
Actually, I'm using a more recent git version (from 2011-06-02);
however, this still identifies as 20110222. And as far as it is
related to the intersection problems, nothing has changed.
Werner
