From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Lilypond
Date: Mon, 13 Apr 2015 09:56:00 -0000 [thread overview]
Message-ID: <552B92C4.1010203@gmail.com> (raw)
In-Reply-To: <552AE74F.3080406@gmail.com>
On 4/12/2015 11:44 PM, Marco Atzeri wrote:
> On 4/12/2015 10:39 PM, Eliot Moss wrote:
>> On 4/12/2015 4:17 PM, David Stacey wrote:
>>> On 12/04/15 11:03, Marco Atzeri wrote:
>>
>>> Seemed to work well with all the '.ly' files I threw at it. I
>>> generated PDF, PNG and MIDI files
>>> successfully. I tried a few files from a web site with lots of freely
>>> available lilypond files, and
>>> a couple of files gave warnings. If you try:
>>>
>>> wget
>>> http://www.mutopiaproject.org/ftp/PaganiniN/O1/Caprice_23/Caprice_23.ly
>>> lilypond --formats=pdf,png Caprice_23.ly
>
>>>
>>> warning: no PostScript font name for font
>>> `/usr/share/fonts/100dpi/ncenR24.pcf.gz'
>>> warning: FreeType face has no PostScript font name
>>
>> I was getting that with the previous version, and segfaults. I had to
>> back up some to
>> get it to work at all, and I recall, I still can't get Times Roman. I
>> wasn't sure who /
>> how to report it, but this thread prompts me to chime in.
using 2.19.18 I see
warning: no PostScript font name for font
`/usr/share/fonts/75dpi/ncenR24.pcf.gz'
warning: FreeType face has no PostScript font name
warning: no PostScript font name for font
`/usr/share/fonts/75dpi/ncenB24.pcf.gz'
warning: FreeType face has no PostScript font name
warning: no PostScript font name for font
`/usr/share/fonts/75dpi/ncenB24.pcf.gz'
warning: FreeType face has no PostScript font name
programming error: Improbable offset for stencil: -inf staff space
Setting to zero.
continuing, cross fingers
Layout output to `Caprice_23.ps'...
Converting to `./Caprice_23.pdf'...
Converting to PNG...
Success: compilation successfully completed
the warning is also mentioned here
http://comments.gmane.org/gmane.comp.gnu.lilypond.general/93663
But it seems not related to segfaults.
Building docs still hang in some place but I will deploy 2.19.18
with PDF only documentation.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-04-13 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 1:00 [ANNOUNCEMENT] Updated: make-4.1-1 Ti Strga
2015-02-20 15:42 ` Franz Sirl
2015-02-20 16:20 ` Libguile17 dependency issue - attention maintainer Marco Atzeri
2015-02-20 16:21 ` Cosimo Lupo
2015-02-20 16:42 ` Marco Atzeri
2015-02-20 17:24 ` Achim Gratz
2015-02-20 19:08 ` Yaakov Selkowitz
2015-02-20 16:24 ` Corinna Vinschen
2015-02-20 16:41 ` Marco Atzeri
2015-02-20 17:05 ` Corinna Vinschen
2015-02-21 0:50 ` David Stacey
2015-04-12 10:03 ` Marco Atzeri
2015-04-12 13:11 ` David Stacey
2015-04-12 20:17 ` David Stacey
2015-04-12 20:39 ` Eliot Moss
2015-04-12 21:45 ` Marco Atzeri
2015-04-13 9:56 ` Marco Atzeri [this message]
2015-04-13 11:54 ` Lilypond Eliot Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552B92C4.1010203@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).