* Finding functions::
* Code style::
* Debugging LilyPond::
-* Checklist for adding features::
+* Adding or modifying features::
@end menu
@node Overview of LilyPond architecture
a documentation editor will be able to write it from the regression
tests.
+If the modification changes the input syntax so that inline snippets in
+the documentation need to be changed, you will need to change the
+snippets in both the english version of the documentation and any
+translated versions. If you do not change the snippets in all
+translations, older versions of the snippet may be included
+when the documentation is built.
+
+If lsr snippets need to be changed, the snippet should be copied to
+input/new and modified there. The portions of the snippet that
+are added by makelsr.py should be removed. The changed snippet
+will then be included in all versions of the documentation.
+
+If non-snippet text is changed in the english documentation, no
+corresponding changes should be made in the translated documentation.
+
@subsection Write convert-ly rule
If the modification changes the input syntax, a convert-ly rule
closed.
On Rietveld, the author should log in an close the issue either by
-using the @quote{Edit Issue} link, or by clicking the circled x icon
+using the @q{Edit Issue} link, or by clicking the circled x icon
to the left of the issue name.
If the changes were in response to a feature request on the Google
issue tracker for LilyPond, the author should change the status to
-@quote{Fixed_x_y_z} where the patch was fixed in version x.y.z. If
+@q{Fixed_x_y_z} where the patch was fixed in version x.y.z. If
the author does not have privileges to change the status, an email
should be sent to bug-lilypond requesting the BugMeister to change
the status.