Re: Web: fix dead links and redirects on Productions page (issue 283990043 by gre...@fastmail.co.uk)

2015-12-27 Thread gregrs 

Updated link for 100-minute version of Wagner's Ring.


https://codereview.appspot.com/283990043/diff/1/Documentation/web/introduction.itexi
File Documentation/web/introduction.itexi (right):

https://codereview.appspot.com/283990043/diff/1/Documentation/web/introduction.itexi#newcode623
Documentation/web/introduction.itexi:623: Wagner to a 100-minute version
for children.
On 2015/12/27 09:51:11, pkx166h wrote:

There is still a link that might be helpful.



http://www.rsb-online.de/content/concerts/new-season-1516/family-concerts-age-7-and-above/index_eng.html

Thanks. Patch uploaded.

https://codereview.appspot.com/283990043/

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

Re: 2.19.31 Notation Reference glitch

2015-12-27 Thread Phil Holmes 
- Original Message - 
From: "James Lowe" 

To: "David Kastrup" ; "Menu Jacques" 
Cc: 
Sent: Sunday, December 27, 2015 10:07 AM
Subject: Re: 2.19.31 Notation Reference glitch



On 27/12/15 09:37, David Kastrup wrote:

Menu Jacques  writes:


Hello folks,

Just for your information: at page 715, «  π ≈ » is not displayed in:



from markup-commands.tely:

Make a fraction of two markups.
@lilypond[verbatim,quote]
\markup {
  π ≈
  \fraction 355 113
}
@end lilypond

The Info file shows:

‘\fraction’ ARG1 (markup) ARG2 (markup)

 Make a fraction of two markups.
  \markup {
π ≈
\fraction 355 113
  }

[proper image elided]

and the HTML at page

looks fine as well.  So this would appear to be a problem with
texinfo.tex regarding its UTF-8 support.

Should we be using a different example then - just for the sake of 
clarity?


(If so can someone suggest something?)

--
James



FWIW, it's been like that since before 2.13 (the earliest NR I have on my 
system).


Simplest might simply be to write Pi instead of the Greek letter?

--
Phil Holmes 



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

Re: 2.19.31 Notation Reference glitch

2015-12-27 Thread David Kastrup 
James Lowe  writes:

> On 27/12/15 09:37, David Kastrup wrote:
>> Menu Jacques  writes:
>>
>>> Hello folks,
>>>
>>> Just for your information: at page 715, «  π ≈ » is not displayed in:
>>>
>>>
>>>
>>> from markup-commands.tely:
>>>
>>> Make a fraction of two markups.
>>> @lilypond[verbatim,quote]
>>> \markup {
>>>   π ≈
>>>   \fraction 355 113
>>> }
>>> @end lilypond
>> The Info file shows:
>>
>> ‘\fraction’ ARG1 (markup) ARG2 (markup)
>>
>>  Make a fraction of two markups.
>>   \markup {
>> π ≈
>> \fraction 355 113
>>   }
>>
>> [proper image elided]
>>
>> and the HTML at page
>> 
>> looks fine as well.  So this would appear to be a problem with
>> texinfo.tex regarding its UTF-8 support.
>>
> Should we be using a different example then - just for the sake of clarity?

That would be one option.

I think the easier option would be to update our version of texinfo.tex
again.  The current version supports both characters.

-- 
David Kastrup

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

2.19.31 Notation Reference glitch

2015-12-27 Thread Menu Jacques 
Hello folks,

Just for your information: at page 715, «  π ≈ » is not displayed in:



from markup-commands.tely:

Make a fraction of two markups.
@lilypond[verbatim,quote]
\markup {
  π ≈
  \fraction 355 113
}
@end lilypond


JM

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

Re: 2.19.31 Notation Reference glitch

2015-12-27 Thread David Kastrup 
Menu Jacques  writes:

> Hello folks,
>
> Just for your information: at page 715, «  π ≈ » is not displayed in:
>
>
>
> from markup-commands.tely:
>
> Make a fraction of two markups.
> @lilypond[verbatim,quote]
> \markup {
>   π ≈
>   \fraction 355 113
> }
> @end lilypond

The Info file shows:

‘\fraction’ ARG1 (markup) ARG2 (markup)

 Make a fraction of two markups.
  \markup {
π ≈
\fraction 355 113
  }

[proper image elided]

and the HTML at page

looks fine as well.  So this would appear to be a problem with
texinfo.tex regarding its UTF-8 support.

-- 
David Kastrup

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

Re: Improve note-by-number to deal better with flag-styles (issue 284000043 by thomasmorle...@gmail.com)

2015-12-27 Thread thomasmorley65 

please review

https://codereview.appspot.com/28443/

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

Re: Improve note-by-number to deal better with flag-styles (issue 284000043 by thomasmorle...@gmail.com)

2015-12-27 Thread thomasmorley65 

On 2015/12/27 22:22:56, simon.albrecht wrote:

LGTM, except for one doc nitpick.



https://codereview.appspot.com/28443/diff/20001/scm/define-markup-commands.scm

File scm/define-markup-commands.scm (right):



https://codereview.appspot.com/28443/diff/20001/scm/define-markup-commands.scm#newcode3547

scm/define-markup-commands.scm:3547: mensural-style-flags.  All

note-heads

@code{flag-style} may be overridden.
This should be
All note-heads’ @code{flag-style} …
or perhaps rather
@code{flag-style} may be overridden independently.


done

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

Re: 2.19.31 Notation Reference glitch

2015-12-27 Thread Knut Petersen 

Am 27.12.2015 um 12:29 schrieb David Kastrup:
I think the easier option would be to update our version of texinfo.tex again. The current version supports both characters. 


A full build with texinfo.tex version 2015-12-20.12 succeeded and cured the 
problem.

cu,
 Knut




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

Re: 2.19.31 Notation Reference glitch

2015-12-27 Thread David Kastrup 
Knut Petersen  writes:

> Am 27.12.2015 um 12:29 schrieb David Kastrup:
>> I think the easier option would be to update our version of
>> texinfo.tex again. The current version supports both characters. 
>
> A full build with texinfo.tex version 2015-12-20.12 succeeded and
> cured the problem.

I'm currently doing a build of my own.  It does not appear like any of
the *.txi files have changed since last time.  And texinfo.tex has
gained a few rather interesting index sorting options.  I have no idea
what kind of makeinfo support is required for that to work with other
backends, however.

-- 
David Kastrup

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