Re: Slurs do not work with Larsen articulations

Noeck writes: > Hi Harm, > > IMHO that's a good explanation and according to the recurring questions > on this list, sth. that would be helpful. > > I like the "attached to the note" much better than "not enclosed in" > because the negative wording "not enclosed in" only

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > 2018-04-25 23:23 GMT+02:00 Carl Sorensen : >> >> >> On 4/25/18, 2:34 PM, "David Kastrup" wrote: >> >> So I see it more as a documentation challenge than a design failure. >> >> >> I agree, and I think we

Re: Slurs do not work with Larsen articulations

On 25.04.2018 23:29, Noeck wrote: c'8-1--(~\markup "what-ever-remark" c') The markup needs a hyphen. I'd suggest to drop the \markup here to make it simpler. In my personal rule set, the ~ goes last – but there is probably no reason for that … One thing does have to go last, and that is

Re: Slurs do not work with Larsen articulations

On 25.04.2018 12:48, foxfanfare wrote: But for instance in the Available Music Functions section, sometimes there is a small code exemple, sometime there isn't (almost evry time). I found personnaly clearer

Re[2]: Slurs do not work with Larsen articulations

Robert Hickman wrote 25/04/2018 19:16:41 It is quite apparent that this wasn't written for random access and I feel that websites are much more effective and user friendly if they are. Whether it is apparent to you or not I can tell you categorically as one of the original authors what the

"Random" access (was: Slurs do not work with Larsen articulations)

Evan Driscoll <eva...@gmail.com>, Lilypond-User Mailing List <lilypond-user@gnu.org> > Bcc: > Date: Wed, 25 Apr 2018 18:30:38 +0000 > Subject: Re: Slurs do not work with Larsen articulations > > > On 4/25/18, 12:16 PM, "Robert Hickman" <robehick...@gmail.com&

Re: Slurs do not work with Larsen articulations

On 4/25/2018 5:03 PM, Robert Hickman wrote: Just including a note at the top of all of the pages "this is the learning manual and is intended to be read start to finish" would help clarify that. -- Karlin

Re: Slurs do not work with Larsen articulations

"As we try to make clear, the Learning Manual is intentionally not built for random access. The Notation Reference *is* built for random access." However it frequently shows up in google search results out of order and the way it is written mean that these pages often don't make sense. Just

Re: Slurs do not work with Larsen articulations

2018-04-25 23:23 GMT+02:00 Carl Sorensen : > > > On 4/25/18, 2:34 PM, "David Kastrup" wrote: > > So I see it more as a documentation challenge than a design failure. > > > I agree, and I think we can improve the documentation. > > Carl > > startSlur,

Re: Slurs do not work with Larsen articulations

Hi Harm, IMHO that's a good explanation and according to the recurring questions on this list, sth. that would be helpful. I like the "attached to the note" much better than "not enclosed in" because the negative wording "not enclosed in" only tells what you _should not_ do and not what you

Re: Slurs do not work with Larsen articulations

On 4/25/18, 2:34 PM, "David Kastrup" wrote: So I see it more as a documentation challenge than a design failure. I agree, and I think we can improve the documentation. Carl ___ lilypond-user mailing list

Re: Slurs do not work with Larsen articulations

