James Lowe | 28 Mar 09:25 2015
Picon

PATCHES: Countdown for March 31st 2015

Hello,

Here is the current patch countdown list. The next countdown will be on
March 31st.

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:

David Nalesnik: Patch: Add means to display objects accessible from a grob
http://code.google.com/p/lilypond/issues/detail?id=4328

James Lowe: Dots ignoring shifted ledger lines
http://code.google.com/p/lilypond/issues/detail?id=4040

____________________

REVIEW:

David Nalesnik: Patch: make pretty-print available in ly files
http://code.google.com/p/lilypond/issues/detail?id=4331

____________________

WAITING:

Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures
(Continue reading)

Simon Albrecht | 27 Mar 17:31 2015
Picon

Re: Language selection code

Am 27.03.2015 um 14:38 schrieb David Nalesnik:
> Hi Simon,
>
>
> On Thu, Mar 26, 2015 at 6:43 PM, Simon Albrecht 
> <simon.albrecht <at> mail.de <mailto:simon.albrecht <at> mail.de>> wrote:
>
> [...]
>
>     So the roadmap would include
>     – discussing design and coding (?)
>
>
> I haven't gone through this thoroughly, but I did notice that an 
> invalid statement like this
> \language general.deutsch.foo
> isn't gracefully dealt with.
>
> I haven't studied this enough to diagnose the problem, but I did 
> notice the following:
>
> % extended from music-functions-init.ly:603 
> <http://music-functions-init.ly:603>
> language =
> #(define-void-function
>   (parser location arg)
>   ;; Usage:
>   ;; \language input.LANG or
>   ;; \language output.LANG or
>   ;; \language LANG—which is equivalent to
(Continue reading)

david.nalesnik | 27 Mar 16:03 2015
Picon

make pretty-print available in ly files (issue 222810043 by david.nalesnik <at> gmail.com)

Reviewers: ,

Message:
Please review.  Thanks!

Description:
make pretty-print available in ly files

Please review this at https://codereview.appspot.com/222810043/

Affected files (+1, -0 lines):
   M ly/init.ly

Index: ly/init.ly
diff --git a/ly/init.ly b/ly/init.ly
index  
8265d171cf2ab3f9ae632ddf722ab4a3a402f99e..d014a401ab506a11213cd1d127108f78e5ef9693  
100644
--- a/ly/init.ly
+++ b/ly/init.ly
 <at>  <at>  -35,6 +35,7  <at>  <at> 

  #(use-modules (scm clip-region))
  #(use-modules (srfi srfi-1))
