Re: rextend macro sometimes repeats a word

On Sat, Oct 30, 2010 at 01:51:14AM +0200, Francisco Vila wrote: > 2010/10/30 Francisco Vila : > > this is to ask if anyone, besides me, has noticed that rextend macro > > sometimes prints a repeated word before the link, and the word is the > > last of the phrase argument. Yes, back in 2008. > Wa

Re: SVG Point Click

On Fri, Oct 29, 2010 at 5:32 AM, Christoph wrote: > > Is there a way to have point-click-behavoir or any semantic > meta-information about the  correspondending postion in > the .ly-file in SVGs that a generated with the SVG-Backend (like in PDFs?). Not currently, but it should be possible to add

Re: non-technical help for spacing issues

On Thu, 28 Oct 2010 05:13:03 -0700, wrote: There is now a small set of over-rides is posted on -user, vertical spacing only so far, hopefully to be tried out by others over the weekend : On one thing might surprise -dev

Re: non-technical help for spacing issues

On Thu, 28 Oct 2010 05:13:03 -0700, wrote: There is now a small set of over-rides is posted on -user, vertical spacing only so far, hopefully to be tried out by others over the weekend : On one thing might surprise -dev

Re: rextend macro sometimes repeats a word

2010/10/30 Francisco Vila : > Hello all, > > this is to ask if anyone, besides me, has noticed that rextend macro > sometimes prints a repeated word before the link, and the word is the > last of the phrase argument.  It's so strange! > > e.g. @rextend{Tutorial de Scheme} produces 'Scheme Tutorial

rextend macro sometimes repeats a word

Hello all, this is to ask if anyone, besides me, has noticed that rextend macro sometimes prints a repeated word before the link, and the word is the last of the phrase argument. It's so strange! e.g. @rextend{Tutorial de Scheme} produces 'Scheme Tutorial de Scheme' in HTML. My rextend macro mi

Re: renaming "vertical spacing inside systems" props

On 10/29/10 4:27 PM, "Mark Polesky" wrote: > Guys, > > Here are my proposals for renaming the properties related to > "Vertical spacing inside systems". > > * * * * * * * * * * * * * * * > > I've thought about it, and I think I slightly favor the term > "loose line" over "non-staff line"; t

Re: renaming "vertical spacing inside systems" props

Mark Polesky wrote Friday, October 29, 2010 11:27 PM Here are my proposals for renaming the properties related to "Vertical spacing inside systems". * * * * * * * * * * * * * * * I've thought about it, and I think I slightly favor the term "loose line" over "non-staff line"; the word "loose"

\layout vs. \paper

Is it true that some \paper variables can be set in a \layout block without a problem, and vice versa? Are there any variables that will only work in a \paper block? Are there any that only work in a \layout block? If so, what are they? Is there a system to this? Thanks. - Mark _

renaming "vertical spacing inside systems" props

Guys, Here are my proposals for renaming the properties related to "Vertical spacing inside systems". * * * * * * * * * * * * * * * I've thought about it, and I think I slightly favor the term "loose line" over "non-staff line"; the word "loose" is distinctive and much less likely to get tangled

Re: Doc: NR 4.4.1: Rewrite. (issue2642043)

On Fri, 29 Oct 2010 01:17:00 -0700, Ian Hulin wrote: On 29/10/10 05:12, Keith wrote: Documentation/notation/spacing.itely:1513: * Inter-system spacing properties:: Within-system You said: inter = between, intra = within [...] or do you mean the original "Inter-system spacing" should have re

[PATCH] Allow music identifiers in \addlyrics (no need for braces any more)

Allow music identifiers in \addlyrics (no need for braces any more) In particular, so far the following did not work: \new Staff { \m \addlyrics \l } Instead, one had to use braces around \m and \l: \new Staff { {\m} \addlyrics {\l} } This patch extends the parser to allow music identifie

Re: Music function extension...

