lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is GUB consistent across platforms?


From: Mats Bengtsson
Subject: Re: Is GUB consistent across platforms?
Date: Thu, 27 Apr 2006 15:53:52 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511



Jan Nieuwenhuizen wrote:

Mats Bengtsson writes:

which unfortunately doesn't support UTF-8 encoding, for example.

That should depend on what flavour of Windows you have.  The editor
is built in two flavours, there is a unicode and ascii one.

At least the one I get on Windows XP doesn't support UTF-8. How do I
check which version is used?

Also, there is no menu entry for running convert-ly on a file, if
that's what you also asked.

Patches thoughtfully considered.  :-)
Without having the faintest idea of what I'm really doing, I guess that something
like the following might work:

--- lilypond.nsi.in.orig        2006-04-27 14:22:07.000000000 +0200
+++ lilypond.nsi.in     2006-04-27 15:47:04.000000000 +0200
@@ -367,6 +367,13 @@
       WriteRegStr HKCR "LilyPond\shell" "" "open"
WriteRegExpandStr HKCR "LilyPond\shell\open\command" "" '"$EDITOR" "%1"'

+;;ly_convert:
+       ReadRegStr $R0 HKCR "LilyPond\shell\convert\command" ""
+       ;;StrCmp $R0 "" 0 ly_generate
+       WriteRegStr HKCR "LilyPond\shell" "" "convert"
+       WriteRegStr HKCR "LilyPond\shell\convert" "" "&Update syntax..."
+ WriteRegExpandStr HKCR "LilyPond\shell\convert\command" "" '"$INSTDIR\usr\bin\convert-ly.py -e" "%1"'
+
;;ly_edit:
       ReadRegStr $R0 HKCR "LilyPond\shell\edit\command" ""
       ;;StrCmp $R0 "" 0 ly_generate


At second thought, I'm certain that it doesn't work out of the box, since
the Python that's included in the package currently it broken so that none
of the Python scripts work.

Actually, as long as the Python build is broken, it would be much better to
exclude Python completely from the package and just add an instruction on the
Downloads page on how to download and install Python from www.python.org.
As long as it's included in the LilyPond package, you have to manually make sure that the working version of Python comes before LilyPond's broken one in the PATH variable as soon as you update LilyPond. If we leave it out from the LilyPond
package, it's sufficient to install Python once and for all.

/Mats



reply via email to

[Prev in Thread] Current Thread [Next in Thread]