When I try "ly2dvi -p" (for pdf), then look at the PS output (which ly2dvi
makes as an intermediate step), I get a score without noteheads, clefs,
etc. (the infamous font problem :)
When I do "ly2dvi -P" (for ps output only), my score is fine.
\score { \notes { c'4 } }
Here's the problem (I think):
#####(portion of stdout for ly2dvi -P; it works)
#####(the file was called "mao.ly")
Output written on mao.dvi (1 page, 4560 bytes).
Transcript written on mao.log.
Invoking `dvips -ta4 -omao.ps mao.dvi'
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
' TeX output 2002.08.19:0016' -> mao.ps
kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 feta20
mktexpk: Running mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input feta20
This is METAFONT, Version 2.7182 (Web2C 7.3.7)
-------------
######(portion of stdout for ly2dvi -p; it doesn't work)
Invoking `dvips -ta4 -Ppdf -G0 -u lilypond.map -omao.ps mao.dvi'
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
' TeX output 2002.08.19:0016' -> mao.ps
kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 --dpi 8000 feta20
mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode.
mktexpk: Can't guess mode for 8000 dpi devices.
mktexpk: Use a config file, or update me.
kpathsea: Appending font creation commands to missfont.log.
dvips: Font feta20 not found, using cmr10 instead.
dvips: Design size mismatch in font feta20
dvips: Checksum mismatch in font feta20
<tex.pro><alt-rule.pro><texc.pro><texps.pro><special.pro>. <cmr10.pfb>
<cmbx10.pfb>[1]
Invoking `ps2pdf mao.ps mao.pdf'
----------
For some reason ly2dvi wants to use 8000 dpi when producing a pdf, but it uses
600 dpi when producing a ps on its own. Shouldn't they both be 600 dpi?
(lilypond 1.5.74.uu1)
HTH,
- Graham
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
