On Wed, Jan 27, 2010 at 6:44 AM, Bernard Hurley <bern...@marcade.biz> wrote: > On Mon, 2010-01-25 at 12:15 -0800, Patrick McCarty wrote: >> I have one more idea that might narrow down the problem: >> >> Does the time signature look correct in the PDF output when using >> \numericTimeSignature ? I'm curious, because the feta-alphabet Type 1 >> fonts are loaded in the same way for the default (PDF) output as for >> the SVG output. >> >> If you want to see exactly which fonts are loaded for the PS/PDF >> output, invoke LilyPond as below, and examine the header of the >> PostScript file. Search for "%%DocumentSuppliedResources". >> >> $ lilypond -dno-delete-intermediate-files myfile.ly > > I have been looking at version 2.12.2 (as installed by the Ubuntu > package) and this too has font problems. I am beginning to think the > problem only effects lilypond on Ubuntu.
That's unfortunate. :-( > 1] Doing: > > $ lilypond -dno-delete-intermediate-files myfile.ly > > where myfile.ly is: > > { \times 3/4 c' } > > with either 2.12.2 or 2.13.12.The PDF doesn't look correct. The > header of the ps file shows the following fonts are loaded: > > %%DocumentSuppliedResources: font CenturySchL-Roma > %%DocumentSuppliedResources: font CharisSIL > %%DocumentSuppliedResources: font Emmentaler-20 Okay, that confirms my suspicion that there is a more general problem. > 2] Something has changed since 2.12.2 since: > > $ lilypond -dbackend=svg myfile.ly > > does produce a readable svg file (but with the wrong font, of > course) with version 2.12.2. However, with version 2.13.12 it > produces an unreadable svg file and the error: > > Layout output to > `myfile.svg'.../home/consultant/lilynew/lilypond/out/share/lilypond/current/scm/lily-library.scm:709:25: > In procedure ly:font-name in expression (ly:font-name font): > > /home/consultant/lilynew/lilypond/out/share/lilypond/current/scm/lily-library.scm:709:25: > Wrong type argument in position 1 (expecting Font_metric): > "CharisSIL" Yes, the SVG font loading mechanism changed between 2.12.* and 2.13.4. In 2.12.*, the entire SVG fonts were included within every SVG output file, but in 2.13.4 and on, glyphs are extracted from the appropriate SVG font. > 3] There is nothing special about CharisSIL, > > If I remove it, DoulosSIL takes it's place. I thinking that it > might have something to do with fontconfig not understanding > lilypond's font instructions and substituting a system font, I > tried replacing the Ubuntu version of fontcong with the Debian > "lenny" version, but it makes no difference. I don't know if fontconfig is to blame or not (at this point). > In addition to the above, there are some (possibly unrelated > font-related errors thrown up while compiling lilypond 2.13.12, For > instance: > > Invoking "fontforge -script feta11.pe feta11.pfb"... > Copyright (c) 2000-2009 by George Williams. > Executable based on sources from 22:35 GMT 22-Jun-2009. > Library based on sources from 22:35 GMT 22-Jun-2009. > Internal Error in accidentals.flat.arrowdown: monotonic is both needed > and unneeded. > Internal Error in accidentals.flat.arrowdown: monotonic is both needed > and unneeded. > Internal Error in accidentals.flat.arrowdown: Expected needed > monotonic. > > and: > > Internal Error in accidentals.sharp.arrowup: couldn't find a needed > exit from an intersection > Internal Error: > Could not find finalm > > and: > > Invoking "fontforge -script feta26.pe feta26.pfb"... > Copyright (c) 2000-2009 by George Williams. > Executable based on sources from 22:35 GMT 22-Jun-2009. > Library based on sources from 22:35 GMT 22-Jun-2009. > Internal Error in scripts.varcoda: couldn't find a needed exit from an > intersection > Internal Error: > Could not find finalm > Internal Error in scripts.varcoda: couldn't find a needed exit from an > intersection These errors appear because your Fontforge was not compiled with the "--enable-double" configure flag. They disappear when "--enable-double" is used. It might be a good idea to report this upstream. I'm still really unsure about the source of this problem. Some more things I would try: 1) Run `ldd lilypond' after you've installed your self-compiled 2.13.12 to check for linking errors. 2) Run `lilypond -dshow-available-fonts 2> fonts.log' and see if the log lists the "feta-alphabet" fonts. 3) Try compiling/installing all of LilyPond's dependencies from scratch, and then compile LilyPond. See if you get the same results. Let me know how it goes. Have you tried the GNU/Linux installers from lilypond.org? Those should work out-of-the-box. Thanks, Patrick _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond