Re: Doc: NR 1.2.3 Expl. manual accidentals + cadenzas (issue 5976056)

[pkx166h]

On 2012/04/29 09:18:28, Trevor Daniels wrote:

LGTM, apart from the deleted index entries



http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely

File Documentation/notation/rhythms.itely (right):



http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1415

Documentation/notation/rhythms.itely:1415: @cindex beams, unmetered

music

The change you've made was not the one I wanted.  There are already

several

adjacent entries in the index from 'cadenza' and 'unmetered', but now

there are

none from 'bar lines' and 'bar numbers'.  There should be.  If you

don't like

'turning off', how about simply
@cindex bar lines, cadenzas
@cindex bar numbers, cadenzas
ditto for unmetered music
to go with the ones for beams and accidentals?


Sounds good. Thanks.

http://codereview.appspot.com/5976056/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Adding Bar Line types

[James]

Hello,

On 1 May 2012 22:06, Thomas Morley  wrote:
...
>
> Hi James,
>
> together with Marc I'm working on a completely new approach to
> barlines, making available custom-barlines of all kind.
> If success (not sure) it would be a major change to lilypond.
> Currently there are several minor and major issues in the code, so I
> don't want to post it.
> But I attach a png what might be possible.

That looks great. Also my ignorance is showing here as Nicolas'
custom-bar file is all in Scheme and not an engraver which is what I
assume is required/preferred in the main code.

However I think it would be useful in our snippets doc at least for
2.15.38 (if there is one) onwards until you have you new code worked
out. While it won't compile on the LSR I believe that we can still add
it as a snippet for our Doc?

If Nicolas (as it is his work) and the dev team agree I can make that
happen with a patch.

James

PS. for those Devs not on the user list:

--snip--

On 17 April 2012 00:17, Nick Payne  wrote:
>
> Here's scheme code (can't remember who I got it from) for creating a dashed
> double bar line - I needed it for a Fine occurring in the middle of a
> measure:

Hi,

Someone asked exactly the same question on the French users mailing
list today.  Here is an approximate translation of Nicolas Sceaux'
answer, that might interest you:

 By using this library file:
 https://github.com/nsceaux/nenuvar/blob/master/common/custom-bars.ily
 one can introduce a dashed double bar line with  \bar ";;"
 See the example file test-custom-bars.ily in the same directory.

--snip--

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

[pkx166h]

Reviewers: Graham Percival,


http://codereview.appspot.com/6137050/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

http://codereview.appspot.com/6137050/diff/1/Documentation/notation/input.itely#newcode1050
Documentation/notation/input.itely:1050: footnote is being attached but
can also be attached as a
On 2012/04/30 07:39:21, Graham Percival wrote:

isn't a textscript also a grob?  if so, you don't need to add that in

the text.

The example carries that story.


Possibly, I don't actually know the technical difference, I was
following the examples I did previously (if you scan down to the start
of the 'manual' footnotes and the 'chorded' notes I've just tried tied
to be consistent and that is what I used there. That was based on
comments by Mike (and possibly David when he made his changes), so if
TextScript and Grob are interchangeable I should make the changes
throughout the @nodes than just here.

If someone can let me know?

Description:
Doc: NR clarified \footnote command as a TextScript

While chorded notes *require* the \footnote command attached
as a TextScript, normal notes can _also_ be attached like that.

The original description stated the command *must* come before
single notes.

Please review this at http://codereview.appspot.com/6137050/

Affected files:
  M Documentation/notation/input.itely


Index: Documentation/notation/input.itely
diff --git a/Documentation/notation/input.itely  
b/Documentation/notation/input.itely
index  
9294d5cd0838826481f4dd87fd5f90783cc0d074..c93a1cad8333f081d6b4037ad944a7db6f049abc  
100644

--- a/Documentation/notation/input.itely
+++ b/Documentation/notation/input.itely
@@ -1046,8 +1046,9 @@ annotated, the @samp{(x . y)} position of the  
indicator and a

 @code{\markup} that will appear in the footnote at the bottom of the
 page.

-The command @code{\footnote} must come @emph{before} the grob that the
-footnote is being attached to:
+The command @code{\footnote} comes @emph{before} the grob that the
+footnote is being attached but can also be attached as a
+@code{TextScript}:

 @lilypond[verbatim,quote,ragged-right,papersize=a8]
 \book {
@@ -1058,7 +1059,9 @@ footnote is being attached to:
 a'4 b8
 \footnote #'(0.5 . 1) #'NoteHead
   \markup { The third note }
-e c4 d4
+e c4
+d4-\footnote #'(-0.5 . 2) #'NoteHead
+ \markup { The last note }
   }
 }
 @end lilypond



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCH: Countdown to 20120503

[Colin Campbell]

For 20:00 MDT Thursday May 3

Issue 2487 : 
LyX integration of lilypond - R6132052 




Cheers,
Colin

--
I've learned that you shouldn't go through life with a catcher's mitt on both 
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: tuplet number placement and ornament

[James]

Hello,

On 1 May 2012 08:52, James  wrote:
> Hello,
>
> On 1 May 2012 08:31, Nick Payne  wrote:
>> On 01/05/12 17:06, James wrote:
>>>
>>> Hello,
>>>
>>> On 1 May 2012 06:12, Nick Payne  wrote:

 On 01/05/12 14:32, Werner LEMBERG wrote:

 In the following, even though I've turned off the tuplet bracket
 stencil, the tuplet number is still placed as though the stencil
 was there:
