Dear Han-Wen,
2008/4/23 Han-Wen Nienhuys :
> The reference point is the center of the stem, and the flag attaches
> to the right side of the stem.
Thanks for the info.
I think that would be the case if the flags would not have a piece of
a stem themselves. However, the flags (1/16 ->) have a
No, @lsr{} is completely distinct from @lilypondfile. @lsr{}
would create a link to a specific snippet; it would be used in the
@seealso
Snippets: @lsr{}
section.
Cheers,
- Graham
On Thu, 24 Apr 2008 08:19:13 +0300
Till Rettig <[EMAIL PROTECTED]> wrote:
> I'm fine with this -- the @lilypondfi
I'm fine with this -- the @lilypondfile is a much more powerful feature
that does almost the same.
Till
Graham Percival schrieb:
Does anybody really want to keep @lsr{} (in addition to
@lsrdir{})? It isn't used in any finished GDP sections, and I'm
90% certain it isn't worth keeping.
@lsrdir
John Mandereau schrieb:
Marcos di Silva wrote:
John Mandereau,
I'm finishing translating Lilypond program messages to pt_BR. I missed
some messages like "syntax error, unexpected %s" [parser.cc] in .pot
file: http://translationproject.org/POT-files/lilypond-2.11.39.pot
How do I translate t
Does anybody really want to keep @lsr{} (in addition to
@lsrdir{})? It isn't used in any finished GDP sections, and I'm
90% certain it isn't worth keeping.
@lsrdir{Pitches, Pitches} points to the whole collection of pitch
snippets.
@lsr{pitches, adding-ambitus-per-voice.ly, Ambitus} (or somethi
/home/lilypond/lilypond/stepmake/stepmake/podir-targets.make:14:
warning: ignoring old commands for target `po-update'
make[5]: Nothing to be done for `messages'.
make[5]: Leaving directory
`/home/lilypond/lilypond/Documentation/po'
/usr/bin/python ../../../buildscripts/texi-gettext.py fr
out-www/l
Marcos di Silva wrote:
> John Mandereau,
>
> I'm finishing translating Lilypond program messages to pt_BR. I missed
> some messages like "syntax error, unexpected %s" [parser.cc] in .pot
> file: http://translationproject.org/POT-files/lilypond-2.11.39.pot
> How do I translate them?
These messages
2008/4/22 Risto Vääräniemi <[EMAIL PROTECTED]>:
> Dear all,
>
> I noticed that the flags in flagged notes created with \note command
> (or \note-by-number) are not positioned properly. The flag grob is
> attached to the right side of the stem and because the flags already
> have a piece of stem
2008/4/23 Valentin Villenave <[EMAIL PROTECTED]>:
> Risto, I have applied you patch. I think it was OK, though I don't
> really understand why stem-thickness was divided by 2 in the first
> place.
The reference point is the center of the stem, and the flag attaches
to the right side of the stem
2008/4/23 Valentin Villenave <[EMAIL PROTECTED]>:
> 2008/4/23 Risto Vääräniemi <[EMAIL PROTECTED]>:
>
>
> > I hope I did it right. Could someone have a look at the patch and
> > possibly commit it to the git if it's OK?
>
> Risto, I have applied you patch. I think it was OK, though I don't
>
Hi Valentin,
2008/4/23 Valentin Villenave :
> Risto, I have applied you patch. I think it was OK, though I don't
> really understand why stem-thickness was divided by 2 in the first
> place.
>
> If anyone finds a good reason, please revert commit
> e646872695248ec7e8eaa9d513a5695d128f
2008/4/23 Risto Vääräniemi <[EMAIL PROTECTED]>:
> I hope I did it right. Could someone have a look at the patch and
> possibly commit it to the git if it's OK?
Risto, I have applied you patch. I think it was OK, though I don't
really understand why stem-thickness was divided by 2 in the first
p
Hi,
I now got the git up and running and made the suggested change to the
freshly retrieved file.
I tried to follow the instructions on the LP home page:
git commit -a
git-format-patch HEAD^
I hope I did it right. Could someone have a look at the patch and
possibly commit it to the git if it's O
13 matches
Mail list logo
