bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToU


From: lilypond
Subject: Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Date: Sun, 22 Jan 2012 16:26:23 +0000


Comment #11 on issue 2146 by address@hidden: Error: Illegal entry in bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146

OK - been doing some work on this with Julien, and here's what I've found. Using a patch Julien kindly prepared led to the error not being fixed. The problem appeared to be that Werner's test fix above uses /usr/share/ghostscript/fonts/ as the path to the directory, whereas NCSB_DIR resolves to /usr/share/fonts/type1/gsfonts/ (which is where the fonts actually are) - there's no trace of the other path on my system. After a fair amount of checking, I've concluded that the way Werner's fix actually worked was that it was pointing to a non-existent file - do this and the error disappears. In other words, putting this:

    \pdfmapline{=pncr8r CenturySchL-Roma </nodir/c059013l.pfb}%

at the top of notation.tely causes notation to compile with no bfrange errors (there are normally 88) and with properly displayed Cyrillic text. So it appears that all that's necessary is to create font mappings to a font file in a non-existent directory. Hmm. I'm a bit loathe to do this without someone else confirming that this would be an acceptable solution.




reply via email to

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