On 2010/11/20 01:23:07, Keith wrote:
Misplaced underscore tag for translation?
Oops. Fixed, thanks.
On 2010/11/20 00:12:19, Graham Percival wrote:
I would rather wait another 23.5 hours, to give people in
all timezones (regardless of geographic location; I'm
living in Pacific Standard Time a
Graham Percival Saturday, November 20, 2010 12:44 AM
On Fri, Nov 19, 2010 at 08:55:26AM -0800, Mark Polesky wrote:
CG 4.3.6 says:
"Always put �...@item’ on its own line, and separate
consecutive items with a blank line."
In fact, we literally have thousands of cases:
$ git grep -c "^...@ite
Trevor Daniels wrote Saturday, November 20, 2010 8:29 AM
Graham Percival Saturday, November 20, 2010 12:44 AM
On Fri, Nov 19, 2010 at 08:55:26AM -0800, Mark Polesky wrote:
CG 4.3.6 says:
"Always put �...@item’ on its own line, and separate
consecutive items with a blank line."
In fact, we
LGTM
http://codereview.appspot.com/3199041/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Content looks fine. A few typographical comments.
http://codereview.appspot.com/2758042/diff/35001/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (left):
http://codereview.appspot.com/2758042/diff/35001/Documentation/notation/spacing.itely#oldcode793
Documentati
Hi everybody,
Correcting some typos in the usage manual, I just read in the section
about musicxml2ly:
"@item -l, --language=LANG
use a different language file 'LANG.ly' and corresponding pitch names,
e.g. 'deutsch' for deutsch.ly and German note names."
I wonder if this assertion is still va
On Sat, Nov 20, 2010 at 11:48:17AM +0100, Jean-Charles Malahieude wrote:
> Correcting some typos in the usage manual, I just read in the
> section about musicxml2ly:
>
> "@item -l, --language=LANG
> use a different language file 'LANG.ly' and corresponding pitch names,
> e.g. 'deutsch' for deutsch
Trevor Daniels wrote:
> ...I'd prefer a blank line before and after every @item
> including the first one...
+1
But only because I'm too lazy to fix the paragraph
formatting command in Vim (gqap), which turns this:
@item
line 1 here could join
line 2 here
into this:
@item line 1 here could joi
On Sat, Nov 20, 2010 at 10:56 AM, Mark Polesky wrote:
> Trevor Daniels wrote:
>> ...I'd prefer a blank line before and after every @item
>> including the first one...
>
> +1
>
> But only because I'm too lazy to fix the paragraph
> formatting command in Vim (gqap), which turns this:
>
> @item
> lin
Le 20/11/2010 19:18, Graham Percival disait :
On Sat, Nov 20, 2010 at 11:48:17AM +0100, Jean-Charles Malahieude wrote:
Correcting some typos in the usage manual, I just read in the
section about musicxml2ly:
"@item -l, --language=LANG
use a different language file 'LANG.ly' and corresponding p
This last patch set (#6) assumes this patch:
http://codereview.appspot.com/3199041/
I'm leaving most of the @item stuff as is.
We can always debate it more, but it doesn't
need to hold up this patch.
- Mark
http://codereview.appspot.com/2758042/diff/35001/Documentation/notation/spacing.itely
F
Patrick McCarty wrote:
> For this situation, I would arrow down to the second line
> and type `J' to join the lines.
>
> Or, if there is more than one line to join, and I have a
> specific `textwidth' setting, I would do a linewise
> highlight (with `V j j j' etc.) and type `gqap'. If the
> paragr
On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>
>> It's easy to test if it is currently valid. It's impossible to
>> say if it will ever be deprecated.
>>
>> I suggest you find a musicxml file and try converting it to
>> lilypond a few times, giving different -l values. If you do not
On 2010/11/19 07:41:46, Patrick McCarty wrote:
One question about the commit message: it mentions
"engravers-one-by-one.ly",
but there are no changes to this file in your patch. Should there be
changes?
This has been removed from the commit message.
Otherwise, looks good to me.
Thanks, p
On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
> On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>
>> instead of the newly formulation
>>
>> \language "lingua"
>>
>> unless there were some Arabic or makam music.xml file around...
>
> The \include "lingua.ly" syntax has not been dep
On Sat, Nov 20, 2010 at 08:29:35AM -, Trevor Daniels wrote:
>
> Graham Percival Saturday, November 20, 2010 12:44 AM
>
> >GDP only covered about 30% of the docs, and didn't strictly
> >enforce the doc policy even within those areas, that's not a good
> >reason to change the policy.
>
> +1.
On Sat, Nov 20, 2010 at 11:13:01AM -0800, Patrick McCarty wrote:
> On Sat, Nov 20, 2010 at 10:56 AM, Mark Polesky wrote:
> > But only because I'm too lazy to fix the paragraph
> > formatting command in Vim (gqap), which turns this:
> >
> > @item
> > line 1 here could join
> > line 2 here
> >
> > i
Le 20/11/2010 21:17, Graham Percival disait :
On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
instead of the newly formulation
\language "lingua"
unless there were some Arabic or makam music.xml file around...
The \include "l
LGTM
Carl
On 11/20/10 2:39 PM, "Jean-Charles Malahieude" wrote:
> Le 20/11/2010 21:17, Graham Percival disait :
>>
>> On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
>>> On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>>>
instead of the newly formulation
\lang
On Sat, Nov 20, 2010 at 9:39 PM, Jean-Charles Malahieude
wrote:
>
> Hoping this is the way you would like me to proceed.
Looks about right, but could we get a proper git commit (i.e. with
your name attached to it, and a commit message) ? I don't want to
steal credit for this bugfix.
Cheers,
- G
Le 20/11/2010 22:44, Graham Percival disait :
On Sat, Nov 20, 2010 at 9:39 PM, Jean-Charles Malahieude
wrote:
Hoping this is the way you would like me to proceed.
Looks about right, but could we get a proper git commit (i.e. with
your name attached to it, and a commit message) ? I don't wa
On 2010/11/20 19:34:44, Mark Polesky wrote:
CG says: NR, Installed Files, Snippets, IR.
Is that wrong?
Hhm. Seems like I mis-remembered where Installed Files goes. I'd argue
it's wrong though, if the order is based on easiest to hardest, or on
recommended order of reference - that's why I tho
Graham Percival wrote Saturday, November 20, 2010 8:40 PM
On Sat, Nov 20, 2010 at 08:29:35AM -, Trevor Daniels wrote:
Graham Percival Saturday, November 20, 2010 12:44 AM
>@itemize
>@item
>foo far
This is best, but I'd prefer a blank line before and after every
@item
including the firs
Patch set 7. We're down to nitpicks here...
I can't really think of a good way to break this up, except
into 2 commits, the 2nd being far larger than the first.
1) Organize paper-defaults-init.ly.
2) Doc: NR 4.1, 4.2: Reorganize, clarify details.
24 matches
Mail list logo
