lilypond-devel
[Top][All Lists]
Advanced

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

Re: GDP: only 3 weeks left


From: John Mandereau
Subject: Re: GDP: only 3 weeks left
Date: Tue, 29 Jul 2008 14:39:39 +0200

Hi everyone,
2008/7/27 Graham Percival <address@hidden>:
> There's only three weeks left in the Grand Documentation Project
> of LilyPond.  On Aug 18, I'm going to stop handling contributors
> -- my thesis defense is on Aug 19, and after the defense I only
> have three days to complete any necessary changes, or else my
> graduation will be delayed by 8 months.  I love you guys dearly,
> but I'm not going to take any risks with this.  :)   So Monday, 18
> Aug 2008 is a hard deadline for any contributions.

I finally begin to find little time to read and proofread post-GDP
docs, and I especially would like to proofread (not translate right
now) LM 3: there are  some ends of sentences with cross-references
which look strangely phrased in Info output, and there are minor
errors like in 3.3.4 Modifying context properties:

"""
This is one of the reasons why it is highly recommended to use a
context-sensitive editor with syntax highlighting for editing LilyPond
input files, such as Vim, Jedit, ConTEXT or Emacs, since unknown
property names will be highlighted differently.
"""

There is no list of context properties in Emacs and Vim modes, so all
context properties are highlighted the same way regardless of their
existence.  Jedit/LilyPondTool doesn't check context properties when
it highlights them, although you can verify that a context property in
your source file exists by moving the mouse pointer over the property
name: if it exists, its docstring appears in a bullet.  I agree it'd
be nice to check context properties, but until this feature is added
the sentence above is wrong.

Trevor, may I work on LM 3 and push such minor corrections directly to
Git master?  I think this will be more efficient for than sending a
list of comments in an email.  Of course I'll send an email for
general suggestions and before making important changes.

Cheers,
John




reply via email to

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