Re: typo LilyPond Internals

Hello, On 29/12/2020 01:31, Freeman Gilmore wrote: LilyPond Internals Reference, 2.2.58 key_engraver keyAlterationOrder(list) It should read: "… *step *is a number from 0 to 6 and *alter *from -2 (flat) to 2 (sharp)." (Not -2 (sharp) to 2 (flat).) Thank you, ƒg

Re: typo LilyPond Internals

On 2020-12-28 6:18 pm, Aaron Hill wrote: On 2020-12-28 5:31 pm, Freeman Gilmore wrote: LilyPond Internals Reference, 2.2.58 key_engraver keyAlterationOrder(list) It should read: "… *step *is a number from 0 to 6 and *alter *from -2 (flat) to 2 (sharp)." (Not -2

Re: typo LilyPond Internals

On 2020-12-28 5:31 pm, Freeman Gilmore wrote: LilyPond Internals Reference, 2.2.58 key_engraver keyAlterationOrder(list) It should read: "… *step *is a number from 0 to 6 and *alter *from -2 (flat) to 2 (sharp)." (Not -2 (sharp) to 2 (flat).) What version of the docs

typo LilyPond Internals

LilyPond Internals Reference, 2.2.58 key_engraver keyAlterationOrder(list) It should read: "… *step *is a number from 0 to 6 and *alter *from -2 (flat) to 2 (sharp)." (Not -2 (sharp) to 2 (flat).) Thank you, ƒg ___ bug-lilypond

Re: Typo on German page http://lilypond.org/doc/v2.21/Documentation/notation/unpure_002dpure-containers

Am 28.10.2020 um 15:25 schrieb Johannes Feulner: Instead of "Zusammenstoßf" it should be "Zusammenstoß" Fixed in 'translation'. Thanks for reporting! Michael ___ bug-lilypond mailing list bug-lilypond@gnu.org

Typo on German page http://lilypond.org/doc/v2.21/Documentation/notation/unpure_002dpure-containers

Instead of "Zusammenstoßf" it should be "Zusammenstoß" -- Johannes Feulner Tel: +49 721 33500158 johannes.feul...@scorio.com scorio GmbH Bonhoefferweg 3 76327 Pfinztal Geschäftsführer Johannes Feulner Sitz der Gesellschaft Karlsruhe Amtsgericht Mannheim HRB 713486

Re: Doc typo

Thank you David. Le ven. 5 avr. 2019 à 23:16, David Kastrup a écrit : > Pierre Perol-Schneider writes: > > >> Le ven. 5 avr. 2019 à 17:33, David Kastrup a écrit: > >> > >>> Pierre Perol-Schneider writes: > >>> > >>> > Hi Bug Squad, > >>> > > >>> > In LM 2.18, A.10.3 & LM 2.19, A.11.3

Re: Doc typo

Pierre Perol-Schneider writes: >> Le ven. 5 avr. 2019 à 17:33, David Kastrup a écrit: >> >>> Pierre Perol-Schneider writes: >>> >>> > Hi Bug Squad, >>> > >>> > In LM 2.18, A.10.3 & LM 2.19, A.11.3 (graphic), above "\oval arg" >>> > It shows: >>> > "[...] Use thickness, x-padding, x-padding and

Re: Doc typo

Oops, sorry, "LM" was for LilyPond Manual. Anyway, no push from here possible, that's why I asked the squad. Le ven. 5 avr. 2019 à 17:33, David Kastrup a écrit : > Pierre Perol-Schneider writes: > > > Hi Bug Squad, > > > > In LM 2.18, A.10.3 & LM 2.19, A.11.3 (graphic), above "\oval arg" > >

Re: Doc typo

Pierre Perol-Schneider writes: > Hi Bug Squad, > > In LM 2.18, A.10.3 & LM 2.19, A.11.3 (graphic), above "\oval arg" > It shows: > "[...] Use thickness, x-padding, x-padding and [...]" > Instead of: > "[...] Use thickness, x-padding, y-padding and [...]" That's not LM but NR. Pushed a fix. --

Doc typo

Hi Bug Squad, In LM 2.18, A.10.3 & LM 2.19, A.11.3 (graphic), above "\oval arg" It shows: "[...] Use thickness, x-padding, x-padding and [...]" Instead of: "[...] Use thickness, x-padding, y-padding and [...]" Cheers, Pierre ___ bug-lilypond mailing

Re: Doc: typo in keyboards.itely

Federico Bruni writes: > $ git grep -n tremelo > Documentation/notation/keyboards.itely:644:@item A > @notation{bisbigliando} is written as a tremelo @ref{Tremolo > > tremelo > tremolo > > Can anybody push a fix? Pushed to staging. -- David Kastrup

Doc: typo in keyboards.itely

$ git grep -n tremelo Documentation/notation/keyboards.itely:644:@item A @notation{bisbigliando} is written as a tremelo @ref{Tremolo tremelo > tremolo Can anybody push a fix? Thanks Federico ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: DOC: Typo in CG 2.2 Where to get lily-git, "auxiliar" not "auxillar"

> lily-git is part of the LilyPond source code and is located in > ‘$LILYPOND_GIT/scripts/auxillar/lily-git.tcl’. > > But since it's command text, I tripped over it. I remember reading > that the main LilyPond contributors have a process to fix typos > directly, without the review cycle? I'll

DOC: Typo in CG 2.2 Where to get lily-git, "auxiliar" not "auxillar"

It's just ONE letter: lily-git is part of the LilyPond source code and is located in ‘$LILYPOND_GIT/scripts/auxillar/lily-git.tcl’. But since it's command text, I tripped over it. I remember reading that the main LilyPond contributors have a process to fix typos directly, without the review

Re: typo in german manual

Jens Dencker writes: > Und noch ein Fund: > > Kapitel http://lilypond.org/doc/v2.18/Documentation/ > notation/common-notation-for-fretted-strings > Abschnitt Vordefinierte Bund-Diagramme > > vortdefinierten -> vordefinierten Pushed those two to staging as well. To be honest,

Re: typo in german manual

Und noch ein Fund: Kapitel http://lilypond.org/doc/v2.18/Documentation/ notation/common-notation-for-fretted-strings Abschnitt Vordefinierte Bund-Diagramme vortdefinierten -> vordefinierten Grüße, Jens Dencker Am 9. März 2017 um 18:36 schrieb Jens Dencker : > Und noch ein

Re: typo in german manual

Und noch ein Fund: Kapitel http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-fretted-strings Abschnitt Standardtabulaturen verändernt -> verändern Grüße, Jens Dencker Am 3. März 2017 um 15:05 schrieb Jens Dencker : > Und noch ein Fund: > > Kapitel

Re: typo in german manual

Jens Dencker writes: > Moin, > > auf der Seite > > http://lilypond.org/doc/v2.18/Documentation/notation/common- > notation-for-vocal-music > > habe ich einige Schreibfehler gefunden: > könn -> können > sichergestell -> sichergestellt > > Dann noch etwas: > > > Auch ein Punkt,

Re: typo in german manual

Moin, auf der Seite http://lilypond.org/doc/v2.18/Documentation/notation/common- notation-for-vocal-music habe ich einige Schreibfehler gefunden: könn -> können sichergestell -> sichergestellt Dann noch etwas: Auch ein Punkt, der auf eine Silbe folgt, wird in die Silbe inkorporiert.

Re: typo in german manual

Und noch ein Fund: Kapitel http://lilypond.org/doc/v2.18/Documentation/learning/vocal-ensembles Abschnitt A.4.6 Hymnen Im ersten Absatz: Zeiel -> Zeile Grüße, Jens Dencker Am 3. März 2017 um 11:01 schrieb Jens Dencker : > Moin, > > auf der Seite > >

typo in german manual

Hallo, I explain in German because I found it in German manual... Im Abschnitt 1.1.2 Viele Tonhöhen gleichzeitig verändern http://lilypond.org/doc/v2.18/Documentation/notation/changing-multiple-pitches.de.html Unterabschnitt Transposition, vorletzter Absatz. Bitte ersetzen: \tranpose durch

Re: typo in NR 3.2.6, input.itely

On 28/11/15 21:13, Federico Bruni wrote: > Hi > > In this line of Documentation/notation/input.itely: > > \tocItem \markup { Cesare. Presti omai l'Egizzia terra } > > Egizzia should be changed to Egizia > > Can anybody just fix and push it? I'll make a patch (and an issue) and include it with

Re: typo in NR 3.2.6, input.itely

Hello, On 29/11/15 13:04, James Lowe wrote: > On 28/11/15 21:13, Federico Bruni wrote: >> Hi >> >> In this line of Documentation/notation/input.itely: >> >> \tocItem \markup { Cesare. Presti omai l'Egizzia terra } >> >> Egizzia should be changed to Egizia >> >> Can anybody just fix and push it?

typo in NR 3.2.6, input.itely

Hi In this line of Documentation/notation/input.itely: \tocItem \markup { Cesare. Presti omai l'Egizzia terra } Egizzia should be changed to Egizia Can anybody just fix and push it? ___ bug-lilypond mailing list bug-lilypond@gnu.org

minor typo in NR 1.1.1 - Relative Octave Entry

While translating, I saw a closing bracket ) that someone forgot deleting: http://lilypond.org/doc/v2.19/Documentation/notation/writing-pitches.html#relative-octave-entry no explicit starting pitch The form \relative { gis''' … }) serves as Can anyone fix it and push it to staging?

Re: minor typo in NR 1.1.1 - Relative Octave Entry

Hello, On 28/10/15 14:27, Federico Bruni wrote: > While translating, I saw a closing bracket ) that someone forgot > deleting: > http://lilypond.org/doc/v2.19/Documentation/notation/writing-pitches.html#relative-octave-entry > > > no explicit starting pitch > >The form \relative { gis''' … })

Re: Small typo in german version of Notationsreferenz, header 2.9.3

On Thu, Jul 9, 2015 at 3:03 AM, Michael Gerdau m...@qata.de wrote: Hi Lilypond documentation team, in the german version of the Notationsreferenz, Headline 2.9.3 reads 2.9.3 Mesurale Musik setzen and it should be 2.9.3 Mensurale Musik setzen (an n is missing in Mensurale) The URL is

Re: Small typo in german version of Notationsreferenz, header 2.9.3

Il giorno ven 10 lug 2015 alle 13:49, Ralph Palmer ralphbugl...@gmail.com ha scritto: Greetings, Michael, documentation team, and LilyPonders - Thanks for the email, Michael. I'm not sure if the bug list is the correct place to submit this, but I do not know of any list specific to

Small typo in german version of Notationsreferenz, header 2.9.3

Hi Lilypond documentation team, in the german version of the Notationsreferenz, Headline 2.9.3 reads 2.9.3 Mesurale Musik setzen and it should be 2.9.3 Mensurale Musik setzen (an n is missing in Mensurale) The URL is

Re: Learning manual, v2.18/v2.19 typo

-and-functions.html There's a typo down here: violin = \relative c'' { \repeat volta 2 { c4._\markup { \italic \bold dolce } b8 a8 g a b | \once \override TextScript.padding = #5.0 c4.^hi there! d8 e' f g d | % c,4.\markup { %% = 'c,4.-\markup

Re: Learning manual, v2.18/v2.19 typo

://www.lilypond.org/doc/v2.19/Documentation/learning/saving-typing-with-variables-and-functions.html There's a typo down here: violin = \relative c'' { \repeat volta 2 { c4._\markup { \italic \bold dolce } b8 a8 g a b | \once \override TextScript.padding = #5.0 c4.^hi there! d8 e' f g d

Learning manual, v2.18/v2.19 typo

I'm not top posting. Dear Bug Squad, On this page: http://www.lilypond.org/doc/v2.19/Documentation/learning/saving-typing-with-variables-and-functions.html There's a typo down here: violin = \relative c'' { \repeat volta 2 { c4._\markup { \italic \bold dolce } b8 a8 g a b | \once

Re: Typo in NR example (vocal music)

On Wed, Jan 7, 2015 at 4:50 AM, Urs Liska u...@openlilylib.org wrote: Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common- notation-for-vocal-music.html there's a typo in the example about special characters (with the text Schad' um das schöne grüne Band). The sixth

Re: Typo in NR example (vocal music)

Am 09.01.2015 um 16:00 schrieb Ralph Palmer: On Wed, Jan 7, 2015 at 4:50 AM, Urs Liska u...@openlilylib.org mailto:u...@openlilylib.org wrote: Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music.html there's a typo in the example

Typo in NR example (vocal music)

Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music.html there's a typo in the example about special characters (with the text Schad' um das schöne grüne Band). The sixth note should read es' instead of e'. I'd fix that myself but I have problems

Re: typo in LM 2.18/2.19 (Contributor's guide)

Thanks Pierre There's already a patch: https://codereview.appspot.com/109140043/ Il 22/giu/2014 00:13 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: I'm not top posting. Hi Squad, See :

Re: typo in LM 2.18/2.19 (Contributor's guide)

Am 22.06.2014 12:51, schrieb Federico Bruni: Thanks Pierre There's already a patch: https://codereview.appspot.com/109140043/ And it's already pushed to staging :-) Il 22/giu/2014 00:13 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: I'm not top posting. Hi Squad,

typo in LM 2.18/2.19 (Contributor's guide)

I'm not top posting. Hi Squad, See : http://lilypond.org/doc/v2.19/Documentation/contributor/documentation-suggestions Go to : Contributions that contain examples using overrides 3rd paragraph : [...] Snippets that don’t have the “docs” tage [...] Cheers, Pierre

Re: LilyPond 2.19.6 released May 11, 2014 - typo

On 12/05/14 09:17, Phil Holmes wrote: Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote in message news:caphotuxeths_bjcdfcko5+wawiwucyz2cbds7vcoiue2suc...@mail.gmail.com... I'm not top posting Hi Squad, Hi Phil, There's a typo in the anouncement : *We are happy to announce

Re: LilyPond 2.19.6 released May 11, 2014 - typo

On 12/05/14 09:17, Phil Holmes wrote: Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote in message news:caphotuxeths_bjcdfcko5+wawiwucyz2cbds7vcoiue2suc...@mail.gmail.com... I'm not top posting Hi Squad, Hi Phil, There's a typo in the anouncement : *We are happy to announce

Re: LilyPond 2.19.6 released May 11, 2014 - typo

- Original Message - From: James pkx1...@gmail.com To: Phil Holmes m...@philholmes.net; bug-lilypond@gnu.org Sent: Monday, May 12, 2014 10:35 AM Subject: Re: LilyPond 2.19.6 released May 11, 2014 - typo On 12/05/14 09:17, Phil Holmes wrote: Pierre Perol-Schneider pierre.schneider.pa

LilyPond 2.19.6 released May 11, 2014 - typo

I'm not top posting Hi Squad, Hi Phil, There's a typo in the anouncement : *We are happy to announce the release of LilyPond 2.19.5* [...] Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug

[LSR v2.18] Setting the mimimum length of a fall/doit typo

Dear Bug Squad, there's a typo in the title of the following snippet : http://lsr.di.unimi.it/LSR/Item?id=565 please change it for Setting the minimum length of a fall/doit Thanks, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: Typo in performer-init.ly

kurivaim wrote In ../ly/performer-init.ly (file version 2.17.14, distributed with LilyPond version 2.18.0), at line 186 (in the NullVoice block), there is a typo. The file reads: \type Performer_Group But this should be: \type Performer_group The erroneous capital G leads

Re: [LSR v2.18] Setting the mimimum length of a fall/doit typo

Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote in message news:caphotuvvcjxyho2efe-5tycfd_a-acpugcauopoymsrsvx5...@mail.gmail.com... Dear Bug Squad, there's a typo in the title of the following snippet : http://lsr.di.unimi.it/LSR/Item?id=565 please change it for Setting

Re: [LSR v2.18] Setting the mimimum length of a fall/doit typo

Hi Phil, 2014-02-20 11:10 GMT+01:00 Phil Holmes m...@philholmes.net: Fixed now. Does it mean that I have to rename the file setting-the-minimum-length-of-a-fall-doit.ly ? ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: [LSR v2.18] Setting the mimimum length of a fall/doit typo

I don't know, to be honest. I wouldn't do that - I guess either it will happen automatically, or we can accept a typo in the file name. -- Phil Holmes - Original Message - From: Pierre Perol-Schneider To: Phil Holmes Cc: bug-lilypond Sent: Thursday, February 20, 2014 11

Re: [LSR v2.18] Setting the mimimum length of a fall/doit typo

OK ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Typo in performer-init.ly

In ../ly/performer-init.ly (file version 2.17.14, distributed with LilyPond version 2.18.0), at line 186 (in the NullVoice block), there is a typo. The file reads: \type Performer_Group But this should be: \type Performer_group The erroneous capital G leads to a fatal error in .ly

small typo

in context: http://lilypond.1069038.n5.nabble.com/small-typo-tp148744.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: small typo

Eluze elu...@gmail.com writes: in NR 2.17.23, Multiple notes to one syllable http://lilypond.org/doc/v2.17/Documentation/notation-big-page#multiple-notes-to-one-syllable 2nd paragraph: When a melisma occurs on a syllable other that the last one in a word… that should be replaced by than

Re: legder docs typo

Paul On 19 January 2013 02:33, Paul Morris p...@paulwmorris.com wrote: Caught a couple of typos here: http://www.lilypond.org/doc/v2.16/Documentation/notation/modifying-single-staves Two corrections shown between ... Legder Ledger lines can also be made to appear

Re: legder docs typo

On Jan 19, 2013, at 4:31 AM, James pkx1...@gmail.com wrote: This has been fixed and checked in. It'll appear when the next version of Lilypond is built (2.17.11) the website gets built at the same time. James, Thanks for fixing this. Regards and HTH, -Paul

legder docs typo

Caught a couple of typos here: http://www.lilypond.org/doc/v2.16/Documentation/notation/modifying-single-staves Two corrections shown between ... Legder Ledger lines can also be made to appear inside the staff where custom staff lines are required. The example shows the

Re: Typo in documentation (3.5 MIDI Output)

On Mon, Jul 09, 2012 at 01:15:27AM +0200, David Kastrup wrote: Colin Hall colingh...@gmail.com writes: On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote: In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo. In the sentence Standard MIDI oputput is somewhat crude

Typo in documentation (3.5 MIDI Output)

In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo. In the sentence Standard MIDI oputput is somewhat crude it should say output. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug

Re: Typo in documentation (3.5 MIDI Output)

Colin Hall colingh...@gmail.com writes: On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote: In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo. In the sentence Standard MIDI oputput is somewhat crude it should say output. Thanks for reporting that problem, Micha

Re: Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

Comment #3 on issue 2410 by pkx1...@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 Just an update as I am not sure when the translations were put in for which language as of 2.13.34's doc Fr

Re: Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

Comment #4 on issue 2410 by paconet@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 Ja = Corrected in lilypond/translation hopefully to be merged today

Re: Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

Comment #2 on issue 2410 by paconet@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 Fixed in Japanese. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

New issue 2410 by address@hidden: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 http://lilypond.org/doc/v2.14/Documentation/notation/modifying-context-plug_002dins First Paragraph. 'Key_signature_engraver' does

Re: Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

Comment #1 on issue 2410 by paconet@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 Fixed in French (by Jean-Charles) and in Spanish. ___ bug-lilypond

Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs

Status: Accepted Owner: Labels: Type-Documentation New issue 2410 by pkx1...@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 http://lilypond.org/doc/v2.14/Documentation/notation/modifying-context

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Status: Verified Comment #4 on issue 2274 by gra...@percival-music.ca: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_28 Comment #3 on issue 2274 by d...@gnu.org: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 Pushed as 8770c579a7808f995af125482ad450709855a2fd to staging

Issue 2274 in lilypond: Patch: Typo fixes

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2274 by plros...@gmail.com: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 Typo fixes Fix unneeded quot;llquot; in quot;canceledquot;, quot;cancelingquot; and quot;labeledquot;. Replace quot

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Labels: Patch-review Comment #1 on issue 2274 by lilypond...@gmail.com: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Labels: -Patch-review Patch-push Comment #2 on issue 2274 by gra...@percival-music.ca: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 (No comment was entered for this change.) ___ bug-lilypond mailing list

Typo in Documentation

Typo in Documentation http://lilypond.org/doc/v2.14/Documentation/learning/engravers-explained Staff_symbol_engraver *Ersetllt* die (standardmäßig) fünf Notenlinien des Systems. MfG hgz ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Typo in Documentation (2)

Typo in Documentation (2) http://lilypond.org/doc/v2.14/Documentation/learning/modifying-context-properties in Kontexteigenschaften mit \with setzen [...] die für die gesamte Partitur erhalten *bleichen* soll. MfG hgz ___ bug-lilypond mailing list

Re: Typo in Documentation

hgz hgzo...@yahoo.com wrote in message news:loom.20111218t153505-...@post.gmane.org... Typo in Documentation http://lilypond.org/doc/v2.14/Documentation/learning/engravers-explained Staff_symbol_engraver *Ersetllt* die (standardmäßig) fünf Notenlinien des Systems. MfG hgz Thanks. Added

Re: Typo in Documentation (2)

hgz hgzo...@yahoo.com wrote in message news:loom.20111218t155621-...@post.gmane.org... Typo in Documentation (2) http://lilypond.org/doc/v2.14/Documentation/learning/modifying-context-properties in Kontexteigenschaften mit \with setzen [...] die für die gesamte Partitur erhalten *bleichen

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #4 on issue 2106 by colingh...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 How should the bug squad verify this? Perhaps by touching a file to verify that some part of the translated doc

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Updates: Status: Fixed Labels: -Patch-review fixed_2_15_22 Comment #5 on issue 2106 by gra...@percival-music.ca: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 We don't expect the bug squad to compile

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #7 on issue 2106 by julien.r...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 I expect to have more enhancement patches to offer as I work through the build of translated manuals. Should I open

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #9 on issue 2106 by julien.r...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 Sounds good, thanks. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #8 on issue 2106 by gra...@percival-music.ca: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 Don't post them here, because this issue is closed. You can upload a whole branch for review; that would be my

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #3 on issue 2106 by colinpkc...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 As this was pushed with 9ac7a5aaff66f2bd19184c9a23bccd195323e193, it should be marked fixed and the relarewd

Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2106 by julien.r...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 Build fixes for translated manuals: dependencies and a typo Adding

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #1 on issue 2106 by julien.r...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 The idea is that translated manuals should also benefit from the work done towards Issue 1852

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Updates: Labels: Patch-review Comment #2 on issue 2106 by lilypond...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106#c2 Patchy the autobot says: LGTM

Re: Minor website typo

Alexander Kobel n...@a-kobel.de wrote in message news:4ed0cf6b.7050...@a-kobel.de... On 2011-11-26 12:27, Colin Hall wrote: On Sat, Nov 26, 2011 at 12:11:22PM +0100, Helge Kruse wrote: There is a little typo on http://www.lilypond.org/text-input.de.html. You read FagottNoteb where it should

Re: Minor website typo

On Sat, Nov 26, 2011 at 12:11:22PM +0100, Helge Kruse wrote: There is a little typo on http://www.lilypond.org/text-input.de.html. You read FagottNoteb where it should be FagottNoten. Regards, Helge Thanks, Helge. I'm forwarding this to bug-lilypond. Cheers, Colin. -- Colin Hall

Re: Minor website typo

On 2011-11-26 12:27, Colin Hall wrote: On Sat, Nov 26, 2011 at 12:11:22PM +0100, Helge Kruse wrote: There is a little typo on http://www.lilypond.org/text-input.de.html. You read FagottNoteb where it should be FagottNoten. The figure just below should also read Transposition für F

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Labels: fixed_2_14_2 Comment #9 on issue 1665 by carl.d.s...@gmail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 backported ___ bug-lilypond mailing list bug

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Labels: -backport Comment #10 on issue 1665 by carl.d.s...@gmail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 (No comment was entered for this change.) ___ bug

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Status: Verified Comment #8 on issue 1665 by brownian.box: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Comment #6 on issue 1665 by philehol...@googlemail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Or new tags. Or change the default sort order. Or a few other things like that concerning the way the project itself

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Comment #7 on issue 1665 by percival.music.ca: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Anybody can add a new tag; only admins can make a registered tag. The difference is whether it's displayed with green text or brown

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Status: Started Owner: pkx1...@gmail.com Labels: Patch-review Comment #1 on issue 1665 by pkx1...@gmail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Cannot see anything wrong with {dis:aug

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Comment #2 on issue 1665 by percival.music.ca: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 ... wow, I have no recollection of this whatsoever. Presumably I added it because somebody asked for it on the bug- or user-list

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Cc: carl.d.s...@gmail.com Comment #3 on issue 1665 by pkx1...@gmail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Pushed as f30a5ddbf8ca50d14b9b73fcaad5161476a47735 This can also be backported

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Status: Fixed Labels: fixed_2_15_2backport Comment #4 on issue 1665 by pkx1...@gmail.com: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Hope this is correct labelling :) I didn't think I could change

Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Updates: Labels: -Patch-review -fixed_2_15_2backport fixed_2_15_2 backport Comment #5 on issue 1665 by percival.music.ca: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 any project member can change the status or add tags

Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly

Status: Accepted Owner: Labels: Type-Documentation Priority-Medium Frog New issue 1665 by percival.music.ca: one-character typo in predefined-guitar-fretboards.ly http://code.google.com/p/lilypond/issues/detail?id=1665 Predefined-guitar-fretboards.ly (v2.12.0): Missing semi-colon at end

Re: Typo in time-signature-settings.scm?

On 4/5/11 1:17 AM, Valentin Villenave valen...@villenave.net wrote: On Sun, Apr 3, 2011 at 1:07 AM, Carl Sorensen c_soren...@byu.edu wrote: On 4/2/11 3:51 PM, Valentin Villenave valen...@villenave.net wrote: Shouldn't it read 3/8, 6/8, and 8/8? Yes, absolutely. Thanks for the catch.

Re: Typo in time-signature-settings.scm?

On Wed, Apr 6, 2011 at 7:07 PM, Carl Sorensen c_soren...@byu.edu wrote: (1.12) = (2 . 3) * (1 . 8) = (2 . 24) which is the duration of an 8th note triplet. OK, that's what I wanted to know. And yes, according to the rules in the references, triplets should be beamed 3 by 3 (or every 1/4

Re: Typo in time-signature-settings.scm?

On Sun, Apr 3, 2011 at 1:07 AM, Carl Sorensen c_soren...@byu.edu wrote: On 4/2/11 3:51 PM, Valentin Villenave valen...@villenave.net wrote: Shouldn't it read 3/8, 6/8, and 8/8? Yes, absolutely. Thanks for the catch. Hi Carl, thanks! While we're talking beaming rules, I just wanted to ask

Typo in time-signature-settings.scm?

Hi Carl, hi everybody, time-signature-settings.scm, line 46 et seq.: ;;; If an exception is specified for a given beam-type, it will apply to all ;;; beams of shorter durations that don't have an individual exception, so ;;; ((1 . 8) . (3 3 2)) ;;; will cause all primary beams to

  1   2   >