Here is a list of jobs that are available. They have all been mentioned
as things that I could do; I think they're all useful things to be done,
but I don't have the resources to do them in the near future.
If you're interested in helping, please ask for more info. If you'd
like to help but
Ruud van Silfhout wrote:
Graham Percival wrote:
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
I think there is a small typo in the documentation-adding page.
In the sentence "Ask on the lilypond-devel mailist if such a rewrite
I'm sorry but I made a mistake concerning the title of the second mail:
"Priority 2 Translation of web site to spanish"
It was supposed to be for the:
Priority 3 Translation of web site to spanish
I attach it again just in case it went unnoticed because of the title.
My apologies for any inconv
Graham Percival wrote:
Could one or two people proofread the new pages on bug reports and doc
suggestions?
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
I think there is a small typo in the documentation-adding page.
In the se
John Mandereau escreveu:
> Dear LilyPond hackers,
>
> The subject says it: I'd like to be notified of make/'make web' failures
> on the master branch. Could you for example send these notifications to
> lilypond-cvs@gnu.org again?
>
> I can live without them, but they can be handy. If you don't s
El vie, 29 de dic de 2006, a las 12:54:58 -0600, Daniel Tonda Castillo dijo:
> >Another nitpick: are you the only translator or are you in a team? All
> >translators should be credited in about/thanks#website.
> >
> There's Francisco Vila also.
...but he's not yet working on it. I do not deser
Here's a patch which implements the volta bracket behavior I proposed
as a user settable option. The default behavior remains unchanged.
The alternate behavior can be turned on by voltaBracketFinish to true.
Two regression tests are also attached. One tests the default
behavior and the other th
On Sat, 30 Dec 2006 13:44:10 +0100
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> > If anything, I think we should be looking to remove the optional
> > pitch argument, and force people to specify the octave in the first
> > note
>
> Yes, I agree.
Cameron Horsburgh wrote:
Here's a small addition for the docs. It is intended to go in Section
8.2.3 (Rehearsal marks) after the sentence "You may use
Thanks, added.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.or
Graham Percival <[EMAIL PROTECTED]> writes:
> I disagree; faking snippets is what started the whole thing. I think
> we should simply not explain it for the first few snippets (ie the
> "here's how to use lilypad" stuff), and explain it in 2.2.
Ok.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]
Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
If anything, I think we should be looking to remove the optional pitch
argument, and force people to specify the octave in the first note
Yes, I agree. But I think we can explain that when we get to octave
entry, and shoul
Cameron Horsburgh wrote:
On Thu, Dec 28, 2006 at 07:15:07PM -0800, Graham Percival wrote:
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
There's one small error on the doc adding page, where you seem to have
cut 'n' paste from
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> If anything, I think we should be looking to remove the optional pitch
> argument, and force people to specify the octave in the first note
Yes, I agree. But I think we can explain that when we get to octave
entry, and should fake it in the first fe
On Thu, Dec 28, 2006 at 07:15:07PM -0800, Graham Percival wrote:
> Could one or two people proofread the new pages on bug reports and doc
> suggestions?
>
> http://lilypond.org/web/devel/participating/bugs
> http://lilypond.org/web/devel/participating/documentation-adding
>
There's one small er
Graham Percival <[EMAIL PROTECTED]> writes:
>> * use more complete and interesting examples lateron to explain
>> several related concepts
>
> Maybe, maybe not. I'd have to judge those on an individual basis.
Yes, of course. Attempts were the lead sheets, piano part, orchestral part.
> I
Here's a small addition for the docs. It is intended to go in Section
8.2.3 (Rehearsal marks) after the sentence "You may use
format-mark-barnumbers, format-mark-box-barnumbers, and
format-mark-circle-barnumbers to get bar numbers instead of
incremented numbers or letters."
Given the overlap of su
Graham Percival escreveu:
> Han-Wen Nienhuys wrote:
>> (or whatever) and run
>> python setup.py py2app --iconfile lilypond.icns
>
> I'm running into problems with "URLHandle.scriptSuite". I noticed the
> URLHandlerClass.py, so I tried running that in case it "compiled" and
> produced the .scrip
Graham Percival escreveu:
>> * only tell novices about relative mode, because that is what you'll
>> use anyway (apropos: we have made several attempts to make \relative
>> the default, and introduce an \absolute keyword/mode for expert
>> use, eg algorithmic composition. we still ma
Han-Wen Nienhuys wrote:
(or whatever) and run
python setup.py py2app --iconfile lilypond.icns
I'm running into problems with "URLHandle.scriptSuite". I noticed the
URLHandlerClass.py, so I tried running that in case it "compiled" and
produced the .scriptSuite file. That didn't work, eit
Hi,
On Sat, 30 Dec 2006, Daniel Tonda wrote:
> ¿The commitish id has changed for these files, this is the expected
> behaviour?
Yes. A commit in git is sort of a tag: It contains everything which makes
up a revision. So, if you say "git commit", you actually construct a new
state from the _wh
Han-Wen Nienhuys wrote:
I suggest to replace this:
"Every piece of LilyPond input needs to have {curly braces} placed
around the input. For the rest of this manual, most examples will omit
these braces, but don't forget them in your own music!"
with this (also note the inserted whitespace arou
Jan Nieuwenhuizen wrote:
* have a very gentle entry introducing only one concept at a time
Agreed.
* have learnful examples that clearly show the most interesting thing,
but not necessarily ready-to-copy (and we introduced clickable-ly's
for that
I disagree somewhat, and the rec
Just as in the lilypond documentation:
Git:
... in small digestible and programmable chunks...
Thanks, I've been re-reading this thread, I'll get it bit by bit but I will. ;)
Daniel T.
2006/12/30, Johannes Schindelin <[EMAIL PROTECTED]>:
Hi,
On Fri, 29 Dec 2006, Daniel Tonda Castillo wrote:
Hi,
On Fri, 29 Dec 2006, Daniel Tonda Castillo wrote:
> From what I gather, so far if no write acces is provided, the most
> important git commands would seem to be clone and patch, but patch is
> still not clear for me yet.
The most important git command (at least to me) is git-diff. Say, you
I've finished the priority 3 files for the lilypond-web site:
According to the mail I sent about dangling directory, the files should be:
es/sponsor/index.html
es/sponsor/natura.html
es/sponsor/options.html
es/about/automated-engraving/applications.html
es/about/automated-engraving/benchmarking.
Hi,
On Fri, 29 Dec 2006, John Mandereau wrote:
> Le vendredi 29 décembre 2006 à 20:01 +0100, Han-Wen Nienhuys a écrit :
> > John, could you have a look at updating the README with this info,
> > so it is understandable for git newbies?
>
> By the way, do you mind if I explain this with cogito
Hi,
On Fri, 29 Dec 2006, Han-Wen Nienhuys wrote:
> Johannes Schindelin escreveu:
> >
> > $ git fetch git://git.sv.gnu.org/lilypond.git/ web/master:web/master
>
> IIRC, used to not work, until Linus changed this at my request. Older
> GIT versions may cause some trouble here.
IIRC you did a p
Am 29. Dezember 2006, 21:57 Uhr (+0100) schrieb Han-Wen Nienhuys:
>
> no, the rule is that you have to end a #...scheme... expression with space
I see. It still might be useful to mention in the docs. I'm not sure
how many users easily distinguish between #...scheme... expressions
and music expre
Jan Nieuwenhuizen wrote:
Daniel Tonda Castillo <[EMAIL PROTECTED]> writes:
For the priority 3 files, the TRANSLATION document show these:
3 sponsor/
3 about/automated-engraving/
Then the whole directory is meant. We just found that something went
wrong with catogorisation of sponsor, a
Daniel Tonda Castillo <[EMAIL PROTECTED]> writes:
> For the priority 3 files, the TRANSLATION document show these:
>
> 3 sponsor/
> 3 about/automated-engraving/
> When there's a path without any file like in sponsor/ ¿which file is
> it referring to, the whole directory or the index.html file?
T
30 matches
Mail list logo
