Carl Sorensen | 25 May 05:39 2016

Tie properties vs. slur properties.

The tie interface has height-limit and ratio as part of Tie.details.

The slur interface has height-limit and ratio as part of Slur (not
embedded in Slur.details).

Is there a reason for this difference, or is it just due to never making
the two be consistent?  If there is no reason for the difference, I think
the two should be rationalized, probably by moving Slur.height-limit and
Slur.ratio to Slur.details.height-limit and Slur.details.ratio.

Before I make such a patch, could you tell me if it makes sense to do so?

Thanks,

Carl
Carl Sorensen | 25 May 02:12 2016

scriptDefinitions context property

According to the Internals Reference, scriptDefinitions is an internal
context property, meaning that the user should not change it.

Why is this so?  As far as I can see, scriptDefinitions is not defined
during engraving, but during initialization.  So it ought to be
user-settable, it seems to me.

The same applies for quotedCueEventTypes and quotedEventTypes.  It seems
to me like all of these properties should be User backend properties,
rather than Internal backend properties.

Have I missed something?

Thanks,

Carl
Carl.D.Sorensen | 25 May 01:57 2016
Picon

Re: Add halfopenvertical to script.scm (issue 297340043 by Carl.D.Sorensen <at> gmail.com)

Reviewers: thomasmorley651,

Message:
It seems to me that if we want to make this kind of a regtest we should
really be looking at all TextScripts that are supposed to be
articulations, and seeing if the articulations work.

The regtest you proposed looks at all the articulations we have defined,
and sees if they properly print out.  This regtest would not have caught
the error I made, because the problem was I didn't add it to the
articulation list.

I think the regtest you proposed has some potential value, but I don't
think it should be tied to this issue.

The challenge is that some of the feta font elements in the scripts.*
familiy are used as articulations, while others (e.g. caesura) are not.
And the ones not used as articulations are not included in script.scm by
choice.

Maybe we could add a field to the NR Appendix A.8 [1] that is the
articulation used for each of the scripts.  And for those that had no
entry it would say something like "Not used as articulation".

Thanks for the careful thought!

Carl

1.
http://lilypond.org/doc/v2.19/Documentation/notation/the-feta-font#script-glyphs
(Continue reading)

James Lowe | 24 May 09:18 2016
Picon

PATCHES: Countdown for May 24th

Hello,

Here is the current patch countdown list. The next countdown will be on
May 27th.

A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/

__________

Push:

4850 Remove self method bindings of translator groups - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/4850
http://codereview.appspot.com/297230043

Countdown:

4857 update doc tarballs link (downloads/) - Federico Bruni
https://sourceforge.net/p/testlilyissues/issues/4857
http://codereview.appspot.com/296210043

4855 Move old news from news-front to news - Urs Liska
https://sourceforge.net/p/testlilyissues/issues/4855
http://codereview.appspot.com/297300043

4854 Set minimum size dots for text spanner to be round. - Carl Sorensen
https://sourceforge.net/p/testlilyissues/issues/4854
(Continue reading)

Dan Eble | 21 May 19:05 2016
Picon

Fwd: Custom accidental styles

[I dropped lilypond-devel when I replied.  Sending David’s reply to the list.]

From: David Kastrup <dak <at> gnu.org>
Subject: Re: Custom accidental styles
Date: May 21, 2016 at 12:29:05 EDT
To: Dan Eble <dan <at> faithful.be>

Dan Eble <dan <at> faithful.be> writes:

