PATCHES: Countdown for July 18th 2014
Hello,
Here is the current patch countdown list. The next countdown will be on
July 18th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
PUSH:
Mark Polesky: Mention backslash escaping in Scheme.
http://code.google.com/p/lilypond/issues/detail?id=4002
James Lowe: Patch: Doc: notation-appendices.itely - added 2 Clefs
http://code.google.com/p/lilypond/issues/detail?id=3988
David Kastrup: Patch: Pitch alterations use SCM rather than flower rationals
http://code.google.com/p/lilypond/issues/detail?id=3967
James Lowe: Patch: Changes.tely updated - 2.19.x up to June 2014
http://code.google.com/p/lilypond/issues/detail?id=3965
James Lowe: Create Texinfo @multitable entries for the
articulations.Appendix
http://code.google.com/p/lilypond/issues/detail?id=1189
COUNTDOWN:
David Kastrup: Patch: \retrograde fails on slurs
http://code.google.com/p/lilypond/issues/detail?id=4009
Thomas Morley: typos/oversight in align-interface.cc and
page-layout-problem.cc
http://code.google.com/p/lilypond/issues/detail?id=4008
David Kastrup: Patch: Fix parts of apparently dead code make-stream-event
http://code.google.com/p/lilypond/issues/detail?id=4007
David Kastrup: Patch: NR: warning for { \chordmode { c } c } obsoleted
by issue 3797
http://code.google.com/p/lilypond/issues/detail?id=4003
David Kastrup: Patch: Fix doc string of ly:pitch-diff
http://code.google.com/p/lilypond/issues/detail?id=4001
Mark Polesky: Make tablature half-note stem-spacing adjustable.
http://code.google.com/p/lilypond/issues/detail?id=3999
David Kastrup: Patch: Let "Mars" example in pitch snippets use isolated
durations
http://code.google.com/p/lilypond/issues/detail?id=3998
Mark Polesky: Rename 'thin-kern to 'segno-kern.
http://code.google.com/p/lilypond/issues/detail?id=3995
Mark Polesky: Change "dash-details" to "dash-definition".
http://code.google.com/p/lilypond/issues/detail?id=3994
David Nalesnik: Using dodecaphonic and dodecaphonic-no-repeat there is
no difference
http://code.google.com/p/lilypond/issues/detail?id=3992
Mark Polesky: Automatically sort props within each grob-interface.
http://code.google.com/p/lilypond/issues/detail?id=3952
David Kastrup: simple chord inversions take 2-octaves
http://code.google.com/p/lilypond/issues/detail?id=2617
REVIEW:
James Lowe: Patch: CG: Update of Patchy instructions
http://code.google.com/p/lilypond/issues/detail?id=4013
WAITING:
Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures
http://code.google.com/p/lilypond/issues/detail?id=3918
Janek WarchoĊ: Positioning of "8" under clef symbol in G_8 clef
http://code.google.com/p/lilypond/issues/detail?id=3186
Mike Solomon: Patch: Prevents vertical axis groups with empty skylines
http://code.google.com/p/lilypond/issues/detail?id=3156
Mike Solomon: Patch: Removes the translate_axis call from
axis-group-interface outside-staff positioning.
http://code.google.com/p/lilypond/issues/detail?id=3134
David Kastrup: Patch: Implement music functions in Scheme rather than C++
http://code.google.com/p/lilypond/issues/detail?id=2716
Thank you,
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: merging philomelos musicxml2ly-dev
On 13/07/14 14:57, Martin Tarenskeen wrote: On Sun, 13 Jul 2014, James wrote: I have no preferences either way - we have done this for articulate.ly for instance - but unless we know that philomelos and LilyPond's versions are reasonably close to start with we could end up with each version becoming so far apart in terms of codebase that nothing gets fixed or that LilyPond's musicxml2ly becomes so far behind philomelos to be worse than useless and we might as well remove musicxml2ly from the code and just point to Philomelos. Would it be an idea to freeze development of musicxml2ly until the Philomenos improvments have been merged with Lilypond's "official" version? This is already the defacto situation? There haven't been much changes for months on both sides I think? This is a question for the dev list. cc-ing them. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Add an expert font tree interface (issue 108700043 by perpeduumimmob...@gmail.com)
Fails make check
--snip--
regression/font-expert-selection.ly
--snip--
Processing
`/tmp/build-lilypond-autobuild/out/lybook-testdb/73/lily-16d682d4.ly'
Parsing...
Renaming input to:
`/tmp/lilypond-autobuild/input/regression/font-expert-selection.ly'
/tmp/lilypond-autobuild/input/regression/font-expert-selection.ly:84:31:
error: syntax error, unexpected \lyricmode,
expecting \sequential or \simultaneous or << or '{'
\new Lyrics \lyricsto "v"
\lyricmode { Foo -- bar baz xyz -- zy! }
/tmp/lilypond-autobuild/input/regression/font-expert-selection.ly:80:3:
error: errors found, ignoring music expressio
n
<<
/tmp/lilypond-autobuild/input/regression/font-expert-selection.ly:99:1:
error: Unfinished main input
--snip--
https://codereview.appspot.com/108700043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing how a font style is requested
Hi all,
since I could not find anything suitable to solve the issue described
below, I decided to write a little patch. Please have a look at
https://codereview.appspot.com/108700043
and tell me what you think about it.
[ BTW: This might or might not be entirely orthogonal to the music font
selection methods which are debated about currently, in the sense that
the feta font loader is hard-coded and built-in into
make-pango-font-tree and the proposed make-expert-font-tree. Sorry, I
did not follow those discussions in detail; but if you think that's a
good time to integrate music font selection as well, please go ahead. ]
I could not see a way to achieve what I need in user-level Scheme, since
add-font is not exposed publicly (and probably for a good reason). I'm
happy to take comments on functionality and coding style; I will write a
bit of documentation in addition to the regtest once (if?) you deem the
interface acceptable.
I hope goals and syntax are somewhat self-explaining; otherwise, feel
free to ask for further explanations. I barely added syntactic sugar
(except the default font scale 1.0), but I'm willing to reconsider the
input syntax to make-expert-font-tree if you have any better ideas.
However, a front-end to it should be much more easy to write, and this
is doable in user-level code.
Thanks in advance,
Alexander
On 07/11/2014 11:59 AM, Alexander Kobel wrote:
Dear all,
I like to use the Romande ADF font family [1] in one of my scores. I do
the usual rule-of-three with
\paper { ... (make-pango-font-tree
"Romande ADF No2 Std" "Romande ADF Std" "monospace"
(/ myStaffSize 20)) ... }
(If you wonder, No2 is condensed, and the non-condensed version, used in
the headers, is mapped to sans for easy access.)
However, here's the catch: Romande does offer a bold variant, but it
announces it as "DemiBold" instead of "Bold", according to fc-list. I
know that I can switch to the different font each time I need bold, but
that's an utter nuisance.
Is there any way to tell Lily how to choose a bold variant? Bonus points
if it only applies to a specific, say, the serif font. Or, , if it is possible to define a mapping similar to
myserif = { regular: # default
"Romande ADF No2 Std:style=Regular",
bold:# choose way of selecting bold
"Romande ADF No2 Std:style=DemiBold",
italic: # pretend I don't like Romande's italics
# and need to scale some other font to match
"Gentium:style=Italic:scaling=0.93",
bold-italic: # use small caps family instead
"Romande ADF Style Std:style=Regular" }
...
\paper { #(define fonts (myserif mysans mymono (/ myStaffSize 20)) }
Obviously, that's not Lily's syntax, but you get the point...
Thanks in advance,
Alexander
[1] http://arkandis.tuxfamily.org/adffonts.html
___
lilypond-user mailing list
lilypond-u...@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
