Christian Mondrup writes:
|"Jeffrey B. Reed" wrote:
|I suppose the purpose of os.getpid() is to concatenate the current PID into a
|filename - but why ?
Too guarantee a unique name I guess.
|
|> replace ly2dvi.py with the enclosed file.
|
|I did so and got rid of the errors.
|
Very Good.
|> If you could help me check things out on 98
|> it would be appreciated.
|
|I would be honoured to do that :-) But ...
|
|I have some technical problems with the co-existence of MusiXTeX and it's
|pre-processors on one hand and lilypond on the other. Before I installed
|lilypond I have had the feta fonts installed into my MiKTeX localtexmf tree
|for quite a long time in order to reference the special mensuration time
|signatures in feta-timesig in some MusiXTeX macros. These feta metafont
|sources are 'frozen' with their last changes from the beginning of june. But
|after I had installed the full lilypond package it turned out that I got
|'unexpected' symbols in the angels.ly sample source which I get rid of only
|after having flushed my pre-existing feta tfm and pk files. But then I don't
|get my MusiXTeX output files right any more :-(
|
|When I look at the current set of feta symbols with the TeX testfont utility
|the special symbols created by Mats and me don't appear at all in the table
|for feta16 while they appear incomplete but with different sequence numbers
|(octal 137-151) in feta20. As created from my old feta sources these symbols
|have the octal numbers 174-203. The two versions of feta-timesig.mf are _not_
|different.
|
|As I expect MusiXTeX to be my primary typesetting platform for some time I
|have to get this conflict solved in order to keep both MusiXTeX and LilyPond
|fully functioning. Could you possibly give me some helping advice - or is
|this rather a question for Mats ?
Could you have the conflicting fonts in separate hierarchies and set
TEXFONTS appropriately for MusicTeX and lilypond. I wonder if Mats
has any other ideas?
|
|It seems that I have some trouble with yap and the angels.dvi file produced
|by ly2dvi. When I open the file with yap some of the beams and all the
|'lower' slurs don't print on the screen. And when I request yap to print on
|my attached printer (HP LaserJet 1100A) yap claims to have problems with some
|ps specials and after that prints the score with no beams and slurs at all.
|These problems are not with postscript files produced either by dvips or by
|adding the -P option to ly2dvi. Am I wrong in expecting yap to function as
|dvi previewer for LilyPond dvi files as I use to do with my MusiXTeX produced
|dvi files or do I have to use gsview ?
|
lilypond uses many postscript specials that dvi does _not_ support.
I have POSTSCRIPT=1 in my $HOME/_lilyrc file so that dvips is always
run. Then a preview with ghostview.
--
Jeffrey B. Reed
[EMAIL PROTECTED]
