Quoting David Petrou <[EMAIL PROTECTED]>:
> > All the tests show normal results. Is your Lilypond still built
> > with without-kpathsea or did you clean and rebuild the full
> > installation?
>
> it was a clean rebuild using kpathsea.
Fine!
> > Try to add the flag -V to ly2dvi and see if it
>
> All the tests show normal results. Is your Lilypond still built
> with without-kpathsea or did you clean and rebuild the full
> installation?
it was a clean rebuild using kpathsea.
> Try to add the flag -V to ly2dvi and see if it
> provides us any more hints on what goes wrong.
nothing jumped
All the tests show normal results. Is your Lilypond still built
with without-kpathsea or did you clean and rebuild the full
installation? Try to add the flag -V to ly2dvi and see if it
provides us any more hints on what goes wrong.
Does ly2dvi -P give a correct PS file (it should give you
a file w
> Did you remember to run 'texhash' after the installation?
i didn't remember because i didn't read anywhere that i had to run
this. :) but, i just ran texhash and reran "ly2dvi -p" and i get the
same bad pdf.
> What do the folllowing commands return?
>
> kpsewhich --format='dvips config' lily
Did you remember to run 'texhash' after the installation?
What do the folllowing commands return?
kpsewhich --format='dvips config' lilypond.map
kpsewhich feta20.pfa
/Mats
Quoting David Petrou <[EMAIL PROTECTED]>:
> > I definitely recommend 1., building Lilypond without kpathsea is
> > askin
> I definitely recommend 1., building Lilypond without kpathsea is
> asking for problems.
well, i did that, and now my pdf output is completely mangled.
i installed tetex-devel which has kpathsea. (i had to force install
this rpm because my tetex installation was in a weird place that rpm
didn't
> so, i think my options are:
> 1. find out some way to get a complete kpathsea-dev for tetex 1.0 and
> redo the lily installation completely.
> 2. revert to my backup and figure out what files to copy from my build
> directory to it to have the pfa files in the right place.
> 3. revert to my backu
> You have to build or download the Type1 version of the fonts,
> since that's what ly2dvi -p uses avoid the fuzzy looking
> bitmapped fonts in the PDF files.
>
> Read
> http://mail.gnu.org/pipermail/lilypond-user/2002-October/003014.html
> for instructions on how to build and install the fonts
You have to build or download the Type1 version of the fonts,
since that's what ly2dvi -p uses avoid the fuzzy looking
bitmapped fonts in the PDF files.
Read
http://mail.gnu.org/pipermail/lilypond-user/2002-October/003014.html
for instructions on how to build and install the fonts. Han-Wen has
> Did you compile and install Lilypond yourself or did you
> install from an RPM, .dpkg or ...?
i compiled and installed lilypond myself.
> What Linux distribution do you use?
SuSE 8.0
> Do you get the correct fonts if you call ly2dvi with the flags -p or
> -P?
well, what i did originally do
Did you compile and install Lilypond yourself or did you
install from an RPM, .dpkg or ...? What Linux distribution
do you use? Do you get the correct fonts if you call ly2dvi
with the flags -p or -P?
/Mats
Quoting David Petrou <[EMAIL PROTECTED]>:
> On 1.6.6 on my Linux box, if i simply lo
On 1.6.6 on my Linux box, if i simply look at postscript or pdf output
from Lilypond i don't get noteheads and lots of other symbols. I need
to first run xdvi on the .dvi output, then the fonts are created.
Once created, I'm set and don't need to run xdvi again; unless of
course I try a different
12 matches
Mail list logo
