Re: Directed \tweak commands in 2.15.39

[David Kastrup]

Janek Warchoł <address@hidden> writes:

> On Thu, May 24, 2012 at 12:39 AM, David Kastrup <address@hidden> wrote:
>
>> Writing good docs is lots of hard work.  Adapting it to a new input
>> syntax, in contrast, dead easy.  Most of the work will likely even be
>> done by convert-ly.
>
> As long as GLISS changes only the /naming/ of the
> commands/properties/etc., you are completely right.  However, i'd like
> to discuss some more fundamental changes during GLISS; i'm thinking
> about GLISS a lot and i have a quite strong feeling that there are
> some big changes that would really benefit LilyPond.  And they would
> probably quite noticeably change the way in which users write lily
> code.

And it would still be mostly trivial to adapt existing documentation.
If someone were to write a book about using LilyPond (and our docs are
not really anything but that), and then GLISS came along: you think he
would scrap the book and start fresh?  No, you'd get "Using LilyPond --
2nd edition".  Perhaps new chapters, and adjustments in some existing
chapters.

Using GLISS as an excuse for keeping the documentation in abysmal state
is far too cheap and it does not at all make sense.  In particular since
good and/or efficient documentation writers tend to be different people
than good and/or efficient programmers, and good documentation draws
both into participating with the project, making things progressively
smoother.

-- 
David Kastrup