Docs: new spacing era

2010-11-14 Thread Jean-Charles Malahieude

Hi Mark,

On my silent and long way to translate spacing.itely, I just got very 
confused by this paragraph (line 1730 - StaffGrouper's props):



@item staff-staff-spacing
The distance between consecutive staves within the current
staff-group.  The @code{staff-staff-spacing} property of an
individual staff's @code{VerticalAxisGroup} grob will be used
instead for any staves in the staff-group that have it set.  If
both @code{staff-staff-spacing} and @code{staff-staff-spacing}
are unset, the @code{default-staff-staff-spacing} property of each
staff's @code{VerticalAxisGroup} grob is used.


Do you mean that It is the @code{default-staff-staff-spacing} property
of each staff's @code{VerticalAxisGroup} grob that will be used when
@code{staff-staff-spacing} is defined neither in @code{StaffGrouper}
nor @code{VerticalAxisGroup}?

TIA,
Jean-Charles

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Docs: new spacing era

2010-11-14 Thread Jean-Charles Malahieude

Le 14/11/2010 17:17, Mark Polesky disait :


Jean-Charles Malahieude wrote:

Do you mean that It is the
@code{default-staff-staff-spacing} property of each
staff's @code{VerticalAxisGroup} grob that will be used
when @code{staff-staff-spacing} is defined neither in
@code{StaffGrouper} nor @code{VerticalAxisGroup}?


Yes.  However, there are still some changes coming to this
file.  I probably should have warned the translators.  See
http://codereview.appspot.com/3089042/.  This particular
oddity was a by-product of the renaming convertrule.  It is
addressed in the Rietveld post.  I'll probably make Trevor's
suggestion and then push that patch today.



So, just a collateral victim.
OK. I just have to pull and carry over these adjustments...
I've not jumped deep into this (r)evolution; it was just this double 
instance both staff-staff-spacing and staff-staff-spacing that made 
happen the tilt.



The other big adjustments to spacing.itely will be coming
from some version of this post
http://codereview.appspot.com/2758042/.  But I'm not
finished with that one either.

Sometimes I feel bad for the translators when I make these
huge changes all at once  But it's really a weird (and
neat) feeling to have my words reach people across
languages.  I really appreciate all the work you've done and
are doing!



Too bad for me to have attacked spacing before input... I shall wait 
before opening vocal!



Feel free to let me know if I have any annoying stylistic
idiosyncracies; sometimes I wonder if I overuse the
semi-colon, for example.  (:

- Mark


As long as I make the point, I don't mind. Rephrasing is fully part of 
the translation process!


And many thanks for this brainstorming that, in my very small opinion, 
might help even non English speaking users.


Cheers,
Jean-Charles

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond