On Sat, 2008-10-25 at 18:41 -0400, Trevor Bača wrote:
> 2008/10/24 Valentin Villenave <[EMAIL PROTECTED]>
> 2008/10/24 Trevor Bača <[EMAIL PROTECTED]>:
>
> > If we're keeping track (informally) of user requests for
> certain features,
> > you can add my name
Hello,
I don't know if this is a bug, so I'm posting to -devel.
In this example, are the beams supposed to be closer to the noteheads
on beats one and three? I like the look of the beam's position for
beat two.
%% Begin
\version "2.11.63"
\relative c' {
c16 g' c r
d,16 a' d r
e,16 b' e r
Ok, I put a merge of the two versions on the wiki at
http://lilypondwiki.tuxfamily.org/index.php?title=German_Release_Text_2.12
I guess formatting will be done whithin the html page, so I didn't pay much
attention to that.
Greetings
Till
Original-Nachricht
> Datum: Tue, 28 Oc
These kind of aspects can seldomly be regarded as bugs, but the
intention in LilyPond is
to provide as beatiful results as possible in as many cases as possible.
If you look at the
regression tests for LilyPond at
http://lilypond.org/doc/v2.11/input/regression/collated-files
and search for test
I have just created a new snippet that should be put into the LSR for
version 2.12, but it won't run under version 2.10.
What do I do to get this into LilyPond somehow? It's a snippet that ought
to go into the docs under selected snippets for fretted strings.
Thanks,
Carl
___
Hi Carl,
2008/10/29 Carl D. Sorensen <[EMAIL PROTECTED]>:
> I have just created a new snippet that should be put into the LSR for
> version 2.12, but it won't run under version 2.10.
Add it to input/new.
Regards,
Neil
___
lilypond-devel mailing list
John Mandereau schrieb:
On 2008/10/25 23:02 +0200, Francisco Vila wrote:
Is there a way to list the changes made to LSR snippets from last time
that they were translated?
Yeah, but not before Thursday ;-)
Success!
I'm thinking on something along the lines
of the make check-t
On 2008/10/29 19:22 +0200, Till Rettig wrote:
> John Mandereau schrieb:
> > It would be even simpler for me to add input/texidocs/*.texidocs by
> > default to "make check-translation" (remember you can always set the
> > files to be checked with CHECKED_FILES makefile variable).
> >
> Wouldn't
On 2008/10/29 16:25 +0200, Heikki Johannes Junes wrote:
> Please find the update for Finnish translation as an attachment.
> The update is against recent git-source of LilyPond.
Thank you, but sorry, we update program messages translations
exclusively through the Translation Project. Please send
On Wed, Oct 29, 2008 at 8:10 AM, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
> These kind of aspects can seldomly be regarded as bugs, but the intention in
> LilyPond is
> to provide as beatiful results as possible in as many cases as possible. If
> you look at the
> regression tests for LilyPond at
George_ wrote:
...
As I said before (and I am even
more certain about this now) I think the \cresc and \dim should be changed
in future versions of Lilypond (especially with the stable release coming
up) to make them into one-time text dynamics.
This is exactly what happens if you use the comman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 29. Oktober 2008 schrieb George_:
> Well, shouldn't the file be changed for future versions of Lilypond so that
> the \cresc command produces the text crescendo, and the \< \! produces the
> hairpin one? They are separate commands, and in
2008/10/29 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> \cresc ... Starts a text crescendo
> \decresc ... Starts a text decrescendo
> \dim ... Starts a text diminuendo
> All of these would simply be ended by \!.
I agree, but in this case we'd have to first have a convert rule that turns
\version "
13 matches
Mail list logo
