> Now lets create some files:
> $ make -C Documentation/user web
> # Ctrl-C after a minute or so
> $ time mf-nowin -progname=mf "\mode:=ljfour; mode_setup; end."
> real0m32.998s
> user0m28.638s
> sys 0m4.336s
Try this for both cases:
KPATHSEA_DEBUG=-1 mf-nowin -progname=mf "\mode:=
Hi all,
I've been struggling with a problem for several days now -- I'm unable to run
configure without first deleting all my out-www directories and I can't
finish "make web". Configure seems to hang forever on "checking for working
metafont mode..." and make web hangs on bibtex.
So I did som
Le vendredi 13 avril 2007 à 19:30 +0300, Till Rettig a écrit :
> Hi John,
> another correction in de/user/working.itely.
Thanks, it's applied as well as 'update to the website'.
Cheers,
John
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://li
Hello,
Le vendredi 13 avril 2007 à 11:46 -0700, Graham Percival a écrit :
> Till Rettig wrote:
> > Then I removed naive-notation.png in the directory
> > site/images and created naive-notation.svg in the directory site/graphics
>
> I don't recommend this; svg images at least don't work in firefox
Graham Percival wrote:
Till Rettig wrote:
Then I removed naive-notation.png in the directory site/images and
created naive-notation.svg in the directory site/graphics
I don't recommend this; svg images at least don't work in firefox on
OSX. I'd be pleasantly surprised if they work easily o
Till Rettig wrote:
Then I removed naive-notation.png in the directory
site/images and created naive-notation.svg in the directory site/graphics
I don't recommend this; svg images at least don't work in firefox on
OSX. I'd be pleasantly surprised if they work easily on other OS as
well. For
Hi,
I tried for some hours to change a picture
(site/images/naive-notation.png) from the website
(site/about/automated-engraving/...) into an svg image and then let it
be translated the same way as those pictures of the switch/howto.html. I
did the following:
creating the notes with lilypon
Hi John,
another correction in de/user/working.itely.
Till
>From 56f6158f30116993f4b81c4ff75ce5b05ac440ca Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Fri, 13 Apr 2007 19:14:33 +0300
Subject: [PATCH] update to de/user/working.itely
---
Documentation/de/user/working.itely
Hi,
just found a bug in the po/de.po on web/master, here is the fixing patch.
Till
>From c3215ba0e0a1ee0411178fb22eb2f4f9c056c967 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Fri, 13 Apr 2007 19:09:59 +0300
Subject: [PATCH] update po/de.po
---
po/de.po |2 +-
1 file
2007/4/13, Mats Bengtsson <[EMAIL PROTECTED]>:
I completely agree about the problem! Since we started moving properties
into details, we have lost the documentation of a number of them (some
are now described within the main manual, but not all). From a users
perspective,
I agree about this, h
2007/4/13, Mats Bengtsson <[EMAIL PROTECTED]>:
Implement it as a standalone program. We have a number of similar converters
today included in the LilyPond distribution, such as midi2ly, abc2ly, etf2ly
implemented in the Python scripting language. If you want your converter
included with LilyPond
[EMAIL PROTECTED]:
> I am currently working with a cataloging project at the British
> Library which is recording all musical manuscripts between the years
> 1600 and 1800, I have developed an application for them to data input
> and manage the manuscripts. The information supplied with each
Implement it as a standalone program. We have a number of similar converters
today included in the LilyPond distribution, such as midi2ly, abc2ly, etf2ly
implemented in the Python scripting language. If you want your converter
included with LilyPond you should therefore also implement it in Python
Hello all,
I am new to Lilypond and the devel list so hello to everyone. I
think Lilypond is a fantastic program and as I am a developer would
like to contribute something to the project. Selfishly, I would like
my first contribution to be something that convert an ancient incipit
to th
I completely agree about the problem! Since we started moving properties
into details, we have lost the documentation of a number of them (some
are now described within the main manual, but not all). From a users
perspective,
the introduction of these subproperties has definitely not been an
im
15 matches
Mail list logo