Valentin Villenave writes: > On Fri, Oct 29, 2010 at 12:46 PM, David Kastrup wrote: >> >> Are there good reasons left for not allowing music functions to take >> pitches as arguments?  That would allow implementing something like >> \transpose as a music function.  The alternative, letting it ta

Re: Doc: move non-Western languages to world.itely (issue2735044)

On Fri, Oct 29, 2010 at 01:12:13PM +, tdanielsmu...@googlemail.com wrote: > OK, it's an improvement so go ahead and push, but "musics" grates so > much I'd definitely have removed it as part of this patch. :) Ok, we're agreed. We *all* hate the material which is moving into world.itely, but

Re: Doc: move non-Western languages to world.itely (issue2735044)

On Fri, Oct 29, 2010 at 3:12 PM, wrote: > OK, it's an improvement so go ahead and push, Thanks. Will do. > but "musics" grates so > much I'd definitely have removed it as part of this patch. I hear you. This will be part of my next patch, which I'm preparing right now. Cheers! Valentin.

Re: Doc: move non-Western languages to world.itely (issue2735044)

On 2010/10/29 13:12:13, Trevor Daniels wrote: OK, it's an improvement so go ahead and push, but "musics" grates so much I'd definitely have removed it as part of this patch. Musics grates on me, too, but I have found it as an accepted use, e.g.

SVG Point Click

dear lilypond-developers, Is there a way to have point-click-behavoir or any semantic meta-information about the correspondending postion in the .ly-file in SVGs that a generated with the SVG-Backend (like in PDFs?). thank you and regards Christoph ___

Re: Doc: move non-Western languages to world.itely (issue2735044)

http://codereview.appspot.com/2735044/diff/8001/Documentation/music-glossary.tely File Documentation/music-glossary.tely (right): http://codereview.appspot.com/2735044/diff/8001/Documentation/music-glossary.tely#newcode2008 Documentation/music-glossary.tely:2008: @uref{http://en.wikipedia.org/wi

Re: Doc: move non-Western languages to world.itely (issue2735044)

LGTM, but I have an organization question. Carl http://codereview.appspot.com/2735044/diff/8001/Documentation/notation/world.itely File Documentation/notation/world.itely (right): http://codereview.appspot.com/2735044/diff/8001/Documentation/notation/world.itely#newcode42 Documentation/notati

Re: Doc: move non-Western languages to world.itely (issue2735044)

OK, it's an improvement so go ahead and push, but "musics" grates so much I'd definitely have removed it as part of this patch. http://codereview.appspot.com/2735044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/l

Re: Music function extension...

On Fri, Oct 29, 2010 at 12:46 PM, David Kastrup wrote: > > Are there good reasons left for not allowing music functions to take > pitches as arguments?  That would allow implementing something like > \transpose as a music function.  The alternative, letting it take a > music event and not checking

Re: Doc: move non-Western languages to world.itely (issue2735044)

LGTM. My nitpick doesn't require a new draft version; if there are no other complaints, go ahead and push in 23 hours. I still don't like seeing TODOs, and in a few months we'll be going through and removing all TODOs from the code... but since these TODOs weren't yours, I can't blame you for ke

Re: Doc: move non-Western languages to world.itely (issue2735044)

Hi guys, here's a new patch set. In case that wasn't clear, this commit is mainly intended as a structural change (hence the de/es/fr docs update): as suggested by Graham, the new subsection in world.itely was blindly copied from pitches.itely and hasn't been adapted *at all* yet. http://coder

Re: convert-ly on lilypondTool under GNU/Linux

