Werner LEMBERG <[email protected]> writes: >> If this bug of TeXlive will persist into stable GNU/Linux >> distributions, it will likely have a devastating effect on >> LilyPond's reputation. It's not just the clef glyph that is >> prominently broken, but also a number of other frequent glyphs like >> the flags. > > Indeed. While I had reported the bug before releasing TexLive 2013, > IIRC, it was not possible to stop the release process (again). > > I sincerely hope that both Debian and Fedora are going to use the > *current* TeXLive version (from the SVN).
Well, the question is whether we can't do better than sincerely hoping. Can we prepare a report that a) prominently and clearly demonstrates that there is a _large_ problem b) prominently and clearly gives a working solution for fixing the problem c) get this out to all relevant parties in time. So far, I've been juggling with binaries to avoid the problem, but that's no working solution for a distribution, in particular not one compiled from source. Is there a clear picture somewhere about what causes the problem? And a reliable recipe for avoiding it? -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