Carl Sorensen writes: > On 4/25/18, 1:46 PM, "Thomas Morley" wrote: > > > There is a point that I was trying to make with these changes, > > without jumping right out and saying it (because I couldn’t find > > a good place to jump

Re: Slurs do not work with Larsen articulations

On 4/25/18, 1:46 PM, "Thomas Morley" wrote: > There is a point that I was trying to make with these changes, without jumping right out and saying it (because I couldn’t find a good place to jump out and say it). In LilyPond, *ALL* extra things that apply

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > Hi Carl, > > 2018-04-25 13:26 GMT+02:00 Carl Sorensen : >> Evan, >> >> Thanks for your feedback. Feedback from new users is important for >> improving the Learning Manual. > > Indeed. > >> There is a point that I was trying

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > Sometimes I think using "(" and ")" to indicate slurs leads to > misunderstandings, they are read as a sort of brackets (they are not) > Ofcourse it's conveniant, but I wonder, if doing like below would lead > to the same misinterpretation: > >

Re: Slurs do not work with Larsen articulations

ieren MacMillan > <kieren_macmil...@sympatico.ca>, David Kastrup <d...@gnu.org>, Lilypond-User > Mailing List <lilypond-user@gnu.org> > Subject: Re: Slurs do not work with Larsen articulations > > > > > > That sounds good to me. > > Thanks fo

Re: Slurs do not work with Larsen articulations

Hi Carl, 2018-04-25 13:26 GMT+02:00 Carl Sorensen : > Evan, > > Thanks for your feedback. Feedback from new users is important for improving > the Learning Manual. Indeed. > There is a point that I was trying to make with these changes, without > jumping right out and

Re: Slurs do not work with Larsen articulations

r Mailing List <lilypond-user@gnu.org> Subject: Re: Slurs do not work with Larsen articulations That sounds good to me. Thanks for the feedback. In case it's not clear, my pseudo-objection to the wording +Note that @code{[} and @code{]} do not enclose the notes to be +slurred. is that the ( an

Re: Slurs do not work with Larsen articulations

\On 4/25/18, 12:16 PM, "Robert Hickman" wrote: I assume that the project still has contributors who work on the documentation? It dosn't really matter if they are the original authors of it. I'm not saying that it is terible, but making some points

Re: Slurs do not work with Larsen articulations

On Wed, Apr 25, 2018 at 6:26 AM, Carl Sorensen wrote: > Thanks for your feedback. Feedback from new users is important for > improving the Learning Manual. > Just so we're on the same page, I've been an occasional LilyPond user for many many years now; I was just saying

Re: Slurs do not work with Larsen articulations

On 4/25/18, 12:16 PM, "Robert Hickman" wrote: It is quite apparent that this wasn't written for random access and I feel that websites are much more effective and user friendly if they are. As we try to make clear, the Learning Manual is intentionally not

Re: Slurs do not work with Larsen articulations

It is quite apparent that this wasn't written for random access and I feel that websites are much more effective and user friendly if they are. "It's easy to wave your hands and say "not good, I want you all to redo it better" but that will not result in changes getting done," I assume that the

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > On 25 April 2018 at 18:44, Karlin High wrote: >> On 4/25/2018 12:38 PM, Kieren MacMillan wrote: >>> >>> Hi Robert, >>> Many pages duplicate content or say 'please read page xyz first' because I recognise that people

Re: Slurs do not work with Larsen articulations

On 25 April 2018 at 18:44, Karlin High wrote: > On 4/25/2018 12:38 PM, Kieren MacMillan wrote: >> >> Hi Robert, >> >>> Many pages duplicate content or say 'please read page xyz first' >>> because I recognise that people will enter the site from any page >>> and I cannot make

Re: Slurs do not work with Larsen articulations

On 4/25/2018 12:38 PM, Kieren MacMillan wrote: Hi Robert, Many pages duplicate content or say 'please read page xyz first' because I recognise that people will enter the site from any page and I cannot make any assumptions about what they already know. This is a great suggestion. Perhaps you

Re: Slurs do not work with Larsen articulations

Hi Robert, > Many pages duplicate content or say 'please read page xyz first' > because I recognise that people will enter the site from any page > and I cannot make any assumptions about what they already know. This is a great suggestion. Perhaps you can contribute such links as you continue

Re: Slurs do not work with Larsen articulations

" In the context of the Learning Manual, pitches and durations are introduced in section 1.2.1. It seems like it would be unfriendly to clutter that section with a discussion about modifications coming after the note. " The problem with this attitude is that it is a website and people will enter

Re: Slurs do not work with Larsen articulations

Sorry to jump in here as someone who just (re-)signed up for the list, but I actually find +Note that @code{[} and @code{]} do not enclose the notes to be +slurred. potentially confusing. I would say something like either "Note that the first note of the slur appears before the opening @code{(}"

Re: Slurs do not work with Larsen articulations

, Kieren MacMillan <kieren_macmil...@sympatico.ca>, David Kastrup <d...@gnu.org>, Lilypond-User Mailing List <lilypond-user@gnu.org> Subject: Re: Slurs do not work with Larsen articulations Sorry to jump in here as someone who just (re-)signed up for the list, but I actually find

Re: Slurs do not work with Larsen articulations

David Kastrup wrote > That's actually the killer reason. There are a few places where > documentation strings get drawn into the manual, and those documentation > strings can be used more and less tersely. They should be verbose > enough to be useful which may include examples (examples take up

Re: Slurs do not work with Larsen articulations

Simon Albrecht writes: > On 24.04.2018 22:02, foxfanfare wrote: >> I missed >> more exemples in the huge "Internal Manual"! > > I don’t think any will be added, for two reasons: > The technical reason is that the Internals Reference is auto-generated > from the program

Re: Slurs do not work with Larsen articulations

Here's a proposed patch for the documentation. I haven't posted it on Rietveld because I'm having some problems with make doc (that are unrelated to this change). -- a/Documentation/learning/common-notation.itely +++ b/Documentation/learning/common-notation.itely @@ -275,6 +275,9 @@ Notation

Re: Slurs do not work with Larsen articulations

On 24.04.2018 22:02, foxfanfare wrote: I missed more exemples in the huge "Internal Manual"! I don’t think any will be added, for two reasons: The technical reason is that the Internals Reference is auto-generated from the program code, so possibilities to manually add stuff are very

Re: Slurs do not work with Larsen articulations

If I may intervene here: about the documentation quality, I'd must say I disagree. As I said in another post, I find it (globaly) very high ended. I started LP about 3 weeks from now, I'm just finishing the full notation PDF book of almost 900 pages! Of course, I still have a lot more to learn

Re: Slurs do not work with Larsen articulations

On Tue, Apr 24, 2018 at 1:58 PM, David Kastrup wrote: > Except when it's a clever way of getting rid of an unwanted semicolon. > Or in this case, create a semicolon hole, a negative semicolon count. > Add one semicolon, and none remains. :) Clean forgot about macros in C. I stand

Re: Slurs do not work with Larsen articulations

Karlin High writes: > On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: >> The only way to create good documentation is to listen to your users >> problems and progressively make improvements. > > Yes, exactly! The LilyPond community has a

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > The only way to create good documentation is to listen to your users > problems and progressively make improvements. "your users" paints a false dichotomy. There is no fundamental difference between you and anybody else writing documentation. --

Re: Slurs do not work with Larsen articulations

Hi Robert (and Karlin), >> Whatever help I would get from the C-people, getting rid >> of the semicolons would not be part of it. > > This is **NOT** the point I am making No, of course not — I would imagine Karlin was simply responding to your comment > Personally I prefer the syntax

Re: Slurs do not work with Larsen articulations

On 24 April 2018 at 16:18, Karlin High wrote: > On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: >> The only way to create good documentation is to listen to your users >> problems and progressively make improvements. > > Yes, exactly! The

Re: Slurs do not work with Larsen articulations

On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: > The only way to create good documentation is to listen to your users > problems and progressively make improvements. Yes, exactly! The LilyPond community has a process for this.

Re: Slurs do not work with Larsen articulations

The only way to create good documentation is to listen to your users problems and progressively make improvements. On 24 April 2018 at 14:49, Kieren MacMillan wrote: > Hi Robert, > >> If I misinterpreted it you can guarantee >> that other people are also doing so.

Re: Slurs do not work with Larsen articulations

Hi Robert, > If I misinterpreted it you can guarantee > that other people are also doing so. Well, that’s a faulty generalization… ;) … but IMO more clarity is always better. As they say: "Patches [to the docs] are always gratefully accepted." Cheers, Kieren.

