Re: [Lilypond-auto] Issue 1637 in lilypond: include newest version of Fontforge in Lilydev

[lilypond]

Updates:
        Labels: -Patch-new Patch-needs_work
        Blockedon: -lilypond:1964 lilypond:1964

Comment #9 on issue 1637 by address@hidden: include newest version  
of Fontforge in Lilydev
http://code.google.com/p/lilypond/issues/detail?id=1637

On second thought, I cannot reproduce the the bug in issue 1683 on my  
Fedora 17 x86_64 system, which has Fontforge 20110222 built without  
--enable-double, nor with buildin from source Fontforge 20120731, which  
enable double use by default, so unless some proof of evidence, requiring  
Fontforge >= 20110222 sounds fine from this issue and issue 1683, but we  
don't need to require Fontforge built with --enable-double or  
--enable-longdouble.