Re: Fwd: MusicXML

Hi David, nice to read that. I think coming to GSoC with an idea is more important than the listed mentor availability. Continuing on the Scheme/XML track would be very rewarding. However, for some reasons I'd try to go into a more generic direction. This could be very suitable for

Fwd: MusicXML

Hi there! Hope everyone had a lovely new year. School has kept me busy, but I'm still interested in continuing work on the MusicXML project that I started over the summer. I just caught up in mailing-list readings for the topic, so I think I'm correct in assuming that it hasn't been added to the

Re: hyphen syntax

On Feb 17, 2016, at 18:17 , David Kastrup wrote: > > I think the main problem we should aim to solve is that the occasional > user just does not remember what's what. __ is a lyric extender, -- is > a lyric hyphen, _ is a non-syllable-separating space, - is a normal > dash, ~ is

(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: hyphen syntax

Noeck writes: > Hi Simon, > >> 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 font).’ I didn’t mean ‘advanced’ in >> the sense of ‘only

Re: Doc: NR renamed New spacing area node (issue 283350043 by pkx1...@gmail.com)

On 2016/02/17 18:45:24, tisimst wrote: Minor punctuation suggestion, otherwise LGTM. https://codereview.appspot.com/283350043/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right):

Re: hyphen syntax

Hi Simon, > 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 font).’ I didn’t mean ‘advanced’ in > the sense of ‘only for advanced users’ or ‘rare’. I know. I'm

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

Re: LilyPond as a service

Urs Liska writes: > I know this has been discussed in various flavors over the years, but I > need to raise the issue once more. Please note that this actually > encloses two questions. > > Would it be possible to make LilyPond work in a server mode where the > whole Guile

Re: hyphen syntax

Hi, Am 17.02.2016 um 17:54 schrieb Simon Albrecht: > And I think the double items suit the advanced functionality better I thought about this when Dan wrote his first mail, but I wanted to keep my comment short. I think many of you know the fun you can have with backslashes and escaping (as in

Re: LilyPond as a service

On Wed, Feb 17, 2016 at 2:51 PM, Urs Liska [via Lilypond] < ml-node+s1069038n187406...@n5.nabble.com> wrote: > I'm sorry but I don't get this. > Urs > > > Am 17.02.2016 um 22:48 schrieb Abraham Lee: > > > This sounds a lot like lilybin.com > You know what, I probably jumped

Re: LilyPond as a service

I'm sorry but I don't get this. Urs Am 17.02.2016 um 22:48 schrieb Abraham Lee: > This sounds a lot like lilybin.com ... > > - Abraham > > On Wed, Feb 17, 2016 at 2:45 PM, Urs Liska > wrote: > > I know this has been

Re: LilyPond as a service

This sounds a lot like lilybin.com... - Abraham On Wed, Feb 17, 2016 at 2:45 PM, Urs Liska wrote: > I know this has been discussed in various flavors over the years, but I > need to raise the issue once more. Please note that this actually > encloses two questions. > >

LilyPond as a service

I know this has been discussed in various flavors over the years, but I need to raise the issue once more. Please note that this actually encloses two questions. Would it be possible to make LilyPond work in a server mode where the whole Guile environment is loaded only once and the running

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 LyricText font rather

Re: Doc section name change proposition

Hello, On 17/02/16 17:16, Phil Holmes wrote: - Original Message - From: "Abraham Lee" To: "LilyPond Development Team" Sent: Wednesday, February 17, 2016 4:35 PM Subject: Doc section name change proposition Docs Team, I noticed

Re: Doc section name change proposition

On Wed, Feb 17, 2016 at 10:17 AM, Phil Holmes-2 [via Lilypond] < ml-node+s1069038n18738...@n5.nabble.com> wrote: > - Original Message - > From: "Abraham Lee" <[hidden email] > > > To: "LilyPond Development Team" <[hidden email] >

Re: hyphen syntax

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 LyricText font > rather > > than a dashed line. I

Re: Doc section name change proposition

- Original Message - From: "Abraham Lee" To: "LilyPond Development Team" Sent: Wednesday, February 17, 2016 4:35 PM Subject: Doc section name change proposition Docs Team, I noticed this a while back, but I thought I might as well

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

Re: hyphen syntax

Simon Albrecht writes: > 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

Re: hyphen syntax

On Wed, Feb 17, 2016 at 9:54 AM, Simon Albrecht-2 [via Lilypond] < ml-node+s1069038n187380...@n5.nabble.com> wrote: > On 17.02.2016 15:58, David Kastrup wrote: > > > Dan Eble<[hidden email] > > writes: > > > >>> >>On Feb 17, 2016, at 05:18 ,

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

Re: When to start patch review

Am 17.02.2016 um 17:47 schrieb Simon Albrecht: >> Waiting for a patch like that to pass before review is pointless if >> there is going to be a reluctance or even refusal to allow it to make >> it to master in the end. >> >> However, is there a particular reason for this question? > > No, just

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

Doc section name change proposition

Docs Team, I noticed this a while back, but I thought I might as well bring it up. Subsubsection 4.5.2 in NR is called "New spacing area", but the command it introduces is called "\newSpacingSection". In favor of not changing the command name, can we rename the section to match the command? In

Re: hyphen syntax

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? >>> >> >>

Re: hyphen syntax

> 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? >> > > Technically, I don't know. But, in terms of

Re: hyphen syntax

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? Technically, I don't know. But, in terms of coherence, I would leave it as it is: one hyphen is treated as one syllable, just like one

Re: Doc: CG Updated section 1.3 - experienced devs (issue 287110043 by pkx1...@gmail.com)

Thanks for reviewing Simon. https://codereview.appspot.com/287110043/diff/20001/Documentation/contributor/introduction.itexi File Documentation/contributor/introduction.itexi (right): https://codereview.appspot.com/287110043/diff/20001/Documentation/contributor/introduction.itexi#newcode120

Re: When to start patch review

Simon, 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 reg test diffs, but I do get