Re: Slurs do not work with Larsen articulations

> The example looks pretty clear to me. "marked with" is not really > synonymous with "surrounded with" in my book even though it could be > more explicit about just how the marks are supposed to be made. > If I misinterpreted it you can guarantee that other people are also doing so. The

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > Personally I prefer the syntax used by ABC notation, with all notes of > a slur inside the parans, but I don't see it being changed at this > point. How does this work for consecutive slurs, like LilyPond's { c4( d)( e2) } ? { (c4 (d) e2) }

Re: Slurs do not work with Larsen articulations

On 24 April 2018 at 14:25, Kieren MacMillan wrote: > Hi Robert, > >> Instead the correct syntax should be: >> >> g (b d g) > > No… the correct syntax is > > g( b d g) > > The ( is attached, postfix, to the first note of the slurred group. Stating that in the

Re: Slurs do not work with Larsen articulations

Hi Robert, > Instead the correct syntax should be: > > g (b d g) No… the correct syntax is g( b d g) The ( is attached, postfix, to the first note of the slurred group. Hope this helps! Kieren. Kieren MacMillan, composer ‣ website:

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > Actually it's a misinterpretation. The documentation does not make it > clear that the start of the slur should be after the first note of the > slur. > > a'2 (a'4 a'4 ) What documentation are you talking about here? -- David Kastrup

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > The documentation says that slurs can be created by putting notes > within '()' What documentation would state that? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Slurs do not work with Larsen articulations

Hi Karlin "Unclear documentation can be improved. Need a reference for it, though; where was this found?" I'm talking about the following page: http://lilypond.org/doc/v2.16/Documentation/learning/ties-and-slurs.en.html The page states: "A slur is a curve drawn across many notes. The starting

Re: Slurs do not work with Larsen articulations

On 4/24/2018 7:57 AM, Robert Hickman wrote: The documentation does not make it clear that the start of the slur should be after the first note of the slur. Unclear documentation can be improved. Need a reference for it, though; where was this found? -- Karlin High Missouri, USA

Re: Slurs do not work with Larsen articulations

Actually it's a misinterpretation. The documentation does not make it clear that the start of the slur should be after the first note of the slur. a'2 (a'4 a'4 ) On 24 April 2018 at 13:50, Robert Hickman wrote: > The documentation says that slurs can be created by

Slurs do not work with Larsen articulations

The documentation says that slurs can be created by putting notes within '()' however this does not work in combination with the Larsen articulation symbols: { (a'2 a'4\cut a'4\strike) } I get the following error: error: syntax error, unexpected EVENT_IDENTIFIER (a'2 a'4\cut