Adam,
On 30 January 2013 00:22, Adam Spiers wrote:
> Whilst the procedure of marking an issue as fixed, with an additional
> Fixed_mm_MM_ss label, is briefly mentioned at the end of the "Issue
> classification section" in the Contributor's Guide:
>
>
> http://lilypond.org/doc/v2.17/Documentation
David Kastrup writes:
> Adam Spiers writes:
>
>> http://lilypond.org/doc/v2.17/Documentation/contributor/patch-handling
>>
>> does not match with the CG source:
>>
>> http://git.savannah.gnu.org/cgit/lilypond.git/tree/Documentation/contributor/issues.itexi#n824
>>
>> The source code has four @su
Adam Spiers writes:
> http://lilypond.org/doc/v2.17/Documentation/contributor/patch-handling
>
> does not match with the CG source:
>
> http://git.savannah.gnu.org/cgit/lilypond.git/tree/Documentation/contributor/issues.itexi#n824
>
> The source code has four @subheadings, but none of them are vi
Whilst the procedure of marking an issue as fixed, with an additional
Fixed_mm_MM_ss label, is briefly mentioned at the end of the "Issue
classification section" in the Contributor's Guide:
http://lilypond.org/doc/v2.17/Documentation/contributor/issue-classification
it is slightly misleading,
http://lilypond.org/doc/v2.17/Documentation/contributor/patch-handling
does not match with the CG source:
http://git.savannah.gnu.org/cgit/lilypond.git/tree/Documentation/contributor/issues.itexi#n824
The source code has four @subheadings, but none of them are visible
online. Additionally the "
On Thu, Jan 17, 2013 at 7:04 AM, Fan Ziye wrote:
> Dear Mike,
>
> Thank you for your rapid reply! It’s very useful for me. I will continue
> reading the CG and then go to the issue list.
http://lilypond.org/help-us.html is also worth reading for starting
points. Thanks very much for the offer of
On 2013/01/29 17:25:19, Keith wrote:
I tried to write simpler texts, below. If you are dissatisfied you >
can use them as inspiration.
I like this evident wording.
https://codereview.appspot.com/7220052/
___
lilypond-devel mailing list
lilypond-de
If you consider that description better than the original,
you might want to look over the entries in learning and
notation. The original entries for \times very much
focused on explaining things in a way and order that
makes the "fraction order" choice appear less strange.
Those looked fine.
I
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 29, 2013 4:13 PM
Subject: Re: Make doc; create-weblinks and translations
"Phil Holmes" writes:
As for getting rid of unmaintained output - I agree on balance. It
would be interesting to be told which languages
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Tuesday, January 29, 2013 3:56 PM
> Subject: Re: Make doc; create-weblinks and translations
>
>
>> "Phil Holmes" writes:
>
>> I noticed that a lot of half-translated Czech pages contain a lot of
>> stuf
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 29, 2013 3:56 PM
Subject: Re: Make doc; create-weblinks and translations
"Phil Holmes" writes:
I noticed that a lot of half-translated Czech pages contain a lot of
stuff from the _German_ translation. Now I do
"Phil Holmes" writes:
> 1. No Czech translations means lots of error messages (which could
> obscure ones
> we actually want to see, in order to correct them).
> I plan to create a patch that will:
>
> a) Restore the -cs pages to use -en (default) "translations" thus
> getting rid of
> the error
I note that 'make doc -s' is again producing large quantities of output.
The
majority of this appears to come from Julien's fix to throw an error from
create-weblinks-itexi.py when a desired translation is not found.
See http://code.google.com/p/lilypond/issues/detail?id=2899
When this was firs
On 2013/01/28 22:18:57, benko.pal wrote:
bwwtolilly is a typo, isn't it?
(diff view doesn't work for some reason.)
Typo fixed as
commit 1b15a2096770f0393c799097afa4a2dcf28ed213
Author: David Kastrup
Date: Tue Jan 29 15:01:05 2013 +0100
Typo bwwtolilly -> bwwtolily
https://codereview.a
Reviewers: Keith,
Message:
On 2013/01/29 04:47:13, Keith wrote:
Looks great.
You can simplify the version in changes. The two tuplets sharing
share one beam
catches the eye, but that was not the change.
Right. This was a cut&paste job from the notation manual where the
intent was to _al
15 matches
Mail list logo