>>
>> [...] I want the number there, but not have it displaced upwards as
>> if the bracket was still there and avoiding the mordent.  I found
>> subsequent to my previous message that I can achieve this by using
>> \override TupletBracket #'avoid-scripts = ##f.
>
> This should be documented (in case it isn't yet).

http://lilypond.org/doc/v2.15/Documentation/internals-big-page#tupletbracket

It is documented after all.

:/

I missed it too.

james

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add announcements to the upper right corner of the website (issue 6068045)

[Jan Nieuwenhuizen]

Graham Percival writes:

> On Fri, Apr 27, 2012 at 10:18:23AM -0300, Han-Wen Nienhuys wrote:
>> On Fri, Apr 27, 2012 at 10:15 AM, Han-Wen Nienhuys  wrote:
>> > Who is GNU_LilyPond anyway?  I thought it was, but I might be mistaken.
>> 
>> I mean: I thought it was Jan.
>
> yeah, it's Jan.

yes, /currently/ it's me, but as you can see, it could do with some love

Jan

-- 
Jan Nieuwenhuizen  | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Build: Fix the misc-file wildcard in website.make (issue 2499). (issue 6136057)

[graham]

LGTM, please push directly to staging

http://codereview.appspot.com/6136057/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: tuplet number placement and ornament

[Nick Payne]

On 01/05/12 17:06, James wrote:

Hello,

On 1 May 2012 06:12, Nick Payne  wrote:

On 01/05/12 14:32, Werner LEMBERG wrote:

In the following, even though I've turned off the tuplet bracket
stencil, the tuplet number is still placed as though the stencil
was there:

[...] I want the number there, but not have it displaced upwards as
if the bracket was still there and avoiding the mordent.  I found
subsequent to my previous message that I can achieve this by using
\override TupletBracket #'avoid-scripts = ##f.

This should be documented (in case it isn't yet).


Other than the avoid-scripts property appearing in the Internals ref,
"TupletBracket #'avoid-scripts" doesn't appear to be documented.

So what you're saying is apart from the 'avoid-scripts' property being
documented [in the IR] it isn't documented?

Is that what you meant, otherwise you'll need to elaborate.


Yes, that's what I mean. Searching the documentation for "TupletBracket 
#'avoid-scripts" doesn't find anything.



There is a
bug for tuplet number placement -
https://code.google.com/p/lilypond/issues/detail?id=2397. It's marked as
fixed, but it seems to me that there is still a bug there if collision
avoidance for a TupletBracket is still being performed when the
TupletBracket stencil has been turned off.


Can't comment on that, Mike Solomon made the patch for this, maybe he can.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: tuplet number placement and ornament

[James]

Hello,

On 1 May 2012 08:31, Nick Payne  wrote:
> On 01/05/12 17:06, James wrote:
>>
>> Hello,
>>
>> On 1 May 2012 06:12, Nick Payne  wrote:
>>>
>>> On 01/05/12 14:32, Werner LEMBERG wrote:
>>>
>>> In the following, even though I've turned off the tuplet bracket
>>> stencil, the tuplet number is still placed as though the stencil
>>> was there:
>
> [...] I want the number there, but not have it displaced upwards as
> if the bracket was still there and avoiding the mordent.  I found
> subsequent to my previous message that I can achieve this by using
> \override TupletBracket #'avoid-scripts = ##f.

 This should be documented (in case it isn't yet).
>>>
>>>
>>> Other than the avoid-scripts property appearing in the Internals ref,
>>> "TupletBracket #'avoid-scripts" doesn't appear to be documented.
>>
>> So what you're saying is apart from the 'avoid-scripts' property being
>> documented [in the IR] it isn't documented?
>>
>> Is that what you meant, otherwise you'll need to elaborate.
>
>
> Yes, that's what I mean. Searching the documentation for "TupletBracket
> #'avoid-scripts" doesn't find anything.

Thanks

http://code.google.com/p/lilypond/issues/detail?id=2508

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyPon's feta-braces font license

[Khaled Hosny]

On Tue, May 01, 2012 at 06:30:43AM +0200, Werner LEMBERG wrote:
> 
> >> I don't mind relicensing the font under a more permissible license.
> >> Werner, do you know of a suitable license for open source fonts?
> > 
> > Dual (multi) licensing is also possible: GNU GPL Font Exc. + OFL ?
> 
> Yes, dual-licensing with OFL sounds like the best solution.

Thanks all for your responses. I agree with Werner, dual licensing is
the beast solution.

Regards,
 Khaled

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: tuplet number placement and ornament

[James]

Hello,

On 1 May 2012 06:12, Nick Payne  wrote:
> On 01/05/12 14:32, Werner LEMBERG wrote:
>
> In the following, even though I've turned off the tuplet bracket
> stencil, the tuplet number is still placed as though the stencil
> was there:
>>>
>>> [...] I want the number there, but not have it displaced upwards as
>>> if the bracket was still there and avoiding the mordent.  I found
>>> subsequent to my previous message that I can achieve this by using
>>> \override TupletBracket #'avoid-scripts = ##f.
>>
>> This should be documented (in case it isn't yet).
>
>
> Other than the avoid-scripts property appearing in the Internals ref,
> "TupletBracket #'avoid-scripts" doesn't appear to be documented.

So what you're saying is apart from the 'avoid-scripts' property being
documented [in the IR] it isn't documented?

Is that what you meant, otherwise you'll need to elaborate.

> There is a
> bug for tuplet number placement -
> https://code.google.com/p/lilypond/issues/detail?id=2397. It's marked as
> fixed, but it seems to me that there is still a bug there if collision
> avoidance for a TupletBracket is still being performed when the
> TupletBracket stencil has been turned off.
>

Can't comment on that, Mike Solomon made the patch for this, maybe he can.

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel