Re: native LilyPond port for Microsoft Windows

[Schneelocke]

Hi Jan,

> If you look in the .ps with a text editor, you'll see that fonts are
> loaded by a command that looks like
> 
>     %%BeginFont: PFAEmmentaler-20
>     (c:/Program 
> Files/LilyPond/usr/share/lilypond/2.5.25/fonts/type1//PFAemmentaler-20.pfa) 
> (r) file .loadfont
>     %%EndFont
> 
> The font that has the problem, has
> 
>    (#f) (r) file .loadfont

OK, here's the relevant part (from xiao-haizi-guai-guai.ps):

--- CUT HERE ---
%%BeginFont: PFAAybabtu-Regular
(#f) (r) file .loadfont 
%%EndFont

%%BeginFont: PFAPFAEmmentaler-23
(#f) (r) file .loadfont 
%%EndFont
--- CUT HERE ---

Other files (like simple.ps) fail to load the PFAAybabtu-Regular font,
at least; the font files are there, though
(share/lilypond/2.5.25/fonts/type1/PFAaybabtu.pfa and
.../PFAemmentaler-23.pfa, respectively). What's noteworthy is that the
BeginFont directives seem to refer to these fonts with an extra PFA
prefix - something that's not the case for PFAEmmentaler-20 (which has
a valid filename in the ps file). The rest of the document does seem
to refer to "Aybabtu-Regular" instead of "PFAAybabtu-Regular", at
least (the same goes for PFAEmmentaler-23).

I tried manually replacing the #f's by paths to the respective font
files, but that doesn't work, either, not even when I change the
BeginFont directives and remove the extra "PFA" prefixes. I attached a
file that shows the ghostscript errors I get in that case, just in
case it might be helpful.

> > the "Convert to PDF" context menu item is gone, and PDF conversion
> > fails for *all* files now
> 
> How odd.  The menu item should be unconditionally written as (nsis command)
> 
>         WriteRegExpandStr HKCR "LilyPond\shell\generate\command" "" 
> '$INSTDIR\usr\bin\lilypond.exe "%1"'
> 
> maybe that does not work [for you], and the context menu you saw was a
> leftover from a previous Cygwin install?

I don't think Cygwin creates a context menu item - it really just
installs the binary package, which is then usable from a shell. But in
any case, I didn't uninstall the Cygwin package, so even if it was
left over from that one, it shouldn't be gone now.

> Jan.


-- 
schnee

error.log
Description: Text document