I only checked the keyboards part that I helped with, but I like the
improvements. Thanks!
On Fri, May 21, 2010 at 7:04 PM, Mark Polesky wrote:
> Warning. This is a monstrously huge patch, with an
> potentially overwhelming number of (mostly) tiny changes.
>
> However, I think it's a worthwhile
Warning. This is a monstrously huge patch, with an
potentially overwhelming number of (mostly) tiny changes.
However, I think it's a worthwhile improvement to the text;
one that makes the NR a lot more readable, and fixes a lot
of sloppy code.
I'm hoping that some of the usual players will at le
Le 21/05/2010 16:51, Francisco Vila disait :
2010/5/21 Graham Percival:
On Fri, May 21, 2010 at 1:11 PM, Francisco
Vila wrote:
2010/5/21 Graham Percival:
There's an automatic tool to fill in menus if there's a @menu
@end menu see the CG for details. "scripts to aid doc work" or
something li
Graham Percival wrote:
>> Can the @menu be simply 'Using the spanner-interface',
>> ditto @unnumberedsubsubsec (sans Tex markups)?
>
> It must be exactly the same as the @node name, which
> cannot have things like @code in it.
Yes and no. It must have exactly the same as the @node
name, but there
On Fri, May 21, 2010 at 09:37:28AM -0700, Mark Polesky wrote:
> Graham Percival wrote:
> > If somebody wants to work on making unfinished doc
> > sections match our doc policy (such as NR 2.1 Vocals, or
> > anything in NR 3 or higher), let's talk.
>
> I will be posting a patch soon to reformat the
Graham Percival wrote:
> If somebody wants to work on making unfinished doc
> sections match our doc policy (such as NR 2.1 Vocals, or
> anything in NR 3 or higher), let's talk.
I will be posting a patch soon to reformat the ly code in
the NR, along the same lines as this patch that did the same
t
On Fri, May 21, 2010 at 3:51 PM, Francisco Vila wrote:
> 2010/5/21 Graham Percival :
>> However, in some cases this
>> *will* change the html splitting in a way that isn't appropriate.
>
> My understanding (you know where does it come from :-) is that only
> numbered sections produce splitting. So
2010/5/21 Graham Percival :
> On Fri, May 21, 2010 at 1:11 PM, Francisco Vila wrote:
>> 2010/5/21 Graham Percival :
>>> There's an automatic tool to fill in menus if there's a
>>> @menu
>>> @end menu
>>> see the CG for details. "scripts to aid doc work" or something like that.
>>
>> I've tried it
Hello,
Graham Percival wrote:
I think the "always add explicit {} apart from ones that would
surround an entire example" might the best way to go; if we
encounter any more exceptions to the "always use them" rule, we
can add them later.
This guideline has been added to the CG.
James
__
On Fri, May 21, 2010 at 1:43 PM, James Lowe wrote:
> Graham,
>
> Graham Percival wrote:
>> I don't see the point in trying a piecemeal approach to the doc
>> sections which have never tried to be rewritten to follow the doc
>> policy.
>
> As far as I can tell, I have this task still to do
> http:/
On Fri, May 21, 2010 at 1:11 PM, Francisco Vila wrote:
> 2010/5/21 Graham Percival :
>> There's an automatic tool to fill in menus if there's a
>> @menu
>> @end menu
>> see the CG for details. "scripts to aid doc work" or something like that.
>
> I've tried it and doesn't work, menu is not filled
Graham,
Graham Percival wrote:
On Fri, May 21, 2010 at 12:15 PM, James Lowe wrote:
Once I resolve this and if anyone spots others I can then start to resolve
them as they get flagged.
I don't see the point in trying a piecemeal approach to the doc
sections which have never tried to be re
2010/5/21 Graham Percival :
> There's an automatic tool to fill in menus if there's a
> @menu
> @end menu
> see the CG for details. "scripts to aid doc work" or something like that.
I've tried it and doesn't work, menu is not filled with
@unnumberedsubsubsec names. Probably only @nodes are taken
On Fri, May 21, 2010 at 12:15 PM, James Lowe wrote:
>
> I can try to fix this. I'll have a go anyway - however can anyone tell me if
> it matters to the code if the @menu item has to be *exactly* the same as the
> @node (which is also missing I notice) and the @unnumberedsubsubsec.
It must be exa
2010/5/21 James Lowe :
> I can try to fix this. I'll have a go anyway - however can anyone tell me if
> it matters to the code if the @menu item has to be *exactly* the same as the
> @node (which is also missing I notice) and the @unnumberedsubsubsec.
I think texinfo, makeinfo and others will comp
Hello,
Francisco Vila wrote:
2010/5/20 Mark Polesky :
At the very top right of
http://lilypond.org/doc/v2.13/Documentation/notation/spanners
The "next" link for "Using the spanner-interface" is broken.
I assume there are other cases, too?
I think this is caused by lack of @menu in the Spanne
16 matches
Mail list logo
