[EMAIL PROTECTED] writes:
> I would like to make the following proposal for the binary
> distribution of the Windows NT version of lilypond.
Let me first stress, that I've got nothing to do the NT port, so all
my comments are to be taken for what they're worth.
> 2. I propose a python version of ly2dvi called ly2dvi32.py. This will
> allow Window's folks to generate music with titles and the like.
I would like to propose to redo ly2dvi in python completely. It
doesn't make sense to have a sh script around when a working .py
script is there.
> 3. Initially this distribution would be a zip file. The installation
> should require an unzip with little to no post installation steps
> other than setting the path variable.
OK.
> 4. Eventually I would like to see an InstallShield like installation
> interface. I have searched for a freeware version of such a thing
> and have not been successful.
I can't see why this is needed. The installation would boil down to
unzip -d zipfile
and deinstallation
deltree lilypond-X
I don't think that this warrants special installers.
> 1. Hard coded lilypond search path does not suit relocation of
> the binary.
>
> o ly2dvi32.py will handle this thru the use of argv[0].
> o We could make lilypond's internal search path use argv[0] as a
> seed to the internal search path.
It could be done; however, on Unix argv[0] is usually useless.
> 2. Internationalization. Being a bone headed American, I don't know
> if this is an issue or not. I assume the internationalization code
> in gettext keys off of environment variables.
We did Internationalization for the pure reason of Coolness (TM). I
think that the NT port can do without.
> 3. Search path separation in Windows is ';' not ':'.
>
> o I believe I remember seeing a cpp macro in the flower lib for the
> search path separation character.
OK.
> 4. Environment variables. Not being an experienced NT user I don't
> know if this is an issue or not. Many programs seem to set values
> in the registry during the post installation process. I'm not so
> crazy about this however.
me too. But it might be inescapable for TeX and MF. Have you given
this thought?
>
> 5. I presently can not generate the web documentation due to my
> inability to find command line graphic translators for the Windows
> NT platform.
>
> o Any suggestions for pstogif etc. on windows?
ps-to-gif is in buildscripts/. You need the PBM utilities.
> I have a rough draft of python32.py that I have been using. And with
> the blessing of the major contributors, I would be willing to
> distribute the proposed binary to anyone who is interested.
That is OK. There is one issue remaining: an FTP site. I want to
migrate away from pcnov095.win.tue.nl, because of various
inconveniences, so I would appreciate it if you set up an FTP site or
web site yourself.
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
