Re: lilypond-book in 2.5.13

On 6-Mar-05, at 3:29 PM, Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: The resulting ps/pdf had staff lines, bar lines, and note stems; no noteheads, clef, etc. you still need -u+lilypond.map Argh. Sorry! It works perfectly. - Graham ___ lilypond-d

lilypond-book in 2.5.13

[EMAIL PROTECTED] writes: > I've just tried lily 2.5.13 in fink. Lilypond itself works ok, > although the fonts > are quite heavy. Han-Wen mentioned that they might be displaying in > bold? > > lilypond-book (I used the LaTeX example template from chapter 3 of the > manual; see below) wasn't h

Re: OpenBSD fix for fopencookie

Jan Nieuwenhuizen wrote: Matt Jibson writes: This appears to have worked. With another patch to make utf8 wchar support work it compiled and linked. utf8 patch? Do we want to include that? Probably not, it's just an include fix in lily/general-scheme.cc: -#include /* wcrtomb */ +#include

Re: OpenBSD fix for fopencookie

Matt Jibson writes: > This appears to have worked. With another patch to make utf8 wchar > support work it compiled and linked. utf8 patch? Do we want to include that? > It's now tracing bitmaps. Thanks for providing patches so quick for > BSD support. You're welcome. Jan. -- Jan Nieuwenhuiz

lilypond-book in 2.5.13

I've just tried lily 2.5.13 in fink. Lilypond itself works ok, although the fonts are quite heavy. Han-Wen mentioned that they might be displaying in bold? lilypond-book (I used the LaTeX example template from chapter 3 of the manual; see below) wasn't happy: 1) \usepackage{graphics} needs to

Re: OpenBSD fix for fopencookie

Jan Nieuwenhuizen wrote: Matt Jibson writes: This patch just relocates the error: Hmm, silly me. I've now added plain casts in CVS. If that doesn't work, we probably need a developer with a BSD system to look into this. This appears to have worked. With another patch to make utf8 wchar su

Re: chroot/setuid for lilypond (for LSR)

On Sun, 2005-03-06 at 21:44 +0100, Han-Wen Nienhuys wrote: > The patch is in. > It should still be documented. Maybe you can work this out with > Graham? OK. Graham, do you think you can give me the piece of texinfo source (it is my understanding that the manual is in texinfo) with the descriptio

Re: smooth CFF fonts?

> I noticed that the music symbols in PDF files now look much worse in > Acrobat compared to the Type1 fonts. The curves look jaggy. Am I > correct that the CFF files aren't antialiased/hinted? > Is this is a FontForge, GS, Acrobat or PDF problem? According to the ttx disassembler, the OTFs are

Re: [Lily4jedit-devel] [Fwd: easier LilyPond tutorial?]

[EMAIL PROTECTED] writes: > I checked the emacs tutorial. I don't think we should have a very > special mode in lily4jedit. If we use the lilypond mode, our plugin gets > active. So we can check for a special comment that turns the tutorial > mode on, that - for example - draws some background c

Re: OpenBSD fix for fopencookie

Matt Jibson writes: > This patch just relocates the error: Hmm, silly me. I've now added plain casts in CVS. If that doesn't work, we probably need a developer with a BSD system to look into this. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.

Re: [Lily4jedit-devel] [Fwd: easier LilyPond tutorial?]

I checked the emacs tutorial. I don't think we should have a very special mode in lily4jedit. If we use the lilypond mode, our plugin gets active. So we can check for a special comment that turns the tutorial mode on, that - for example - draws some background color for the indented blocks. The

Re: chroot/setuid for lilypond (for LSR)

[EMAIL PROTECTED] writes: > On Sun, 2005-03-06 at 00:04 +0100, Han-Wen Nienhuys wrote: > > > If you resend with this change, I will apply the patch. > > > > Here it is. The patch is in. It should still be documented. Maybe you can work this out with Graham? -- Han-Wen Nienhuys | [EMAIL

Re: [Lily4jedit-devel] [Fwd: easier LilyPond tutorial?]

[EMAIL PROTECTED] writes: > >For a typical mac/windows user this is a rough introduction. We were > >wondering whether it was possible to provide something similar to the > >Emacs tutorial, where a user is really taken by the hand learning > >LilyPond. > > Its pretty shameful I havnt tried (or re

Re: OpenBSD fix for fopencookie

Jan Nieuwenhuizen wrote: Matt Jibson writes: The current CVS gives a much nicer error: Thanks. I've added the patch below to CVS. Can you check if that works for you? Jan. [...] This patch just relocates the error: memory-stream.cc:28: error: invalid conversion from `ssize_t (*)(void*, c

OTF no PostScript name

Hi! just wondering, why do OTF fonts return null for FT_Get_Postscript_Name()?. If I understand correctly, CFF files only contain the outlines, but OTF has everything, doesn't it? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___

Re: tetex-3 updmap

Bertalan Fodor writes: > Ok, I'll try. Thanks! > I'm working on it... however there are ec-fonts issues there (I guess > I have to rebuild them with the latest CVS of mftrace). Ok, sorry. I thought you had it prepared already. Not to hurry. Good luck, Jan. -- Jan Nieuwenhuizen <[EMAIL PROT

Re: tetex-3 updmap

can you prepare a patch and send it to tetex@dbs.uni-hannover.de Ok, I'll try. When do you want to upload your texex-3-safe lilypond? I'm working on it... however there are ec-fonts issues there (I guess I have to rebuild them with the latest CVS of mftrace). Bert _

Re: OpenBSD fix for fopencookie

Matt Jibson writes: > The current CVS gives a much nicer error: Thanks. I've added the patch below to CVS. Can you check if that works for you? Jan. --- libc-extension.hh 28 feb 2005 20:03:16 +0100 1.26 +++ libc-extension.hh 06 mrt 2005 10:14:05 +0100 @@ -53,6 +53,8 @@ extern "