Le 9 janv. 08 à 00:37, Valentin Villenave a écrit :
2008/1/7, Tim Reeves <[EMAIL PROTECTED]>:
4. What is a .ily file?
It is basically, as far as I can understand, a programmer's use: you
can't give the same extension to a file that is meant to be compiled
as is, than to another file that is only meant to be included in
another.
(actually, you perfectly can, but it's just inelegant I guess)
So Nicolas has this very elegant solution, that is to name all his
files something.ily, then include them all in a master file, and only
give the .ly extension to the master file that has to be compiled.
I assume the "i" in "ily" stands fot "inclusion" or whatever.
It seems that there is no widespread convention or consensus
regarding extension of LilyPond files that are not compilable, but
should be included in other files. See for instance this thread:
<http://lists.gnu.org/archive/html/lilypond-devel/2003-09/msg00025.html
>
I chosed to use ".ily" for my scores because of the analogy with
.texi/.itexi, .tely/.itely, etc. And I seem to recall that ".ily"
has been used for some files in the LilyPond distribution.
[...searching...] Actually that's still the case:
./input/manual/engraver-example.ily
./input/mutopia/W.A.Mozart/mozart-hrn3-allegro.ily
./input/mutopia/W.A.Mozart/mozart-hrn3-defs.ily
./input/mutopia/W.A.Mozart/mozart-hrn3-romanze.ily
./input/mutopia/W.A.Mozart/mozart-hrn3-rondo.ily
./input/regression/allfontstyle.ily
nicolas
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
