Hi,
Following a little bit of investigation, the changes I propose are given
below. Sorry, I couldn't get a diff off git (no git installed here, and
installing might be troublesome), so my 'hack' will be presented at the end
of this mail.
All this really does, is it makes 'registering the li
Hi,
There are actually two major problems with what the installer is currently
doing:
1) It used to add the lilypond path near the start of the PATH variable (but
I think that has been changed to be at the end at one point?)
2) It forces all python scripts to be run with the python bundled with
Thanks.
I'm starting to go with some C++ hacking. I can get the extra ledger
lines as long as I don't need them, when the note is outside of the
staff and normal ledger lines are created, as you mentioned. I
haven't yet lied to LilyPond about whether the note is outside the
staff, but I'll think
convert-ly converts from one version of lilypond to another. There's
a chance that the problem is related to an old version of lilypond, if
you are lucky.
Graham Percival <[EMAIL PROTECTED]> writes:
> Jim Hauxwell wrote:
>> I'm using capella-scan to scan some music into musicxml format and am
>>
Jim Hauxwell wrote:
I'm using capella-scan to scan some music into musicxml format and am
having some problems with lilypond.
Unfortunately musicxml2ly is currently not maintained. Patches are
welcome, but bug reports will not go anywhere.
Sorry,
- Graham
_
Don't talk nonsense! It works perfectly well to run commands like
convert-ly -e myfile.ly
from the command prompt.
Wow, sorry. I never thought that. It seems that I must update my knowledge.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.o
I was thinking a bit more. Installing and uninstalling LilyPond itself
should remain separate from jEdit. So there should be one installer that
separately installs the two.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu
Bertalan Fodor wrote:
Putting these into the path would also not help.
- you can not run convert-ly.py
Don't talk nonsense! It works perfectly well to run commands like
convert-ly -e myfile.ly
from the command prompt.
- you must use python convert-ly.py - But if you do, you must say:
python "
Putting these into the path would also not help.
- you can not run convert-ly.py
- you must use python convert-ly.py - But if you do, you must say:
python "c:\program files\lilypond\usr\bin\convert-ly.py" So you didn't
gain much.
Still I don't see it is useful.
Perhaps we should look at the p
Bertalan Fodor wrote:
Of course it should, but probably not the current \bin\ folder
Why? On Windows platforms people rarely use the PATH to run programs.
Since midi2ly, lilypond-book and the other utility scripts are not available
via any graphical interface. Of course, your immediate
Of course it should, but probably not the current \bin\ folder
Why? On Windows platforms people rarely use the PATH to run programs.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-deve
Of course it should, but probably not the current \bin\ folder but
a folder that only contains wrapper scripts to lilypond, lilypond-book,
midi2ly, ... which call the real programs from a directory that's not in
the PATH. This is the way it's done in the Linux installers.
/Mats
Bertalan Fo
I don't think that lilypond path should be in the PATH.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
As has already been stated. the Python bundled with LilyPond is
sufficiently functional to handle all the Python scripts such as midi2ly,
convert-ly, lilypond-book, ...
If you find any problem with any of these scripts, please send a bug report.
I guess your real problem is that you have installe
Hi,
On Wed, 21 Feb 2007, J L wrote:
> LilyPond's bundled python is useless (unless something has changed in
> the past 6 months), so I don't see why it is still bundled.
Maybe it is bundled, because LilyPond _needs_ Python? And Windows users
are typically too clueless to install all needed dep
J L escreveu:
> Hi,
>
> It's been a while since I've had much to do with LilyPond, but it seems
> that the installer is STILL fiddling with the registry in terms of python.
>
> What I would like to see:
> 1. Could the "call registry_python" line in the lilypond.nsh (or
> whatever) file used for g
LilyPond's bundled python is useless (unless something has changed in
the past 6 months), so I don't see why it is still bundled.
It is needed an perfectly good to run convert-ly.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http:/
Hi,
It's been a while since I've had much to do with LilyPond, but it seems that
the installer is STILL fiddling with the registry in terms of python.
What I would like to see:
1. Could the "call registry_python" line in the lilypond.nsh (or whatever)
file used for generating the installer be
Han-Wen Nienhuys wrote:
Graham Percival escreveu:
I have no clue how pngtopbm managed to find a "version 4.0.0". Does
anybody have any hints?
LilyPond uses pnggtopnm for scaling down PNG images. Unfortunately, there
is a version clash between libpng as shipped with lilypond and the one in
fi
Graham Percival escreveu:
> When I try to build the docs, I get the following error:
>
> Invoking `pngtopnm lily-39f2b92ff8.png.old | pnmscale -reduce 2
> 2>/dev/null | pnmtopng -compression 9 2>/dev/null > lily-39f2b92ff8.png'...
> dyld: Library not loaded: /sw/lib/libpng.3.dylib
> Referenced f
As far as I can see from the implementation, the ledger lines are only
typeset if the note pitch is outside the staff, so some C++ hacking would
be needed to get a clean solution for you. It should be possible to fool
LilyPond, though, by typesetting the note heads one octave too high
(for example
21 matches
Mail list logo