Comment #2 on issue 1364 by jameseli...@googlemail.com: Enhancement:
Dynamics should be printed *above* vocal staves
http://code.google.com/p/lilypond/issues/detail?id=1364
A slightly more definitive source:
http://mpa.org/music_notation/choral_standards
Comment #4 on issue 1364 by v.villenave: Enhancement: Dynamics should be
printed *above* vocal staves
http://code.google.com/p/lilypond/issues/detail?id=1364
I'm not sure I agree. The whole point of LilyPond has always been to
provide the user with a nearly-ideal output out-of-the-box.
Updates:
Status: Started
Comment #2 on issue 1247 by ianhuli...@gmail.com: Use new modules provided
by Guile V2 - Part 1 (ice-9 curried-definitions)
http://code.google.com/p/lilypond/issues/detail?id=1247
In lily.scm ly:load needs to use primitive-load-path to allow Guile
Status: Accepted
Owner:
Labels: Type-Scripts Priority-Low
New issue 1365 by percival.music.ca: convert-ly removes Dynamics blocks too
aggressively
http://code.google.com/p/lilypond/issues/detail?id=1365
spun off from issue 1288. Note that this is not release-blocking.
Comment 12 by
Updates:
Labels: -Patch
Comment #17 on issue 1288 by percival.music.ca: running convert-ly on git
http://code.google.com/p/lilypond/issues/detail?id=1288
The convert-ly Dynamics thing is now 1365. I have manually updated the
version of ly/performer-init.ly.
The policy has been
Updates:
Summary: Language links in manual pages should be right from start and
kept intact by web_post.py
Status: Started
Owner: john.mandereau
Comment #1 on issue 1363 by john.mandereau: Language links in manual pages
should be right from start and kept intact by
Graham wrote Wednesday, October 27, 2010 8:02 AM
I agree with wbsoft. It's easy to mention \dynamicsUp in Notation
2.1 Vocals -- I'd actually be shocked if Trevor hadn't added this
already --
Actually I haven't, but I will.
That said, \dynamicsUp should be added to the vocal templates,
Comment #2 on issue 1363 by percival.music.ca: Language links in manual
pages should be right from start and kept intact by web_post.py
http://code.google.com/p/lilypond/issues/detail?id=1363
hmm... ok. web_post.py is only used by make website, so I guess you have
three things to check:
Status: Accepted
Owner:
Labels: Priority-Medium Patch Type-Enhancement
New issue 1366 by v.villenave: [Patch] Tablature: proper support for
tie/slur- and tie/glissando-constellations
http://code.google.com/p/lilypond/issues/detail?id=1366
Here's a patch submitted by Marc Hohl a while
Comment #3 on issue 1363 by john.mandereau: Language links in manual pages
should be right from start and kept intact by web_post.py
http://code.google.com/p/lilypond/issues/detail?id=1363
Oh, you're right that the broken link I see with make doc has nothing to
do with web_post.py stuff.
2010/10/23 Patrick McCarty pnor...@gmail.com
2010/10/21 Janek Warchoł lemniskata.bernoull...@gmail.com:
% I was very happy to find out that \parenthesize works not only with
notes,
but very unhappy to find out that the brackets seem to have constant
size.
For example, they are too small
Hi guys!
I request a feature for the upcoming 2.14.0.
As we have a good support for SVG now, wouldn't it be nice to add a
--svg switch to the program, so that you can write
lilypond --svg fancystuff.ly
instead of
lilypond -dbackend=svg fancystuff.ly
which seems to be less intuitive?
On Wed, Oct 27, 2010 at 2:50 PM, Richie Gress searchfgold67...@live.com wrote:
I'm having a small issue here. I'm writing a score for Mutopia which
involves some beamed notes, which are in a \times 4/6 { ... } block,
switching staves like this:
\times 4/6 { \stemUp c, ees aes c[ ees aes c ees
Comment #4 on issue 316 by pkun80: ancient \ictus not centered
http://code.google.com/p/lilypond/issues/detail?id=316
Incidentally, in many cases it should be placed inside the staff lines, the
current placement makes it really hard to see which note it might be
belonging to.
I'm not top posting.
Tiny example:
\include english.ly
%\version 2.12.3
\score {
% \keepWithTag #'notate
\keepWithTag #'midi
\relative c' {
\clef bass
bf8 a16 g a8 d, g ef c d
\tag #'notate {g,1 \fermata}
\tag #'midi {g,1.}
}
\layout { }
\midi { }
Am Mittwoch, 27. Oktober 2010, um 21:53:10 schrieb Ed:
Tiny example:
[...]
\relative c' {
\clef bass
bf8 a16 g a8 d, g ef c d
\tag #'notate {g,1 \fermata}
\tag #'midi {g,1.}
The pitch values are evaluated before the tag-killing routine comes in.
Pitches in
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low Frog
New issue 1367 by v.villenave: Enhancement: NoteNames context should handle
any note names language
http://code.google.com/p/lilypond/issues/detail?id=1367
As Mats noticed a few years ago, default (Nederlands) note names
Comment #1 on issue 1367 by v.villenave: Enhancement: NoteNames context
should handle any note names language
http://code.google.com/p/lilypond/issues/detail?id=1367
Of course, there are workarounds: I posted a very dumb one on -user
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 1368 by RalphBugList: ly:score-set-header! badly documented
http://code.google.com/p/lilypond/issues/detail?id=1368
The doc string of ly:score-set-header! doesn't document `module', and
it's quite cryptic what this argument is
Greetings, Werner -
Thank you for your report. This has been added as:
http://code.google.com/p/lilypond/issues/detail?id=1368
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Wed, Oct 20, 2010 at 9:27 AM, Valentin Villenave
valen...@villenave.netwrote:
Hi Alexander,
CC-ing to the bug list just in case.
On Wed, Oct 20, 2010 at 2:39 PM, Alexander Kobel n...@a-kobel.de wrote:
why does LyricText #'font-series default to #'bold-narrow?
First, it's
On Tue, Oct 26, 2010 at 7:25 AM, Werner LEMBERG w...@gnu.org wrote:
The doc string of ly:gulp-file doesn't document `size'.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 1369 by RalphBugList: incomplete documentation of ly:gulp-file
http://code.google.com/p/lilypond/issues/detail?id=1369
The doc string of ly:gulp-file doesn't document `size'.
From Werner Lemberg
Status: Accepted
Owner:
Labels: Type-Build Priority-Medium Maintainability
New issue 1370 by percival.music.ca: any console-output-producing regtests
should be separate
http://code.google.com/p/lilypond/issues/detail?id=1370
If a regtest is designed to produce console output, it should
I'm directing this primarily to bug-list folks. This was submitted
over a week ago, and I see no action. Did I miss something?
Yes. I've already fixed this in the git repository.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
25 matches
Mail list logo