>> On May 21, 2016, at 11:00 , David Kastrup <dak <at> gnu.org> wrote:
>> 
>> Dan Eble <dan <at> faithful.be> writes:
>> 
>>> On May 20, 2016, at 05:38 , Simon Albrecht <simon.albrecht <at> mail.de> wrote:
>>>> I was hoping to do further improvements to the code (comments and
>>>> simplification) such as to make the threshold still lower, but I
>>>> didn’t get there unfortunately.
>>>> 
>>>> HTH, Simon
>>>> <accidental-style-baroque.ily>
>>> 
>>> Thank you.  That was helpful.  This worked for me:
>>> 
>>> %% Like voice, with additional cautionary cross-voice cancellations
>>> #(set! accidental-styles (append accidental-styles
>>> 			  `((hymnbook-cautionary #f
>>> 			     (Voice ,(make-accidental-rule 'same-octave 0))
>>> 			     (Staff ,(make-accidental-rule 'same-octave 0))
>>> 			     Staff))))
>> 
(Continue reading)

James | 20 May 19:27 2016
Picon

PATCHES: Countdown for May 20th

Hello,

Here is the current patch countdown list. The next countdown will be on
May 23rd.

A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/

__________

Push:

4851 Scheme_engraver::init_acknowledgers API change - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/4851
http://codereview.appspot.com/291690043

4845 lilypond-ftplugin.vim: set makeprg locally rather than globally - 
Greg Swinford
https://sourceforge.net/p/testlilyissues/issues/4845
http://codereview.appspot.com/292660043

Countdown:

4850 Remove self method bindings of translator groups - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/4850
http://codereview.appspot.com/297230043

Review:
(Continue reading)

Knut Petersen | 20 May 10:56 2016
Picon

broken doc build (orchestra.ly)

Hi everybody!

Building the current git lilypond binary succeeds, but building the documentation is broken even if I try a
single core build.

exec ./autogen.sh --noconfigure in /home/knut/sources/lily ... succeeded after 1 seconds
exec ../configure --prefix=/home/knut/sources/lilybuilt/ in /home/knut/sources/lily/build ...
succeeded after 4 seconds
exec make -j 11 CPU_COUNT=11 LANGS='de' all in /home/knut/sources/lily/build ... succeeded after 71 seconds
exec make -j 11 CPU_COUNT=11 LANGS='de' install in /home/knut/sources/lily/build ... succeeded after 1 seconds
exec make -j 1 CPU_COUNT=1 LANGS='de' doc in /home/knut/sources/lily/build ... failed

tail of build log:
=========

/home/knut/sources/lily/build/scripts/build/out/run-and-check
"/home/knut/sources/lily/build/out/bin/lilypond -dpreview -dresolution=150 -o ./out-www
/home/knut/sources/lily/Documentation/ly-examples/orchestra.ly" "orchestra.preview.log"

Please check the logfile orchestra.preview.log for errors

/home/knut/sources/lily/./Documentation/ly-examples/GNUmakefile:17: recipe for target
'out-www/orchestra.png' failed
make[3]: *** [out-www/orchestra.png] Error 1
make[3]: Leaving directory '/home/knut/sources/lily/build/Documentation/ly-examples'
/home/knut/sources/lily/./Documentation/GNUmakefile:230: recipe for target
'out-www/ly-examples' failed
make[2]: *** [out-www/ly-examples] Error 2
make[2]: Leaving directory '/home/knut/sources/lily/build/Documentation'
/home/knut/sources/lily/stepmake/stepmake/generic-targets.make:166: recipe for target 'WWW-1' failed
(Continue reading)

John Gourlay | 20 May 05:10 2016
Picon

Error from "make doc"

I’m trying to set up a new LilyDev development system after some kind of VirtualBox error that trashed my
old one. I’ve run “make” successfully in my ~/lilypond-git/build directory, and lilypond runs.
When I run “make doc”, however, I get errors. One of the messages from make directed me to look at a log
file named suffix-lyxml.dblatex.log. This file contains the following messages about invalid fonts.
Have I overlooked something in setting up my system?

John Gourlay

Build the book set list...
Build the listings...
XSLT stylesheets DocBook - LaTeX 2e (0.3.5-2)
===================================================
Build suffix-lyxml.pdf
kpathsea:make_tex: Invalid fontname `[lmroman10-regular]', contains '['
kpathsea:make_tex: Invalid fontname `[lmromanslant10-regular]', contains '['
kpathsea:make_tex: Invalid fontname `[lmroman10-italic]', contains '['
kpathsea:make_tex: Invalid fontname `[lmroman10-bold]', contains '['
kpathsea:make_tex: Invalid fontname `[lmsans10-regular]', contains '['
xelatex failed
/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty:100: Font
EU1/lmr/m/n/10=[lmroman10-regular]:mapping=tex-text at 10.0pt not loadable: Metric (TFM) file or
installed font not found.
/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty:100: leading text: \fontencoding\encodingdefault\selectfont
/usr/share/texmf/tex/latex/tipa/t3enc.def:316: Font
EU1/lmr/m/sl/10=[lmromanslant10-regular]:mapping=tex-text at 10.0pt not loadable: Metric (TFM)
file or installed font not found.
/usr/share/texmf/tex/latex/tipa/t3enc.def:316: leading text: }{}
/usr/share/texmf/tex/latex/tipa/t3enc.def:316: Font
EU1/lmr/m/it/10=[lmroman10-italic]:mapping=tex-text at 10.0pt not loadable: Metric (TFM) file or
installed font not found.
(Continue reading)

Dan Eble | 20 May 00:38 2016
Picon

Custom accidental styles

Simon,

When you have time, would you please give me an example of adding a user-defined accidental style? (changes
in https://codereview.appspot.com/280510043/, as far as I can tell)

The latest lilypond doesn’t work on my source where I’ve been using this:

hymnbookCautionaryAccidentalStyle =
    #(set-accidentals-properties
      #f
      `(Voice ,(make-accidental-rule 'same-octave 0))
      `(Staff ,(make-accidental-rule 'same-octave 0))
      'Staff)
— 
Dan

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
fedelogy | 19 May 19:04 2016
Picon
Gravatar

issue 4857: update doc tarball link (issue 296210043 by fedelogy <at> gmail.com)

Reviewers: ,

Description:
issue 4857: update doc tarball link

This completes issue 4833.

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

Affected files (+1, -1 lines):
   M scripts/build/create-weblinks-itexi.py

Index: scripts/build/create-weblinks-itexi.py
diff --git a/scripts/build/create-weblinks-itexi.py  
b/scripts/build/create-weblinks-itexi.py
index  
e529ca7327cdd5a6a4ff2a36a861bd7a413a3b7b..e631c27fd8b43a5e7c75792be202237fadfb9d3d  
100644
--- a/scripts/build/create-weblinks-itexi.py
+++ b/scripts/build/create-weblinks-itexi.py
 <at>  <at>  -554,7 +554,7  <at>  <at>  def make_regtest_links(name, version, lang):
          getTrans("PDF of lilypond-book regtests for ", lang)+version)

  def make_doctarball_links(name, version, lang):
-    url = depth + "download/binaries/documentation/lilypond-"
+    url = depth + "downloads/binaries/documentation/lilypond-"
      # ugly FIXME, but proper build number support isn't Critical.
      url += version + "-1"
      url += ".documentation.tar.bz2"
(Continue reading)

Jon Ciesla | 19 May 16:25 2016
Picon
Gravatar

Whither doc tarballs?

http://lilypond.org/download/binaries/documentation/lilypond-2.19.42-1.documentation.tar.bz2

is 404, for all versions.  Have these moved?

Thanks!

-Jon

--

-- 
http://cecinestpasunefromage.wordpress.com/
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love

-d. bowie

Gmane