+#(use-modules (ice-9 pretty-print))

  $(if (ly:get-option 'include-settings)
    (ly:parser-include-string parser
David Nalesnik | 27 Mar 14:46 2015
Picon

Re: Language selection code

On Fri, Mar 27, 2015 at 8:38 AM, David Nalesnik <david.nalesnik <at> gmail.com>
wrote:

> I haven't gone through this thoroughly, but I did notice that an invalid
> statement like this
> \language general.deutsch.foo
> isn't gracefully dealt with.
>
> [...]

>
> If correct-input is #f, language will be undefined.  You could add
>
(else #f)
>

Yes, doing this:

    (language (cond ((= 1 (length arg)) (list-ref arg 0))
                     ((= 2 (length arg)) (list-ref arg 1))
                     (else #f)))

(and changing the German note-name in the example)
cleans up the output.

DN
Simon Albrecht | 27 Mar 00:43 2015
Picon

Language selection code

Hello,

triggered by a discussion on -user I have begun to implement a new 
\language command which in addition to setting the note names input 
language also automatically translates the default text fields in 
tagline and table of contents, or may be used for both tasks separately.
By now, with help from David N. and Harm, I made a one-file working 
version of this feature (see attachment) and would like to bring this 
feature into the code base. There are many comments inline explaining 
the design and coding.
I could not manage to combine a convincing new interface with full 
backwards compatibility, partly because optional arguments were not 
working as expected. As a result, the previous \language "english" 
syntax would have to be updated into the equivalent \language 
input.english – which I estimate to be feasible using convert-ly, 
although I have no knowledge of python.
How to proceed further? I think it unlikely that I am soon going to make 
contributions regularly, but I think it would be good to have a mentor, 
as suggested by the CG. I work with ubuntu and have also started using 
git, so I might be able to incorporate these changes in the code base 
and propose a patch myself, though I’m not much into it yet and will 
need help in addition to the CG explanations…
So the roadmap would include
– discussing design and coding (?)
– placing the code in the respective .ly and .scm files where it belongs
– modifying the documentation
– and adding a convert-ly rule.

I hope that I can thus contribute something of use.

(Continue reading)

James Lowe | 25 Mar 21:08 2015
Picon

PATCHES: Countdown for March 28th 2015

Hello,

Here is the current patch countdown list. The next countdown will be on
March 28th.

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:

Urs Liska: Patch: web: productions: Update Aurélien's Rosenkavalier
http://code.google.com/p/lilypond/issues/detail?id=4327

James Lowe: Patch: Web: Introduction.itexi - updated 'Productions'
http://code.google.com/p/lilypond/issues/detail?id=4322

____________________

COUNTDOWN:

David Nalesnik: Patch: Add means to display objects accessible from a grob
http://code.google.com/p/lilypond/issues/detail?id=4328

James Lowe: Dots ignoring shifted ledger lines
http://code.google.com/p/lilypond/issues/detail?id=4040

____________________

(Continue reading)

Urs Liska | 25 Mar 13:54 2015

Re: Sans-serif free Unicode font (was Re: Ghostscript 9.15)


Am 25.03.2015 um 13:32 schrieb Carl Sorensen:
>
> On 3/25/15 3:06 AM, "Urs Liska" <ul <at> openlilylib.org> wrote:
>
>> 2) Find suitable fonts and include them in the distribution
>> I know this is a more difficult issue than 1) but I think it would be
>> worth it. By default LilyPond scores don't use sans or monospace (IISC)
>> but I think LilyPond should actually provide beautiful defaults for
>> these too.
>> Maybe it would be a good start looking for fonts in the same sources as
>> CenturySchoolbook?
> As of 2014, Google has released a free unicode sans-serif font, Carlito:
>
> http://openfontlibrary.org/en/font/carlito
>
>
> I don't know if it is any better than Helvetica or Arial.

I don't think so.
However, "better" can only be considered in terms of "visually suitable" 
in the context of LilyPond scores.
I think the fonts we're looking for should have a similarly classic or 
old-fashioned look as Century.

Maybe we should look for fonts that (optionally) ship with texlive.

Urs

> Carl
(Continue reading)

Urs Liska | 25 Mar 09:38 2015

Fwd: Re: Ghostscript 9.15

Sorry, this had accidentally gone private ...

-------- Weitergeleitete Nachricht --------
Betreff: 	Re: Ghostscript 9.15
Datum: 	Wed, 25 Mar 2015 09:31:49 +0100
Von: 	David Kastrup <dak <at> gnu.org>
An: 	Urs Liska <ul <at> openlilylib.org>

Urs Liska <ul <at> openlilylib.org> writes:

> Am 25.03.2015 um 08:51 schrieb David Kastrup:
>> Urs Liska <ul <at> openlilylib.org> writes:
>>
>>> Am 25.03.2015 um 07:50 schrieb David Kastrup:
>>>>> So that’s probably a matter of the font, not of its style - not every
>>>>>> font defines ligatures, and the name „TakaoPGothic“ tells me its main
>>>>>> focus would be Japanese (is this true?), so the designers probably
>>>>>> didn’t put so much work in features of Latin script.
>>>>>>
>>>>>> Would you care to try a different font?
>>>> Well, why would the sans-serif font be TakaoPGothic in the first place?
>>>> I think we should be using the same default fonts on every installation.
>>>>
>>> We don't use any particular font for sans-serif and
>>> monospace. LilyPond simply calls the OS's default here.
>>> Which is something I'd like to raise (once more?): Would it be an
>>> option to find suitable complementing fonts here, ship them with
>>> LilyPond and make them the default?
>> As first measure we should just use one of the 11 or so standard
>> PostScript fonts.  Probably Helvetica and Courier for sans serif and
(Continue reading)

david.nalesnik | 24 Mar 17:38 2015
Picon

Add means to display objects accessible from a grob (issue 217260043 by david.nalesnik <at> gmail.com)

Reviewers: ,

Message:
Please review.  Thanks!

Description:
Add means to display objects accessible from a grob

A convenient means of displaying the grobs and grob-arrays pointed to by
various internal properties of a given grob would be very helpful for
debugging and development purposes.  For example, it would facilitate
the
creation of advanced tweaks, which frequently require "lateral" access
to other grobs.

The output of the function 'grob::display-objects' shows all of the
grobs
accessible to a given grob through ly:grob-object, along with the
relevant
interfaces and properties.  It includes properties which are empty: not
all
properties within an interface may be set for or used by a grob
supporting
that interface.

Please review this at https://codereview.appspot.com/217260043/

Affected files (+38, -0 lines):
   M scm/output-lib.scm

(Continue reading)

hanwenn | 24 Mar 12:37 2015
Picon

Re: Decrease space between vertical beams by length-fraction. (issue 214250043 by hanwenn <at> gmail.com)

On 2015/03/14 14:53:37, hanwenn wrote:
> I don't think we have explicit test coverage for this, but not sure
what it
> would look like.

Ping?

https://codereview.appspot.com/214250043/
paulwmorris | 23 Mar 04:45 2015
Picon

Fix issue 4040: Dots ignoring shifted ledger lines (issue 220090043 by paulwmorris <at> gmail.com)

Reviewers: ,

Message:
Please review, thanks!

-Paul

Description:
Fix issue 4040: Dots ignoring shifted ledger lines

includes the following two commits:

add test staff-ledger-positions-dotted-notes.ly

tests positioning of dots on dotted notes with
custom ledger line positions (issue 4040)

staff-symbol.cc: on_line and custom ledger lines

make Staff_symbol::on_line work properly with
custom ledger line positions

Please review this at https://codereview.appspot.com/220090043/

Affected files (+47, -28 lines):
   A input/regression/staff-ledger-positions-dotted-notes.ly
   M lily/staff-symbol.cc

Index: input/regression/staff-ledger-positions-dotted-notes.ly
diff --git a/input/regression/staff-ledger-positions-dotted-notes.ly  
(Continue reading)


Gmane