Re: Appearance of S-curves

Hi, I find the second one with crossing beziers mich more pleasant, but I'm sure the question is easily settled by looking at any good hand-engraved example (I'm travelling right now and don't have any at hand, sorry). Best, Simon > On 26.04.2019 - 13:10, Thomas Morley wrote: > > > Hi, > > cu

Re: What is holding up 2.20 release?

I would like to give whatever small contribution I can make to this without knowing so much on the technical levels; please do tell me whether I say below is considered helpful. On 18.11.19 18:10, Jonas Hahnfeld wrote: 965a607096 Fix #1367: NoteNames context in any language not sure, has qui

Re: vim script for transpositions

Hello, thanks for your interest in sharing. LilyPond’s code base doesn’t contain any tools like this. There are of course LilyPond’s built-in music functions for transposing, but that’s a slightly different use case. What’s more comparable are the tools for manipulating input code contained

2.20 announcements/publicity

Hello everybody, I’ve been more or less lurking on the lists for quite a while now and I’m sorry for not contributing myself these days. I’m thrilled about the boost to development efforts that could be seen and immensely grateful for all of you keeping up the good work, especially completing

Re: Re: An exciting new release… of Sibelius!!!

Let's be honest, they really had to get their stuff together to keep any ground all against Dorico. Best, Simon > On 27.03.2020 - 15:26, Shane Brandes wrote: > > > They are really on the ball on that one. > > > -Shane > > > On Fri, Mar 27, 2020 at 10:09 AM Valentin Villenave > wrote: > >

GS version conflict in packaged 2.20 and 2.21

Hello everyone, it appears from this exchange that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known issue? Best, Simon

Re: GS version conflict in packaged 2.20 and 2.21

On 18.04.20 01:46, Simon Albrecht wrote: Hello everyone, it appears from this exchange <https://lists.gnu.org/archive/html/lilypond-user/2020-04/msg00294.html> that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 16:56, Valentin Villenave wrote: Yes, a French user also had some gs issues that I think may be related to yours: https://lists.gnu.org/archive/html/lilypond-user-fr/2020-04/msg00164.html That seems to be the same usage issue—see my parallel reply or the -user thread. Best, Simo

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 20:27, Werner LEMBERG wrote: Do we have a warning somewhere in the LilyPond documentation that people must not use the binary directly but the wrapper? Simon, have you tried to find something in the docs? If yes, what keywords were you looking for? I have no idea from where I mig

Re: OpenType Features

On 18.01.2016 17:59, Jay Anderson wrote: This is the lilypond issue: https://code.google.com/p/lilypond/issues/detail?id=1388 (What's the new issue location? I couldn't find it in my quick searching and lilypond still points to google code (

Re: OpenType Features

On 18.01.2016 18:40, James wrote: I'll make a patch Good! TIA, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

text-replacements: add ä and the like (issue 281470043 by simon.albre...@mail.de)

Reviewers: , Message: Please review. Description: text-replacements: add ä and the like Provides aliases auml,Auml,ouml,Ouml,uuml,Uuml They were wanted by a user, so why not provide them? I take it that the list in NR A.13 is auto-generated? Please review this at https://codereview.appspot.com

Re: text-replacements: add ä and the like (issue 281470043 by simon.albre...@mail.de)

On 22.01.2016 02:13, Dan Eble wrote: text-replacements: add ä and the like Provides aliases auml,Auml,ouml,Ouml,uuml,Uuml They were wanted by a user, so why not provide them? I don’t want my observation to hold back this change if everyone else likes it, but this looks like a slippery slope.

Re: text-replacements: add ä and the like (issue 281470043 by simon.albre...@mail.de)

On 22.01.2016 11:12, David Kastrup wrote: Simon Albrecht writes: On 22.01.2016 02:13, Dan Eble wrote: text-replacements: add ä and the like Provides aliases auml,Auml,ouml,Ouml,uuml,Uuml They were wanted by a user, so why not provide them? I don’t want my observation to hold back this

