[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: broken clef glyph

From: James
Subject: Re: broken clef glyph
Date: Tue, 03 Sep 2013 11:42:26 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8


On 03/09/13 11:10, David Kastrup wrote:
Werner LEMBERG <address@hidden> 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 is there something we can do in terms of damage limitation (reputation and emails to address@hidden) such that the 'make files' or the binary, or whatever can detect the fact that we have a bad version of whatever it is that is causing this and display something?

My only comparison is for something like VLC that requires many third-party codecs so that when it fails to encode/decode something it will report the problem where 'XYZ is missing' and tell the user to to 'do something' (such like install a lib file or contact a third party but not complain to them).

I know this isn't a fix, but it might take some load off of address@hidden when/if it eventually becomes mainstream.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]