Re: glossary - add 'high bass clef'

[ArnoldTheresius]

James wrote
> Hello,
> 
> ...
> 
> Well I have applied this patch and I am not sure it is appropriate for
> the glossary, perhaps the explanation, but the example is far too
> complex for our documentation - perhaps as a snippet maybe.
> 
> Also you have not followed really any of our style guidelines in the
> Contributor's Guide (line lengths, texinfo syntax, @lilypond
> [variables] etc. so there is still a fair amount of work to do here
> before it will even be considered.
> 
> So, I can do this for you (shepherd your patch) or you are more than
> welcome to use our git-cl and patch review process yourself until you
> need to push it, when you will need to prepare a properly formatted
> git patch that is easy to apply etc (i notice your $LILYPOND_GIT
> variable is not the standard one, making it slightly more work for
> those that need to apply it - I am no expert but managed to work it
> out). I don't want to discourage you from submitting patches, but we
> do have a well defined (if slightly idiosyncratic work-flow - so I am
> told, I only know LilyPond so cannot comment)
> 
> If you do choose to do this yourself you should read our Contributor's
> Guide and follow the style guidelines there, and I suggest that you
> take the huge example out, cut it right back as you can and include it
> as a snippet.
> 
> See:
> 
> http://lilypond.org/doc/v2.16/Documentation/contributor/documentation-work
> 
> and
> 
> http://lilypond.org/doc/v2.16/Documentation/contributor/summary-for-experienced-developers
> (the reviews section specifically).
> 
> James
> 
> _______________________________________________
> bug-lilypond mailing list

> bug-lilypond@

> https://lists.gnu.org/mailman/listinfo/bug-lilypond

Well,

I noticed, the example is quite huge. But I'm not sure, can it be understood
without example?
If so, we can completely remove the snippets.

I think the line length of 80 characters was succeded only in the
'snippets'.

What could a 'separate snippet' want to tell? Perhaps "How to build a pitch
usage chart manually".

I did try to use only the syntax I found in the '.tely' file, but I did not
look (deeply) into the documentation contributors guide. Sorry for that.

To upload contributions by myself: My computer I'm working with lilypond is
not connected to any network. (For that reason I prefer the PDF of the
handbooks to the HTML version) So at first I'll need to find some
description how to operate this in a 'package mode', i.e. GIT-access (in a
HTML browser) at one computer, transfer files to and from the working
computer (the most easy step), import and export the file packages in the
working computers lilydev VM.
Do you know where such an description is?

ArnoldTheresius



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/glossary-add-high-bass-clef-tp135206p135215.html
Sent from the Bugs mailing list archive at Nabble.com.