2010/10/29 Bertalan Fodor (LilyPondTool) : > Yeah, it uses python only if convert-ly command (in Plugins>Plugin > properties) is set to convert-ly.py (It looks for the py extension) > If you change that to just convert-ly that should work (at least that's the > intention, though I don't have linux

Music function extension...

Are there good reasons left for not allowing music functions to take pitches as arguments? That would allow implementing something like \transpose as a music function. The alternative, letting it take a music event and not checking its duration and hoping that it is a single note, seems quite le

Re: convert-ly on lilypondTool under GNU/Linux

Yeah, it uses python only if convert-ly command (in Plugins>Plugin properties) is set to convert-ly.py (It looks for the py extension) If you change that to just convert-ly that should work (at least that's the intention, though I don't have linux so I can't test that.) On Tue, Oct 26, 2010 at 1:1

Re: Doc: move non-Western languages to world.itely (issue2735044)

Generally ok, but I don't know why you're changing the translations before the English docs are done. http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely File Documentation/notation/pitches.itely (right): http://codereview.appspot.com/2735044/diff/1/Documentation/n

Re: Doc: move non-Western languages to world.itely (issue2735044)

Looks fine generally, but some editorial changes are needed. Trevor http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely File Documentation/notation/pitches.itely (right): http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely#newcode459

Doc: move non-Western languages to world.itely (issue2735044)

Reviewers: , Message: Greetings, new patch. Description: Doc: move non-Western languages to world.itely Please review this at http://codereview.appspot.com/2735044/ Affected files: M Documentation/de/notation/pitches.itely M Documentation/de/notation/world.itely M Documentation/es/notat

Re: Allow predefined diagrams regardless of note names language. (issue2791041)

http://codereview.appspot.com/2791041/diff/1/ly/predefined-guitar-fretboards.ly File ly/predefined-guitar-fretboards.ly (right): http://codereview.appspot.com/2791041/diff/1/ly/predefined-guitar-fretboards.ly#newcode20 ly/predefined-guitar-fretboards.ly:20: #(set! pitchnames default-language) On

Re: Tablature: proper support for tie/slur- and tie/glissando-constellations (issue2191042)

Am 28.10.2010 14:53, schrieb carl.d.soren...@gmail.com: LGTM. However, I'm a bit nervous about putting bends as well into the Tab_tie_follow_engraver. Not that the engraver won't work, but that the Tab_tie_follow_engraver won't be part of the documentation. Currently, I view Scheme engravers a

Re: Tablature: proper support for tie/slur- and tie/glissando-constellations (issue2191042)

On 28 October 2010 23:55, Carl Sorensen wrote: > Well, as far as I can see, Scheme engravers are really engravers, so they > ought to be documented in the IR along with the C++ engravers, not in an > appendix of the NR along with Scheme functions. > > Although the approach you suggest is better th

Re: (tuplet . around) causes regtests to fail to compile

On 29 October 2010 09:18, Werner LEMBERG wrote: > in file lily-guile.cc; for the above lilypond call it gets passed a > value of 0x204 for `val'.[1] This is obviously a special constant, > however, I haven't found out what guile symbol this corresponds to due > to the extremely cryptic definition

Re: (tuplet . around) causes regtests to fail to compile

> lilypond -dcheck-internal-types input/regression/slur-tuplet.ly > > It appears that there is some internal error in LilyPond that is > causing -dcheck-internal-types not to work properly. Yep. > I'm afraid this is over my head, although I'll look around a bit > more at it. I did a bit of deb

Re: Doc: NR 4.4.1: Rewrite. (issue2642043)

On 29/10/10 05:12, k-ohara5...@oco.net wrote: > > http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely > > File Documentation/notation/spacing.itely (right): > > http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely#newcode1509 > > Docume

Re: Allow predefined diagrams regardless of note names language. (issue2791041)

OK, will push. http://codereview.appspot.com/2791041/diff/1/ly/predefined-guitar-fretboards.ly File ly/predefined-guitar-fretboards.ly (right): http://codereview.appspot.com/2791041/diff/1/ly/predefined-guitar-fretboards.ly#newcode20 ly/predefined-guitar-fretboards.ly:20: #(set! pitchnames defa