Updates:
Blockedon: 1964
Comment #25 on issue 2146 by julien.r...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
(No comment was entered for this change.)
___
bug-
Comment #24 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
See comment 19.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gn
Comment #23 on issue 2146 by pkx1...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
..and lilydev..
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.or
Comment #22 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Sounds like the best option is to check the correct fonts are installed
during configur? It will also mean that the GUB build
Comment #21 on issue 2146 by julien.r...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
My ubuntu install has Cyrillic in the fonts provided by the gsfonts
package. Looks like it's a matter of installing or updating
Comment #20 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
This sounds reasonable. Since the URW fonts are GPLed, I don't see a
problem here.
__
Comment #19 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
I think a further action that's needed is to include "working" NCSB font
files with the LilyPond Ubuntu distro. AFAICS neither
Comment #18 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Ah, I haven't thought of this. You are right, this can happen. So we
perhaps have to scan the (possibly binary) fonts directly a
Comment #17 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
I think it finds the "wrong" ones - i.e. those delivered without the
Cyrillic fonts.
___
Comment #16 on issue 2146 by julien.r...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
The configure script looks for these files on your system. Does it not
complain when it does not find them?
Comment #15 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
I agree in principle. The problem I have is that, on my vanilla
lilypond-ubuntu installation - I don't appear to have the corr
Comment #14 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Ok, I've tested what you suggest, and now I know that you are right and
wrong at the same time :-)
Making the font unknown to pd
Comment #13 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
In the pdfTeX logfile notation.log, which is produced by texi2pdf, there is
no sign of any font substitution at all, AFAICS. H
Comment #12 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
On my box, the fonts *are* in /usr/share/ghostscript/fonts. However, this
is completely irrelevant, since we should set up someth
Comment #11 on issue 2146 by philehol...@gmail.com: 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 err
On Fri, Dec 30, 2011 at 06:22:19PM +, lilyp...@googlecode.com wrote:
>
> My personal opinion is that we should avoid the texinfo.cnf route
> (intended for system-wide, global configuration options). It's
> another file for no good reason. macros.itexi seems to be the right
> place. Other op
Comment #10 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
My personal opinion is that we should avoid the texinfo.cnf route (intended
for system-wide, global configuration options). It's
Comment #9 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
The texinfo docs say that if there is a texinfo.cnf, it's read when the
@setfilename command is executed. We don't currently ha
Comment #8 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Sorry, my mistake: There is the config file `texinfo.cnf' which could also
hold the necessary @tex block.
__
Comment #7 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Modifying texinfo.tex directly is a bad idea IMHO. Since there isn't a
configuration file for texinfo.tex, adding it to macros.ite
Comment #6 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
What I've written was a proof of concept only. In reality, you should do
the following:
1. Create a `lilypond.map.in' file conta
Comment #5 on issue 2146 by gra...@percival-music.ca: Error: Illegal entry
in bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
can't this be added to texinfo.tex ?
___
bug-lilypond mailing list
bug-lilypond@g
Comment #4 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
I can confirm that putting this at the top of notation.tely gets rid of
the "Illegal entry in bfrange" error messages when makin
Comment #3 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
On my GNU/Linux box, the attached file does the trick.
Attachments:
BFRangeTesttest.texi 502 bytes
_
Comment #2 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
This is a bug directly in pdftex; I've just reported the problem as
http://tug.org/pipermail/pdftex/2011-December/008788.html
In
Comment #1 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in
bfrange block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
Of course you mean texi2pdf...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Status: Accepted
Owner:
Labels: Type-Build
New issue 2146 by philehol...@gmail.com: Error: Illegal entry in bfrange
block in ToUnicode CMap
http://code.google.com/p/lilypond/issues/detail?id=2146
The error in the title occurs when trying to create LilyPond documentation
that contains a
27 matches
Mail list logo
