> concept to show to developers. I think what has happened is that the > developers have concentrated on features and output. That is great,
> because the output is pretty impressive. They did not think about
> language design, though. And lilypond is basically a programming
> language.
>
> One thing I'm not sure about is how TeX like it should be. For
> example, in lilypond
>
> \markup{ \italic this is some text}
>
> is subtly different from TeX
>
> {\it this is some text}
>
> In the first, only "this" is italic. In the second, the entire string > is italic. I'm not sure if these should be rationalized or not.
>
> I think the first thing I will do is put together a language
> reference. The fact that one does not exist shows that the language
> has been something of a second class citizen to output. Once I see
> what is there, perhaps how best to simplify things will be more
> apparent.
Hi,
Sounds like an interesting plan, but have a look at the existing documentation first, I think there is already quite some reference documentation available. (from the website: follow the links to documentation, then program reference)
Best regards, Stefaan.
_______________________________________________ lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
