default-next-staff-spacing question

2010-10-11 Thread Mark Polesky
When would I ever need to set default-next-staff-spacing? I can't think of a case where this property (as described in the docs) is ever needed, since I can always just set next-staff-spacing. Can someone explain? Thanks. - Mark ___

Re: default-next-staff-spacing question

2010-10-11 Thread Joe Neeman
Suppose you have an orchestral score with several staff groups and you set next-staff-spacing for the flute part. If there is a part where only the flute and strings play, then your next-staff-spacing will apply for the spacing between the flute part and the violin part. If you had set

macro missing for nl website

2010-10-11 Thread Graham Percival
Could somebody fix this? make website: ... Initializing settings for web site: [nl] ** Unknown command with braces `...@contactusabout' (in out-website/others-did.itexi l. 31) ... AFAIK all you need to do is copy the macro from the English docs and put it in the relevant place in the nl docs.

Rename vertical spacing dimensions. (issue2303044)

2010-10-11 Thread percival . music . ca
With regards to convert-ly, it would be nice to run it on the translations. But as long as the doc build still works, don't manually change anything in the translations. I'll be writing up policies for convert-ly later this evening or tomorrow. For the regtests, just go ahead and rename them.

Re: names of vertical spacing dimensions

2010-10-11 Thread Carl Sorensen
On 10/10/10 12:56 PM, Mark Polesky markpole...@yahoo.com wrote: Here's an updated patch set for review: http://codereview.appspot.com/2303044/ It's organized into 5 commits on my local branch: 1) Rename vertical spacing dimensions. 2) Update convert-ly (vertical spacing). 3) Run

convert: properly escape some single-backslashes. (issue2401042)

2010-10-11 Thread percival . music . ca
Reviewers: , Message: I noticed a few weird error messages while testing convert-ly on the docs. Description: convert: properly escape some single-backslashes. Please review this at http://codereview.appspot.com/2401042/ Affected files: M python/convertrules.py Index:

Re: convert: properly escape some single-backslashes. (issue2401042)

2010-10-11 Thread dak
http://codereview.appspot.com/2401042/diff/1/python/convertrules.py File python/convertrules.py (right): http://codereview.appspot.com/2401042/diff/1/python/convertrules.py#newcode2992 python/convertrules.py:2992: _ (\\RemoveEmpty*StaffContext - \*Staff \\RemoveEmptyStaves)) Any particular

Re: convert: properly escape some single-backslashes. (issue2401042)

2010-10-11 Thread dak
http://codereview.appspot.com/2401042/diff/1/python/convertrules.py File python/convertrules.py (right): http://codereview.appspot.com/2401042/diff/1/python/convertrules.py#newcode2992 python/convertrules.py:2992: _ (\\RemoveEmpty*StaffContext - \*Staff \\RemoveEmptyStaves)) Any particular

Re: [Patch] Request for addition to the publications list

2010-10-11 Thread Jean-Charles Malahieude
Le 10/10/2010 22:48, Valentin Villenave disait : On Sun, Oct 10, 2010 at 9:41 PM, Graham Percival wrote: Hmm. My first thought was that maybe it should go under Community-Publishing (since it was a developer who wrote it) Wow, look at that. And here I was, thinking I had written it myself.

Re: convert: properly escape some single-backslashes. (issue2401042)

2010-10-11 Thread percival . music . ca
On 2010/10/11 18:18:37, dak wrote: python/convertrules.py:2992: _ (\\RemoveEmpty*StaffContext - \*Staff \\RemoveEmptyStaves)) Any particular reason that \*Staff does not get the backslash doubled as well? The reason was that I didn't know what \* did -- I'm guessing it has a special meaning in

Re: [Patch] Request for addition to the publications list

2010-10-11 Thread Valentin Villenave
On Mon, Oct 11, 2010 at 9:57 PM, Jean-Charles Malahieude lily...@orange.fr wrote: Je te laisse le soin de traduire, sur la branche traduction, le fichier en question (à partir de la ligne 630). Merci, c'est fait. Valentin ___ lilypond-devel mailing

Re: macro missing for nl website

2010-10-11 Thread Francisco Vila
2010/10/11 Graham Percival gra...@percival-music.ca: Could somebody fix this?  make website: ... Initializing settings for web site: [nl] ** Unknown command with braces `...@contactusabout' (in out-website/others-did.itexi l. 31) ... AFAIK all you need to do is copy the macro from the

Re: names of vertical spacing dimensions

2010-10-11 Thread Graham Percival
On Mon, Oct 11, 2010 at 6:29 PM, Carl Sorensen c_soren...@byu.edu wrote: On 10/10/10 12:56 PM, Mark Polesky markpole...@yahoo.com wrote: ...but Rietveld meshed them all into one.  So, once approved, I'll push it as a set of patches, not just one. Why not push it as one patch?  It seems like

Compile failure with commit edd89894

2010-10-11 Thread Patrick McCarty
Hi Graham, With GCC 4.5.1, I'm seeing a compile failure with latest git. Reverting your commit edd89894 fixes it. Here's the error: context-def.cc: In static member function 'static scm_unused_struct* Context_def::mark_smob(scm_unused_struct*)': context-def.cc:118:1: error: expected 'while'

Re: Compile failure with commit edd89894

2010-10-11 Thread Graham Percival
On Tue, Oct 12, 2010 at 2:30 AM, Patrick McCarty pnor...@gmail.com wrote: With GCC 4.5.1, I'm seeing a compile failure with latest git. Reverting your commit edd89894 fixes it.  Here's the error: context-def.cc: In static member function 'static scm_unused_struct*

Re: Compile failure with commit edd89894

2010-10-11 Thread Patrick McCarty
On Mon, Oct 11, 2010 at 6:54 PM, Graham Percival gra...@percival-music.ca wrote: On Tue, Oct 12, 2010 at 2:30 AM, Patrick McCarty pnor...@gmail.com wrote: With GCC 4.5.1, I'm seeing a compile failure with latest git. Reverting your commit edd89894 fixes it.  Here's the error: context-def.cc:

Re: Compile failure with commit edd89894

2010-10-11 Thread Graham Percival
On Mon, Oct 11, 2010 at 06:59:32PM -0700, Patrick McCarty wrote: On Mon, Oct 11, 2010 at 6:54 PM, Graham Percival gra...@percival-music.ca wrote: On Tue, Oct 12, 2010 at 2:30 AM, Patrick McCarty pnor...@gmail.com wrote: With GCC 4.5.1, I'm seeing a compile failure with latest git.