I have just committed a rewrite of the dynamics engravers that does
away with this feature. I haven't yet thought of a proper convert-ly
rule though.
2008/4/30 Werner LEMBERG <[EMAIL PROTECTED]>:
> > Note that these settings don't behave like most others. As is
> > illustrated in the following
On Thu, 1 May 2008 23:13:26 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote
>
> >> In the meantime, the current behavior of \setTextCresc and the
> >> others
> >> -- that they are only applied once -- should be documented. Would
> >> this be more appropriate in the main
Graham Percival wrote
In the meantime, the current behavior of \setTextCresc and the others
-- that they are only applied once -- should be documented. Would
this be more appropriate in the main body of NR 1.3.1.2 or in
@knownissues?
@knownissues.
Is this a change in policy? Previously an
2008/5/1 John Mandereau <[EMAIL PROTECTED]>:
> - use xsltproc (from libsxlt package) to convert 20 first news items
> from HTML to RSS with a xslt stylesheet. Is it easy to make libxslt
> available on lilypond.org?
Lilypond.org is a debian box, so I think it should be easy. My only
worry is
On Thu, 1 May 2008 13:33:03 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 30, 2008 at 12:42 AM, Graham Percival <[EMAIL PROTECTED]>
> wrote:
> > We could even go with pairs of:
> > \crescText
> > \crescHairpin
>
> I still think we should scrap the Hairpin commands.
Don't
On Wed, Apr 30, 2008 at 12:42 AM, Graham Percival <[EMAIL PROTECTED]> wrote:
>
> I prefer on/off. However, I'm not certain whether we want to go
> with
> \textCrescOn
> or
> \hairpinCrescOn
> (with Off being the opposite, of course)
>
> We could even go with pairs of:
> \crescText
> \
On 2008/04/27, Graham Percival wrote:
> On second thought, could we use "% LSR" as the comment denoter? As in
> "only visible in LSR" ? Or, if you can think of a comment indicator
> that makes more sense, please use that... evidently I can't come up
> with good names.
I cannot come up with bette
Jan Nieuwenhuizen wrote:
> Valentin Villenave writes:
>
> > For instance, our news.xml file could look like:
>
> >
>
> Lots of <:> cruft.
>
> The idea of an rss feed is nice, but I don't like typing xml feeds
> by hand. How about junking old-news.html and just have
> news.ihtml and generate b
Hi Sebastiano,
is it me or is there a problem with the LSR?
It seems that the LSR currently unavailable (the other subdomains at
dsi.unimi.it work fine though); it works for several minutes once in a
while, then nothing.
Thanks,
Valentin
___
lilypond-
On 2008/04/26, Graham Percival wrote:
> Could we get
> [relative=x]
> to automatically imply
> [fragment]
> ? I can't imagine any possible use of [relative] where you don't
> want [fragment], and this would simplify the doc source by almost
> entirely omitting [fragment].
Indeed, relative=x d
2008/5/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> please give me or Jan a ping when you make changes to the website
> formatting scripts; for security reasons, the scripts on lilypond.org
> themselves are not automatically updated when you change them in git.
Oh, yes indeed; I thought the websi
Hi Valentin,
please give me or Jan a ping when you make changes to the website
formatting scripts; for security reasons, the scripts on lilypond.org
themselves are not automatically updated when you change them in git.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
2008/4/21 Legrand Jean-Marc <[EMAIL PROTECTED]>:
> This ancient habit has one single exception which is not, to my mind,
> supported by Lilypond : when 'n' identical and successive notes are altered
> the same way, the accidental IS NOT repeated on the 'n' following notes.
It's interesting: I've
Le 1 mai 08 à 10:18, Valentin Villenave a écrit :
2008/4/28 Nicolas Sceaux <[EMAIL PROTECTED]>:
Categories should be set right in markup command definitions,
in file scm/define-markup-commands.scm.
The code generating the markup command documentation file is
scm/document-markup.scm, which may
2008/4/28 Nicolas Sceaux <[EMAIL PROTECTED]>:
> Categories should be set right in markup command definitions,
> in file scm/define-markup-commands.scm.
> The code generating the markup command documentation file is
> scm/document-markup.scm, which may need to be edited a bit
> (there are some
15 matches
Mail list logo