Re: LilyPond & Guile 2

On 22.01.2016 16:23, David Kastrup wrote: Hans Åberg writes: What are the technical problems when trying to integrate Guile 2.0 into LilyPond? The same that were extensively discussed this and last week between Harm and myself on-list. I can’t find the post by Paul Morris which linked some

Re: A bunch of small changes (issue 281510043 by simon.albre...@mail.de)

Please review. https://codereview.appspot.com/281510043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: text-replacements: add ä and the like (issue 281470043 by simon.albre...@mail.de)

On 22.01.2016 13:00, Simon Albrecht wrote: On 22.01.2016 11:12, David Kastrup wrote: Simon Albrecht writes: On 22.01.2016 02:13, Dan Eble wrote: text-replacements: add ä and the like Provides aliases auml,Auml,ouml,Ouml,uuml,Uuml They were wanted by a user, so why not provide them? I don’t

Re: OpenType Features

On 31.01.2016 07:14, Jay Anderson wrote: An update for those interested. I got something working. Brilliant! Looking forward to have this in LilyPond :-) The attached patch is certainly not ready to be merged, but I'm curious if the chosen interface seems reasonable (see smallcaps.ly which

Re: OpenType Features

On 31.01.2016 16:39, Jay Anderson wrote: On Sun, Jan 31, 2016 at 6:52 AM, Simon Albrecht wrote: It definitely looks like a good way to go, except that I wouldn’t know how to use multiple features at the same time. Would it be possible to input font-features as a symbol list, i.e. (random

Re: OpenType Features

On 31.01.2016 16:45, Simon Albrecht wrote: we might even use an alist to allow for things like \override font-features.ligatures = #'(clig dlig hlig) or \override font-features.number-case = #'onum This is also inspired by the list in <https://en.wikip

Fwd: lilypond-book/pdflatex: LaTeX Error: Environment lilypond undefined.

This would rather be a case for the bug list. Best, Simon Forwarded Message Subject: lilypond-book/pdflatex: LaTeX Error: Environment lilypond undefined. Date: Sun, 7 Feb 2016 11:58:51 +0200 From: Dave Plater To: lilypond-devel@gnu.org Hi, I maintain lilypond in

Re: Super and sub

On 07.02.2016 15:07, Noeck wrote: to follow the instructions given on http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl I need a Rietveld account. To login on Rietveld, you need any Google account, like you might use for Gmail, YouTube, or have been using for Google Code.

Add \with-dimensions-from markup command (issue 281710043 by simon.albre...@mail.de)

Reviewers: , Message: Please review. Description: Add \with-dimensions-from markup command This command acts as a front-end to \with-dimensions, taking the new dimensions from a markup object instead of having them explicitly given. Also provides a Changes entry. I didn’t think a regtest was ne

Let ChoirStaff accept Dynamics (issue 284660043 by simon.albre...@mail.de)

Reviewers: , Message: Please review. Description: Let ChoirStaff accept Dynamics This addresses a bug report where dynamics in a ChoirStaff implicitly created a PianoStaff, sporting spurious InstrumentNames. Please review this at https://codereview.appspot.com/284660043/ Affected files (+1, -

When to start patch review

Hello, actually it would make sense to only start Rietveld review _after_ testing, i.e. when the tracker issue is set to Patch:review – wouldn’t it? Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/lis

Re: When to start patch review

On 17.02.2016 09:42, James Lowe wrote: On 16/02/16 21:34, Simon Albrecht wrote: Hello, actually it would make sense to only start Rietveld review _after_ testing, i.e. when the tracker issue is set to Patch:review – wouldn’t it? Full make doc errors are always forgivable, as are unexpected

Re: hyphen syntax

On 17.02.2016 15:58, David Kastrup wrote: Dan Eble writes: >>On Feb 17, 2016, at 05:18 , Jean-Charles Malahieude wrote: >> >>Le 14/02/2016 20:41, Dan Eble a écrit : >>>Are there technical limitations that require typing a double hyphen >>>to hyphenate lyrics? Why not just one? >>> >> >>Tec

Re: hyphen syntax

On 17.02.2016 18:02, tisimst wrote: I've always wondered why the LyricHyphen doesn't actually use the hyphen from the LyricText font rather than a dashed line. I realize that doing that would reduce the customizability of the dash (i.e., length, thickness, dash-period, etc.), but it might it imme

Re: hyphen syntax

On 17.02.2016 18:24, tisimst wrote: On Wed, Feb 17, 2016 at 10:16 AM, Simon Albrecht-2 [via Lilypond] < ml-node+s1069038n187386...@n5.nabble.com> wrote: On 17.02.2016 18:02, tisimst wrote: I've always wondered why the LyricHyphen doesn't actually use the hyphen from the LyricT

Re: hyphen syntax

On 17.02.2016 23:22, Noeck wrote: Or to come back to the quote I started with: IMHO a lyric hyphen is not advanced. You should have come back to the entire quote: ‘And I think the double items suit the advanced functionality better (advanced in comparison to printing a hyphen character from a

(OT) Re: hyphen syntax

On 17.02.2016 23:22, Noeck wrote: I think many of you know the fun you can have with backslashes and escaping (as inhttp://xkcd.org/1638/). Funny site :-) Also see that one: – particularly applies to Schemers… Best, Simon __

Re: Keep parsed document in memory

On 22.02.2016 20:22, Sharon Rosner wrote: Having worked on numerous big scores I've found that if you separate the instrumental parts into separate files you can work quite efficiently on fixes, tweaks and annotations. That’s true for proofreading, but it’s not true for beautification, and mak

Re: Lose the tagline (permanently)

On 23.02.2016 18:42, Noeck wrote: 1) It is in*English* and would be the only English part in my otherwise German score – that looks just unprofessional. That's the most important part for me. Some time ago I made a proposal of having the \language command automatically translate this and othe

Re: Lose the tagline (permanently)

On 23.02.2016 13:56, Abraham Lee wrote: In any new score I create, it has become second nature for me to set tagline = ##f because it gets in the way of the finished product. In any new score I create, I first do \include "standard-include.ily" in order to have all default stylesheet, aliases a

Re: Music function for arrow directions in arpeggios

On 23.02.2016 16:14, Abraham Lee wrote: On Tue, Feb 23, 2016 at 8:04 AM, Malte Meyn > wrote: Am 23.02.2016 um 15:52 schrieb Caio Giovaneti de Barros: I'm trying to write a function to make easier for me to change arrow directions in ar

Re: Music function for arrow directions in arpeggios

On 24.02.2016 00:08, Dan Eble wrote: Is this a case where attaching an arpeggio to a chord with ^ or _ should make a difference, or do I misunderstand the point of those characters? Yes, you do. They change the direction of the entire grob, not the arpeggio-direction indicated by the arrow.

Re: Music function for arrow directions in arpeggios

On 23.02.2016 22:22, Noeck wrote: the names \arpeggioUp and \arpeggioDown are still free and would me much more lilypondish. More imprecise, really. It’s really only the direction of the arrow that’s changed, not the direction of the whole grob. Best, Simon _

Sorting of markup commands (NR A.11)

Hello, in the command index, \with-dimensions-from is sorted _after_ \with-dimensions, as I’d expect. The source code also has them in this order. However, the auto-generated documentation in NR A.11, ‘Other’

Re: starting to contribute (GSoC)

On 02.03.2016 20:56, Carl Sorensen wrote: There are some issues that have been identified as easy. You can locate them by searching for "Frog" on the issues list: https://sourceforge.net/p/testlilyissues/issues/search/?q=frog Or, to exclude closed issues:

Verifying issues

Hello, I noticed that there have been many ‘Issues to verify’ around, so I started to catch up with these. Now the question is: Shouldn’t we only mark issues as verified, when the change is already included in an official release? For curiosity, following the CG instruction I took the committi

Re: Verifying issues

On 03.03.2016 00:15, Urs Liska wrote: Am 02.03.2016 um 23:52 schrieb Simon Albrecht: Hello, I noticed that there have been many ‘Issues to verify’ around, so I started to catch up with these. Now the question is: Shouldn’t we only mark issues as verified, when the change is already included in

Re: Verifying issues

On 03.03.2016 00:19, Trevor Daniels wrote: Simon Albrecht wrote Wednesday, March 02, 2016 10:52 PM >I noticed that there have been many ‘Issues to verify’ around, so I >started to catch up with these. Now the question is: Shouldn’t we only >mark issues as verified, when the change i

Re: Verifying issues

On 03.03.2016 10:19, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" To: "ly-devel" Sent: Wednesday, March 02, 2016 10:52 PM Subject: Verifying issues Hello, I noticed that there have been many ‘Issues to verify’ around, so I started to catch up

Re: Changing Staff Size Without Messing Up Fonts

On 07.03.2016 04:45, tisimst wrote: On Sunday, March 6, 2016, kwpaprocki [via Lilypond] <[hidden email] > wrote: Hello, I've been having trouble with changing staff size. I've been using this: #(set-global-staff-size 30) to change the staff size. When I do the text and no

Re: Let ', ' separate symbol lists like '.' does (issue 290490043 by d...@gnu.org)

I also like the idea. Should this get a regtest? Best, Simon https://codereview.appspot.com/290490043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Unable to use git-cl

On 08.03.2016 19:54, Carl Sorensen wrote: I would hate to leave LilyPond development, but it appears that I have no choice, as I cannot contribute with a broken toolchain. I can upload patches to Rietveld, as you can see at https://codereview.appspot.com/283550043 but the links to the issue tr

Re: Ask about the lyric of Lilypond

Hello, it was quite correct to ask on the -user list. The -devel mailing list is about development of LilyPond, not about usage. Best, Simon On 19.03.2016 16:50, 15221328968 wrote: Hello: I am a university student in China and I am interested in making music score by using computer. R

Re: [Feature Request] Align lyrics to middle of font 'x-height' instead of baseline

On 23.03.2016 18:14, Abraham Lee wrote: Dev Team, I was wondering if you have any insight concerning the possibility of/complications with changing the default Y-offset of LyricText to be aligned on vertical center of the font's x-height. The Dynamics characters do something similar already (rou

Re: [Feature Request] Align lyrics to middle of font 'x-height' instead of baseline

On 23.03.2016 19:04, tisimst wrote: Why would anybody want that? The lyrics should be placed between the skylines of the neighbouring lines, and I don’t see the point of any exact v-centering. I can count quite a few times where I have wanted this, not only with hymnal-like music either. I can't

Re: GSoC next steps

On 25.03.2016 21:43, Urs Liska wrote: Paul Morris and Isaac David have both applied for the "Chord Structures" project which would be mentored by Carl Sorensen. So that means there will have to be a choice between these two. David Garfinkle has applied for both "MusicXML export" and "Emmentaler

Re: Leave of absence / lookahead

On 28.03.2016 10:03, David Kastrup wrote: I've been on my yearly vacation (climbing in Italy for 10 days) since last Thursday and so I've been a lot less responsive and particularly productive the last day. While I do check the messages and try providing answers morning and evening, I don't actu

New context modifier \CompletionRhythms?

Hello, using Completion_heads_engraver and Completion_rests_engraver means a lot of typing, and yet it is a pretty stereotypical action. So I thought about introducing a context modification identifier (like \RemoveEmptyStaves) for this task. Do you think this makes sense? Perhaps one might a

Re: Code examples in docs

On 06.04.2016 01:09, Urs Liska wrote: Hi, can someone tell me where I should look for code that generates code examples in the HTML docs? There are links on the pictures, aren’t they? Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.

Re: How to create complex chord

Hi Larry, how come you asked on the devel list? As the name says, this list is about developing LilyPond, not about using it – for that, there’s the user list. On 06.04.2016 21:57, Larry wrote: Hello, I need to create a chord of which part is a tuplet and don't know how. A chord can only

Re: New context modifier \CompletionRhythms?

On 09.04.2016 15:16, Dan Eble wrote: these are the kinds of questions that should be asked before turning it on by default and to decide whether the command to turn it off should be terse or verbose. That’s a misunderstanding, I didn’t want them to be turned on by default. The question is, i

Re: New context modifier \CompletionRhythms?

On 09.04.2016 23:37, David Kastrup wrote: Why would you even split note values across bars in "ancient music"? I much prefer unmolested note values and bar lines_between_ staves there. Makes the motives stand out clearer and avoids boorish accentuation of mid-syncopes by the singers. While th

Re: midi2ly will not launch on OSX 10.11.4

On 13.04.2016 18:38, Floris van Manen wrote: midi2ly does not launch on OSX 10.11.4 That is a question about usage, hence to be asked on the -user list. What’s more, you’ll do everybody a great favour if you don’t randomly reply to any thread you find, but start a new thread if you’ve got a ne

Re: midi2ly will not launch on OSX 10.11.4

On 13.04.2016 22:06, v...@klankschap.nl wrote: On 13 Apr 2016, at 20:49, Simon Albrecht wrote: On 13.04.2016 18:38, Floris van Manen wrote: midi2ly does not launch on OSX 10.11.4 That is a question about usage, hence to be asked on the -user list. No, the question is not about usage, it is

Re: midi2ly will not launch on OSX 10.11.4

On 13.04.2016 23:13, Hans Åberg wrote: On 13 Apr 2016, at 22:56, David Kastrup wrote: What makes you think that i’m doing that ? The subject is a new topic. That's why you should not have told your mail program that it is a reply to Such metadata copied into the mail message is not a part of

Re: Notation manual - 1.3.3 Expressive marks as lines - glissandi

Sorry, but what are you playing at with such an e-mail on the -devel list? First, it’s a little bit offensive considering that – as you very well know – all people bringing Lily to you are only volunteers who do their very best to make her as good as possible. Second, this is a _developers’_ lis

Re: Custom accidental styles

Hi Dan, On 20.05.2016 00:38, Dan Eble wrote: When you have time, would you please give me an example of adding a user-defined accidental style? (changes inhttps://codereview.appspot.com/280510043/, as far as I can tell) exactly, that’s the one. I just attach my library file which adds the c

Warn on solitary \! ?

Hello, I was just wondering if we might want to emit a warning if there is a \! without a (de)crescendo before. It’s likely that the latter has only been forgotten. \version "2.19.42" \displayMusic { 2 4\! } => (make-music 'SequentialMusic 'elements (list (make-music 'Note

Re: Scheme question

On 13.06.2016 20:55, David Kastrup wrote: So you probably want testy = #(define-music-function (note) (ly:music?) (make-relative (note) note #{ \tag #'a { $note } \tag #'b { $note } #})) This uses just "note" as the expression affecting \relative, but places two separate copies of t

Re: 4919: beam 1/20 and shorter notes by 1/4 in 2/2 and 3/2 time (issue 303980043 by simon.albre...@mail.de)

On 04.07.2016 19:55, d...@gnu.org wrote: Since this is supposed to be an improvement in typesetting, it would seem rather appropriate to include a regtest demonstrating intended use. That makes it easy to consider the improvements achieved for the same input. https://codereview.appspot.com/3039

Re: GSoC spanners review/update

On 19.07.2016 11:26, Nathan Chou wrote: My other question regards the footnote-spanner acknowledger in Dynamic_align_engraver, which calls Axis_group_interface::add_element to add footnote spanners for dynamics to the DynamicLineSpanner. In what situation is this is actually needed? Well, I gue

Re: Optional fraction after \afterGrace command (issue 304200043 by d...@gnu.org)

LGTM. https://codereview.appspot.com/304200043/diff/20001/Documentation/notation/rhythms.itely File Documentation/notation/rhythms.itely (right): https://codereview.appspot.com/304200043/diff/20001/Documentation/notation/rhythms.itely#newcode3436 Documentation/notation/rhythms.itely:3436: the l

Re: [Spamverdacht] Re: repeating bar numbers and rehearsal marks in frenched score

Am 01.08.2016 um 10:49 schrieb Mark Knoop: > James, could you test this patch for review please? Please create a tracker issue following the CG instructions, with yourself as owner and Patch:new, and upload the patch for review on Rietveld. Then James will test it. Best, Simon

Re: identifiers with numbers - new LSR-snippet

On 13.08.2016 10:29, David Kastrup wrote: \part.1 in contrast is slightly different. I'll work on improvements by and by but at the current point of time this is not really at a "proudly announceable by snippets" state. It still has drawbacks and irks. It seems that others as well as I have b

Re: Help with Scheme engraver please

Hi Trevor, On 24.08.2016 11:51, Trevor Daniels wrote: David Kastrup wrote Wednesday, August 24, 2016 7:48 AM "Trevor Daniels" writes: Prompted by the recent discussion on lute tablature, I tried coding a Scheme engraver to create the duration grobs but quickly ran into a problem. I need to c

Fwd: Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)

Doesn’t seem to have come through to the devel list (probably because you aren’t subscribed), so I forward it. Forwarded Message Subject:Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic) Date: Mon, 5 Sep 2016 00:20:30 +0200 From: Hans Aikema To: lilypond-user , C

Re: Web: home page: add examples/images, reduce news to headlines (issue 306350043 by paulwmor...@gmail.com)

My 2cts. https://codereview.appspot.com/306350043/diff/40001/Documentation/web.texi File Documentation/web.texi (right): https://codereview.appspot.com/306350043/diff/40001/Documentation/web.texi#newcode142 Documentation/web.texi:142: @exampleImage{bach-bwv610} I agree that we should look for t

Re: BUG: Lilypond forgets to draw barline spanner after \bar ""

On 19.09.2016 14:17, Knut Petersen wrote: Hi everybody! As far as I understand after \bar "" a \break is permitted in the middle of a bar. Lilypond is supposed to engrave the next barline at the proper place. At the marked places ( FIXME/ BUG) in the attached score lilypond needs to be force

Re: BUG: Lilypond forgets to draw barline spanner after \bar ""

On 19.09.2016 17:12, Wols Lists wrote: On 19/09/16 13:29, Simon Albrecht wrote: On 19.09.2016 14:17, Knut Petersen wrote: Hi everybody! As far as I understand after \bar "" a \break is permitted in the middle of a bar. Lilypond is supposed to engrave the next barline at the proper

Add annotation of \shape-d curves (WIP) (issue 303650043 by g...@ursliska.de)

Hi Urs, please resubmit the patch without reformatting. https://codereview.appspot.com/303650043/diff/1/ly/music-functions-init.ly File ly/music-functions-init.ly (right): https://codereview.appspot.com/303650043/diff/1/ly/music-functions-init.ly#newcode30 ly/music-functions-init.ly:30: (ice-9

Re: Add annotation of \shape-d curves (WIP) (issue 303650043 by g...@ursliska.de)

https://codereview.appspot.com/303650043/diff/20001/ly/music-functions-init.ly File ly/music-functions-init.ly (right): https://codereview.appspot.com/303650043/diff/20001/ly/music-functions-init.ly#newcode1646 ly/music-functions-init.ly:1646: present and set to @code{##t} the control points, th

Re: How can I read/use properties of LyricText while processing LyricHyphen?

Hi Knut, thanks for taking this on! On 06.10.2016 09:11, Knut Petersen wrote: To solve issue 1255 I added a "use-markup" and a "text" property to LyricHyphen and changed lyric-hyphen.cc to use Text_interface::print if the use-markup property is true. I’d prefer to have an alternative stenci

Re: issue tracker access

Hi Janek, great to see you back in the Pond :-) Best, Simon On 18.10.2016 22:05, Janek Warchoł wrote: Hi guys, can you give me write access to the sourceforge issue tracker? My sourceforge username is janek-warchol. thanks, Janek ___ lilypond-deve

Avoid a few trivial lambda function wrappers (issue 306710043 by d...@gnu.org)

Good call, thanks! https://codereview.appspot.com/306710043/diff/1/ly/music-functions-init.ly File ly/music-functions-init.ly (right): https://codereview.appspot.com/306710043/diff/1/ly/music-functions-init.ly#newcode1656 ly/music-functions-init.ly:1656: coords offsets))) Now the line-breaks ca

Re: Akkordzither-tab in lilypond proper?

On 22.10.2016 10:00, Thomas Morley wrote: Hi, I recently mentioned my work to create the very special notation for Akkordzither. http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html I consider to put it in the source, probably in the same way we have gregorian.ly. I think Gre

Re: Whiteout / LyricHyphen

On 02.11.2016 21:36, Carl Sorensen wrote: So I don't know whether to say "include the code because we need the functionality" or "keep it out, because we don't want to break consistency". Consistency has already been broken in the 2.19 series, and for good reason. The precise form of the white

Re: Stepping down and moving on

Hi David, wow! Congratulations on the new job, and on having made that decision! Thanks a million for all the work and dedication you put into LilyPond and into the community. It was extremely valuable. All the best for your way ahead, cordially Simon On 09.11.2016 18:09, David Kastrup wrot

Re: Stepping up, contributor mentoring

On 30.11.2016 00:40, David Kastrup wrote: Graham Percival writes: Hi all, I'm back. Excellent news that could not have come at a better time. So, are there any vacancies on the Bug Squad? I vaguely fear so. In spite of the Bug Squad's importance I've been lousy at keeping track of it and

Re: unfoldRepeats can be restricted to certain repeat-types (issue 318890043 by thomasmorle...@gmail.com)

Hi Harm, thanks for the patch. As for the user-interface, I’d prefer something like \unfoldRepeats tremolo \m \unfoldRepeats volta,tremolo \m IIUC, that would require using predicate symbol-or-symbol-list? for the optional argument. (I hope that works… didn’t test TBH) Also, I think we shoul

Re: Doc CG 6.1: Add caveat on website work (issue 315130043 by gra...@percival-music.ca)

On 05.12.2016 09:24, Urs Liska wrote: If this intends to codify the website being tied to the documentation I don't really like that. It intends to prevent further loops of discussing this with new contributors and having a place in the docs to point to. It’s only intended to clarify the curr

Re: music function to be included somewhere in scm/*

On 14.12.2016 14:54, Knut Petersen wrote: With a music function \autoextenders that adds extender events to every syllable you - can be sure never to forget extenders, - can be sure never to generate too short extenders - can use the same lyrics definition for voices that require extenders at d

Re: music function to be included somewhere in scm/*

On 15.12.2016 13:34, Knut Petersen wrote: After a bit of thinking I'd say: go the radical route. Attached is a patch against current master that implements it that way. I like it, and I’d say: go ahead. Best, Simon ___ lilypond-devel mailing list l

Re: music function to be included somewhere in scm/*

On 15.12.2016 01:34, Alexander Kobel wrote: any use case for hyphen + extender? No. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: music function to be included somewhere in scm/*

On 15.12.2016 17:17, Francisco Vila wrote: I think lyrics extenders are meant only for the last syllable of a word. Of course they are. That’s why the proposed code checks for any hyphens before adding an extender. Any syllable which is not the last of a word must have a hyphen. Best, Simon

Re: music function to be included somewhere in scm/*

On 15.12.2016 17:45, Alexander Kobel wrote: (1) You can put the lyrics to all voices, as extenders are only printed on melismata (unless explicitly enforced). (2) You don't have to add __ in your lyrics anymore - it's done automagically (unless explicitly disabled). (3) minimum-length (or some o

Re: music function to be included somewhere in scm/*

On 16.12.2016 08:30, Marc Hohl wrote: Am 16.12.2016 um 02:09 schrieb Alexander Kobel: Hi all. [...] What about hide-below-length or hide-if-shorter-than? minimum-visibility? We’re getting closer… I think ‘threshold’ describes the functionality well; maybe visibility-threshold? printing-th

Re: music function to be included somewhere in scm/*

On 17.12.2016 00:23, Trevor Daniels wrote: How about "collapse-length", which would be analogous to "collapse-height"? +1 Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [PATCH] Automatic lyric extenders

On 22.12.2016 02:17, Thomas Morley wrote: 2016-12-22 1:33 GMT+01:00 Knut Petersen: Hi everybody! Attached find a new version of the patch. Please test. Read the updated manuals. Feel free to provide corrections and translations! cu, Knut Hi Knut, how about putting the patch on Rietveld?

Re: Two small amendments to Doc/web/community.itexi (issue 319880043 by simon.albre...@mail.de)

On 22.12.2016 23:21, gra...@percival-music.ca wrote: https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi File Documentation/web/community.itexi (right): https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi#newcode434 Documentation

Re: Delete new LSR-snippet?

On 23.12.2016 12:42, Thomas Morley wrote: with http://lsr.di.unimi.it/LSR/Item?u=1&id=1049 a new snippet arrived. Though, it only demonstrates how to use 'extra-offset, imho. And very poorly – how the staff lines resurface after the text script… This is definitely not showcase-able and I agree

\arrow markup command

Hello, I have just been annoyed by the fact that it takes four commands (\combine, \arrow-head, \override, and \draw-line) to draw an acceptable arrow-head (\override is to match the thickness of the line to the Feta glyph), so I proceeded to code an \arrow markup command simplifying the use.

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

On 23.12.2016 22:36, Alexander Kobel wrote: The corresponding issue can be found at https://sourceforge.net/p/testlilyissues/issues/5018/ …which I took the liberty to merge with . Thanks for the work and happy holidays as well! Best, Sim

Re: \arrow markup command

Hello again, I created a better preview image and on the way noticed that a small adjustment is necessary, so that the line doesn’t obstruct the finer tip of the filled arrow head. Best, Simon arrow.pdf Description: Adobe PDF document \version "2.19.53" \header { tagline = ##f } \paper {

Free alternatives to Rietveld?

Hello everybody, just now I tried to login with Google in order to close my two recent Rietveld reviews. However, Google decided that despite entering a verification code from e-mail it couldn’t confirm me being authorised to login. So I’m currently out. Maybe they want to force me to give a

Re: Free alternatives to Rietveld?

On 27.12.2016 14:09, Urs Liska wrote: While we're at it: is there really no tool that integrates with Git directly? I find it pretty inconvenient and partly unreliable that the author is responsible himself that what is pushed actually is what has been reviewed. Well, I had a brief look at so

Arrow-glyphs in Feta (was: \arrow markup command)

On 23.12.2016 22:34, Simon Albrecht wrote: Why does the Feta font have one glyph for each of the 4 directions in which an arrow head generated with \arrow-head can point? Why not simply rotate one glyph in the first place? (I’m sure the Metafont code does just that, though it would strike me

  1   2   3   >