relative coordinates of different note heads

Re: start [was: Re: Take 1] Datum: Wed, 1 Jul 2009 07:57:28 -0600 Von:Carl D. Sorensen An: Marc Hohl Marc, This question should be asked on the -devel list; somebody there will be able to help you. Carl On 7/1/09 1:47 AM, "Marc Hohl" wrote: [...] I agree that the

Re: First release of ly/tablature.ly

Joe Neeman schrieb: On Tue, 2009-06-23 at 12:53 -0600, Carl D. Sorensen wrote: http://codereview.appspot.com/67174/diff/1/2#newcode237 Line 237: \layout { It seems to me that we have 3 versions of tablature now: the "default" version in engraver-init.ly, the version that appears if the user i

Re: First release of ly/tablature.ly

[...] I don't particularly mind breaking existing scores (as long as there is a convert-ly rule to at least warn about the problem), but I don't think the situation in the patch is particularly friendly. We've a long tradition of choosing sensible behaviour over backwards compatibility and I see

Re: First release of ly/tablature.ly

Carl D. Sorensen schrieb: [...] 3) move the existing predefined tunings from scm/output-lib.scm into tablature.scm, where I can add my new tunings as well; Yes, I agree with this. Should the definitions for fret-number-tablature-format and fret-number-tablature-format-banjobe move

Re: First release of ly/tablature.ly

Carl D. Sorensen schrieb: On 7/7/09 12:20 PM, "Marc Hohl" wrote: [...] I don't particularly mind breaking existing scores (as long as there is a convert-ly rule to at least warn about the problem), but I don't think the situation in the patch is particularly fr

Re: First release of ly/tablature.ly

Marc Hohl schrieb: Carl D. Sorensen schrieb: On 7/7/09 12:20 PM, "Marc Hohl" wrote: [...] I don't particularly mind breaking existing scores (as long as there is a convert-ly rule to at least warn about the problem), but I don't think the situation in the p

Re: percussion and midi

Hello Alan, Alan Szlosek schrieb: Greetings, current Lilypond developers. I'm new here and would like some guidance. I'm interested in using Lilypond to compose music for high school drumlines. Hopefully my contributions will be useful to others. I'm not new to programming (Computer Science

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: On 7/16/09 5:54 PM, "Jonathan Kulp" wrote: Carl Sorensen wrote: So, while I asked Marc to provide documentation, I didn't require it. I did, however, require regtests. As soon as we get the patch applied, we can ask one of the people who is clamoring for impr

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: On 7/16/09 9:56 AM, "Carl Sorensen" wrote: Marc Hohl has completed a patch for improved tablature support. It is available for review at: http://codereview.appspot.com/95059 Please review and comment. Thanks, Marc, Here are some comment

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: 2) Your regression test for the modernTab clef: Doc header should say "four- to seven- stringed instruments", which means instruments having four to seven strings. "four to seven stringed instruments" means four to seven instruments having strings. Isn't english fun?

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: Right, so we *must* have the function mode. Do we need the setting mode as well? I don't feel strongly about eliminating it, but I don't feel strongly about keeping it either. I trust your judgment. I prefer to offer both variants. However, now that I think about i

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: On 7/17/09 10:16 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: Right, so we *must* have the function mode. Do we need the setting mode as well? I don't feel strongly about eliminating it, but I don't feel strongly about keeping it e

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: Wikipedia (in a poorly-cited article) uses the term "ghost note" for all instruments (including the string-muted and palm-muted notes). This entry seems to indicate that "ghost note" is a term widely used with drums. Following up on links to "ghost note" in the guitar wor

Re: PATCH: Improved tablature support

Trevor Daniels schrieb: Carl, Marc After the long discussion about naming the new cross-head function and associated predefs I see you have retained deadNote as the base name. I thought the outcome of the discussion was to use xHead or crossHead for the base name with deadNote being defined to

Re: PATCH: Improved tablature support

dem...@suffolk.lib.ny.us schrieb: Please dont rename the cross head, it has a name, predating any usage stemming from rock musicians jargon. That name is further 'blessed' by the unicode standard, "Musical Symbol X Notehead", 1D143. I think Lilypond should propose both, the "official", s

Re: PATCH: Improved tablature support

Carl Sorensen schrieb: [...] The generic approach has now been pushed to git 247f0b6d46fd8f3253a99f95a70ce14345daa5f9 There's a generic styledNoteHeads music function that applies a note style to music whether or not it's in a chord construct. deadNotes and palmMute have been redefined to use

slur information available within callback?

Is there any possibility to retrieve informations about slurs being adjacent from a callback? For example \displayMusic { c4 ( c ) ( c ) c } shows [...] (make-music 'EventChord 'elements (list (make-music 'NoteEvent 'duration

Re: PATCH: Improved tablature support

Graham Percival schrieb: On Wed, Aug 12, 2009 at 08:51:42PM +0100, Trevor Daniels wrote: Carl Sorensen wrote Wednesday, August 12, 2009 7:32 PM And if we're ever going to move it to a postfix operator (which is one of the goals of the GLISS project), now is the time, before we get a

Re: PATCH: Improved tablature support

Graham Percival schrieb: On Thu, Aug 13, 2009 at 09:28:02AM +0200, Marc Hohl wrote: Graham Percival schrieb: Yes, this is planned. It's been on my list of discussions to introduce when the website/build stuff is finished, for about two months now. Sorry to interrupt

Re: PATCH: Improved tablature support

Mark Polesky schrieb: * there are single and double angle-brackets here. Recently I've noticed some e-mail clients and/or mailing list archives do weird things with them (like removing them). Just in case you think I accidentally left something out! Yes, the closing angled bracket is n

explanation of Slur #'details?

Hello, is there a description of Slur #'details? I googled for some of the parameters and did a git grep, but I didn't find anything which would explain the meaning of these parameters: ((region-size . 4) (head-encompass-penalty . 1000.0) (stem-encompass-penalty . 30.0) (closeness-factor . 10

Re: explanation of Slur #'details?

Patrick McCarty schrieb: On 2009-08-20, Marc Hohl wrote: Hello, is there a description of Slur #'details? I googled for some of the parameters and did a git grep, but I didn't find anything which would explain the meaning of these parameters: ((region-size . 4) (head-encompa

Re: [PATCH] Implement new handling for margin settings

Michael Käppler schrieb: More in a few hours. I won't be able to check my mail during the next week so don't expect me to reply until then. Anyway, I want to ask you some things before I leave. 1. Can someone run the regression test suite for me? I ask because I've never done this and my c

[PATCH] Enhancement: automatic polyphony in different \...Staff contexts

[moved from -user] According to Neil's proposals and Carl's annotations, I created a patch to enhance the automatic polyphony: << ... \\ .. >> constructs can now be used within \DrumStaff, \TabStaff and \Staff constructs, without to explicitly inserting placeholders. I send it as a gzipped file

Re: [PATCH] Enhancement: automatic polyphony in different \...Staff contexts

Carl Sorensen schrieb: On 8/22/09 3:47 AM, "Marc Hohl" wrote: [moved from -user] According to Neil's proposals and Carl's annotations, I created a patch to enhance the automatic polyphony: << ... \\ .. >> constructs can now be used within \DrumStaff,

Re: \context for named Staff

Jay Anderson schrieb: [...] So what do you think? Should the "SmallStaff" just be left as a snippet? If it is a snippet ideally I'd want to do something like: \include "small_staff.lyi" \score { \new SmallStaff {...} } How would one make small_staff.lyi so this worked? This way it would be

Re: \context for named Staff

Trevor Daniels schrieb: Marc Hohl wrote Saturday, August 22, 2009 7:30 PM Jay Anderson schrieb: [...] So what do you think? Should the "SmallStaff" just be left as a snippet? If it is a snippet ideally I'd want to do something like: \include "small_staff.lyi" \

Re: [PATCH] Enhancement: automatic polyphony in different \...Staff contexts

Carl Sorensen schrieb: On 8/22/09 12:11 PM, "Marc Hohl" wrote: Carl Sorensen schrieb: On 8/22/09 3:47 AM, "Marc Hohl" wrote: [moved from -user] According to Neil's proposals and Carl's annotations, I created a patch to e

Errors in Documentation/snippets

Hello, glad to see that 2.13.4 is out! However, by clicking through the docs, I found some errors on http://lilypond.org/doc/v2.13/Documentation/snippets/Fretted-strings#Fretted-strings 1) Guitar slides: Here the ledger lines are still visible. Moreover, guitar notation is generally notated

Re: Errors in Documentation/snippets

Graham Percival schrieb: On Thu, Sep 24, 2009 at 04:05:22PM +0200, Marc Hohl wrote: 1) Guitar slides: Here the ledger lines are still visible. Moreover, guitar notation is generally notated with \clef "treble_8". I'll let a guitar person handle this. Ok.

Re: Errors in Documentation/snippets

Neil Puttock schrieb: 2009/9/25 Marc Hohl : The problem I see is the fact that \clef "moderntab" is available in 2.13.4, whereas LSR is based on 2.12, as far as I know. So "moderntab" should go into the docs for 2.13, not into LSR (yet). Until the tablature docu

different sizes for instrument names (Staff vs. PianoStaff)

Hello, while working with lilypond I discovered that changes of the font size are treated differently between Staff and PianoStaff. Consider the following snippet: \version "2.13.4" stuff = \relative c { c4 d e f g a b c } \score { << \new Staff = "Staff" \with { \override StaffSymbol #

Re: different sizes for instrument names (Staff vs. PianoStaff)

= #(magnification->font-size 2/3) ... } I found yet another solution via \markup: \new PianoStaff \with { instrumentName = \markup { \font-size #(magnification->font-size 2/3) ... } } Thanks, Marc /Mats Marc Hohl wrote: Hello, while working with lilypond I discovered tha

Re: build failure

Carl Sorensen schrieb: On 10/10/09 5:59 AM, "Graham Percival" wrote: Please don't do this. Starting from doc-clean, clean, distclean, and ./autogen, I get: I'm sorry. I pushed a patch without testing it, because Marc has been a reliable contributor. Oops - sorry for the proble

patch: tablature and MultiMeasureRestNumber

Hello, after messing up lilypond with my latest patch, I now follow the recommendations and send patches to -devel. Here is a small one which removes the spurious MultiMeasureRestNumber in standard tablature (gzipped for proper line endings). Greetings Marc 0001-tablature-fix-problems-with-M

Re: patch: tablature and MultiMeasureRestNumber

TabVoice or TabStaff level? Marc Trevor - Original Message - From: "Marc Hohl" To: "Lily-Devel List" Sent: Thursday, October 15, 2009 7:14 AM Subject: patch: tablature and MultiMeasureRestNumber Hello, after messing up lilypond with my latest patch, I now follow

Re: patch: tablature and MultiMeasureRestNumber

Trevor Daniels schrieb: Marc Hohl wrote Thursday, October 15, 2009 9:36 AM Trevor Daniels schrieb: Marc Should not the \revert be limited to TabVoice to avoid reverting the property in other contexts? The same could be said for some of the other \reverts too. Yes, of course. Attached is

engraver how-to?

Hello, I am still working on bends for guitar notation. For the moment, I redefined the slur stencil to get the desired results, but this has some severe drawbacks, so this is only a crude workaround for testing the postscript routines. A cleaner solution will need a new engraver for this pur

Re: engraver how-to?

Patrick McCarty schrieb: On Sat, Oct 17, 2009 at 1:34 PM, Neil Puttock wrote: The Slur_engraver looks quite complicated, but it's a walk in the park compared with the code which does all the slur scoring/formatting. :) Yeah, I've noticed that. :-) BTW, Marc, I haven't forgotten abou

Re: [PATCH] Twoside mode

Michael Käppler schrieb: Hi all, please review this patch: http://codereview.appspot.com/144049 I cannot judge the code, but it is great to have this functionality in future versions! Thanks a lot for your efforts! Marc It's aim is to provide the possibility for setting different margins o

Patch: remove Ottava_spanner_engraver from \TabStaff

Hi all, Raphaël Doursenaud has pointed me to an error in tablature: showing the ottava spanner in tablature doesn't make any sense, so I removed it. Is this patch ready to be applied? Marc 0002-tablature-enhancement-remove-Ottava_spanner_engrave.patch.gz Description: GNU Zip compressed dat

Re: Patch: remove Ottava_spanner_engraver from \TabStaff

Marc Hohl schrieb: Hi all, Raphaël Doursenaud has pointed me to an error in tablature: showing the ottava spanner in tablature doesn't make any sense, so I removed it. Is this patch ready to be applied? I reworked my patch slightly; now the new behavior (and the improved multi measure

Re: Patch: remove Ottava_spanner_engraver from \TabStaff

Neil Puttock schrieb: 2009/11/6 Marc Hohl : Ready to be applied? LGTM. I don't think these comments are necesary though: + %% No key in tablature! There was already a "no accidentals" comment in it, so for the sake of consistency, I added the others. I added

Re: Patch: remove Ottava_spanner_engraver from \TabStaff

Neil Puttock schrieb: 2009/11/9 Marc Hohl : I added another version of my patch without these comments; I tried to fill the [DOCME] in the description tag with something more useful. Cheers, it's applied. Thank you! Marc Regards,

Re: Issue #768 - chord repetition shortcut: patch for review

David Kastrup schrieb: Nicolas Sceaux writes: Hi, Here is patch implementing the chord repetition shortcut that has been discussed a few times, for review: This is great! I've chosed arbitrary defaults, which may be changed: - the shortcut i

Re: Issue #768 - chord repetition shortcut: patch for review

David Kastrup schrieb: [...] But *4 is _logical_. You can guess what it does without looking it up in the manual. No. Since it looks like a multiplication, it treats the number, not the notes (at least for me). So < c e g>4*4 could be interpreted as < c e g >16, which is not what we want. I

[Patch] Fwd: [frogs] Changing subproperties with grob-set-property

Hello, there is a patch attached for providing ly:grob-set-nested-property! This has been discussed in the frogs mailing list. Marc Enhancement-Providing-ly-grob-set-nested-property.patch.gz Description: GNU Zip compressed data ___ lilypond-devel ma

Frog's Lament

Hello all, I followed the (partly very emotional) discussions about (un)documentated code with great interest, and aside from the fact that I neither have the technical arguments nor the knowledge, I mostly agree with David Kastrup. As a frog, I feel supported very well from Carl et al., but

Re: [frogs] Frog's Lament

Sorry, some Germanism found its way into the mail, sed "s/documentated/documented/g" ;-) Marc Marc Hohl schrieb: Hello all, I followed the (partly very emotional) discussions about (un)documentated code with great interest, and aside from the fact that I neither have the

Re: [frogs] Frog's Lament

Carl Sorensen schrieb: On 11/26/09 2:56 AM, "Marc Hohl" wrote: [...] Two things come to mind here: 1) When any of us asks a question on the list and gets an answer, we ought to add it to the CG. We can either do it by writing a patch, or by writing some text that will

Re: [frogs] Frog's Lament

Trevor Daniels schrieb: Carl Sorensen wrote Thursday, November 26, 2009 4:31 PM [...] While I was learning how to use the Internals Reference manual I wrote chapter 4 of the Learning Manual to make it easier for others to follow. It also benefitted me: having to write down what I was learning

Re: [frogs] Frog's Lament

Han-Wen Nienhuys schrieb: [...] There is not a goal per se to move stuff from C++ to Scheme, but rather to expose relevant (C++) interfaces to Scheme so people can write the extensions in Scheme if they want. Come to think of it, it's actually a neat project to write a Scheme interface to engra

Re: [frogs] Frog's Lament

Graham Percival schrieb: On Thu, Nov 26, 2009 at 10:56:05AM +0100, Marc Hohl wrote: Well documented code is crucial in such a project for other developers to jump on the train, so learning by RTF code isn't fun (as mentioned elsewhere) - for me, it's annoying, it's frustratin

Re: Lettered tablature patch

Trevor Daniels schrieb: I posted my first patch to Rietveld last night, but nothing seems to have been cc'd to the list. Not sure what I did wrong. It's at http://codereview.appspot.com/164063. Here's what it does. This is the first patch of a series aiming eventually to enable Baroque lut

Re: [Issue #3947] fixing \huge et al.

Hi Kieren, Am 25.06.2017 um 17:11 schrieb Kieren MacMillan: Hi, Another ten days has passed… I guess I don't understand how the Lilypond development process works. I keep hearing we need people to jump in and learn how to develop/improve Lilypond. I took the initiative, found an issue I tho

Re: Should we have a from-barline property in analogy to to-barline ?

Am 24.07.2017 um 13:58 schrieb David Kastrup: Seems like an obvious addition. Would make stuff (like slurs, hairpins and so on) starting at the bar move backwards to the bar line. Probably also useful for non-spanners like a \fermata ? +1 ___

Re: [frogs] Patch for Issue #830

Carl Sorensen schrieb: On 12/19/09 1:07 PM, "Marc Hohl" wrote: Hi all, I have renamed the feta-*.mf files accordingly (see issue #830). I did make clean make all and didn't get any errors. Ok to apply? I will check this later today. I think I'd like to r

Re: [frogs] Patch for Issue #830

Neil Puttock schrieb: 2009/12/20 Carl Sorensen : I think I'd like to recommend that in the future, instead of emailing patches (with the associated problems with line endings), we just have Frogs post them on Rietveld. I'd also recommend at least checking a snippet runs properly (if n

Re: [frogs] Patch for Issue #830

Mark Polesky schrieb: Marc Hohl wrote: I have renamed the feta-*.mf files accordingly (see issue #830). I did make clean make all and didn't get any errors. Ok to apply? I don't see any problems looking at the patch, but that doesn't mean there aren't any. I

Re: [frogs] Patch for Issue #830

git when it makes the patch than anything else. regards James ------ From: Marc Hohl Sent: Sun 20/12/2009 20:53 To: Mark Polesky Cc: Neil Puttock; Carl Sorensen; Lily-Devel List; fr...@lilynet.net

Re: Alternative music font

Carl Sorensen schrieb: Jan Nieuwenhuizen xs4all.nl> writes: Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon Tatham: It's interesting that you should mention that: that actually reminds me of one of my specific issues with Feta, namely that the curved centre line of

Re: Alternative music font

David Kastrup schrieb: Marc Hohl writes: Carl Sorensen schrieb: Looks good to me. I'd also like to see half-way between this attempt and the first attempt, not because I think this is wrong, but because I tend to find optimum settings by finding "not enough" and

Re: Alternative music font

Francisco Vila schrieb: Just to add a bit to the brainstorming: The uppermost lace of our G-clef already was slightly oversized. I cannot explain why, but latest proposals I've seen are getting it even greater. Anyone appreciates the same? Well spotted. I was not sure whether this is kind o

Re: [frogs] Corrected patch for Issue #830

Carl Sorensen schrieb: On 12/23/09 12:49 AM, "Marc Hohl" wrote: Marc Hohl schrieb: [...] Here it is again. Marc Is the patch I sent ok? Applying it would simplify my attempts to do some further font work (i.e. "rotating" the G clef slightly and preparin

Re: [frogs] Corrected patch for Issue #830

Mark Polesky schrieb: Marc Hohl wrote: By the way, it would be easier for you developers when the patches go directly to rietveld. How can I archieve this? Does somebody need to create an account for me? See CG "Adding or modifying features"; scroll down to 8.7.9 "

G clef changes [was: Re: Alternative music font]

Marc Hohl schrieb: Francisco Vila schrieb: Just to add a bit to the brainstorming: The uppermost lace of our G-clef already was slightly oversized. I cannot explain why, but latest proposals I've seen are getting it even greater. Anyone appreciates the same? Well spotted. I was not

Re: G clef changes [was: Re: Alternative music font]

Francisco Vila schrieb: 2009/12/29 Marc Hohl : I concatenated the pdfs to one file, which is too big for the list, so I put it on my website: http://www.hohlart.de/marc/gclef-slant.pdf I know that there is a spurious error on value 2, but I think that's not the main problem. Which

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: On 12/30/09 6:06 AM, "Marc Hohl" wrote: @Carl: I am not at all familiar with SVG. Could you please produce a file similar to the one you sent already with different rotating angles? I can only produce a file like that with the clefs you have desig

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: On 12/30/09 7:42 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: On 12/30/09 6:06 AM, "Marc Hohl" wrote: @Carl: I am not at all familiar with SVG. Could you please produce a file similar to the one you sent already with diffe

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: On 12/31/09 6:37 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: On 12/30/09 7:42 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: OK, I've attached a 300 dpi png and with the clef rotated from 0 to 4 degrees.

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: [...] Ok, so I'll go for this. It isn't as easy as I thought, because I cannot just rotate the whole picture, because the path is too complex for metafont. So I'll have to transform every point and draw thereafter. It seems to work, but I have to change some explicit draw

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: On 1/1/10 2:52 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: [...] Ok, so I'll go for this. It isn't as easy as I thought, because I cannot just rotate the whole picture, because the path is too complex for metafont. So I'l

Re: G clef changes

Han-Wen Nienhuys schrieb: On Sat, Jan 2, 2010 at 9:01 AM, Valentin Villenave wrote: On Fri, Jan 1, 2010 at 6:49 PM, David Kastrup wrote: Don't load this as a picture into firefox on X11. It is something like 1x1 pixels, and apparently firefox allocates a full-size display-dep

bends: pre-implementation issues

Hello all, I plan to work on the emplementation of bends for lilypond. Some preliminary tests with scheme were successful, so I want to go to the next stage soon and create some new engravers. But there are still some unsolved issues. But first, a brief explanation for all non-guitarists out t

Re: [tablatures] bends: pre-implementation issues

Carl Sorensen schrieb: On 1/4/10 5:38 AM, "Marc Hohl" wrote: {[..] so with bends, I have to add the commands to the parser. Is this correct? Yes, you will need to add something to the parser, I believe. It's because bends need to be spanners (they connect notes

Re: [tablatures] Re: bends: pre-implementation issues

Carl Sorensen schrieb: On 1/4/10 12:29 PM, "Marc Hohl" wrote: Han-Wen Nienhuys schrieb: On Mon, Jan 4, 2010 at 10:38 AM, Marc Hohl wrote: [...] As bends are musically and technically some sort of slurs, I think the best way to implement them is mainly to cop

Re: bends: pre-implementation issues

Oops, I just sent a mail with an attachment that seems to be too big for -devel, I don't know where the limits are for the tablature list. I'll upload it to my homepage: http://www.hohlart.de/marc/bendtest.pdf Marc ___ lilypond-devel mailing list lil

Re: [tablatures] bends: pre-implementation issues

Patrick Horgan schrieb: Marc Hohl wrote: Hello all, I plan to work on the emplementation of bends for lilypond. Some preliminary tests with scheme were successful, so I want to go to the next stage soon and create some new engravers. But there are still some unsolved issues. But first, a

Re: bends: pre-implementation issues

lar? Then most parts of the slur computation routines hadn't to be duplicated, just extended to draw pointed slurs. Marc On Mon, Jan 4, 2010 at 5:44 PM, Marc Hohl wrote: Oops, I just sent a mail with an attachment that seems to be too big for -devel, I don't know where the limits ar

Problems with git cl

Hello all, I have done some work to issue 659. I have drwan the alternate segno symbol and in addition, I'll provide new bar commands for easier use. But I don't manage to upload it to rietveld. 1) I have a google account 2) I have downloaded git-cl 3) I have a branch called "varsegno" in my

Re: bends: pre-implementation issues

Han-Wen Nienhuys schrieb: On Tue, Jan 5, 2010 at 5:36 PM, Marc Hohl wrote: Han-Wen Nienhuys schrieb: I am confused here. Are you trying to implement the symbols that are on the tab staff, or on the normal notation? Both. But first, I want to concentrate on the pointed slurs

Re: Problems with git cl

Reinhold Kainhofer schrieb: Am Mittwoch, 6. Januar 2010 09:45:20 schrieb Marc Hohl: the files, then $ git commit, then $ git format-patch origin That's not needed for git-cl and afterwards $git cl upload which I obtained from gitk & Ah, so there's the

Patch: issue #659

Hello all, I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. To start a sengo part, you can use \bar ".§" or \bar "§" at the end of the segno part, use \bar "§.". The difference between ".§"

Re: Problems with git cl

Carl Sorensen schrieb: [...] You can test this out before using git-cl by doing git diff and seeing what is reported. This is very helpful - thanks! Marc HTH, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gn

Re: Issue 659: alternate segno symbol (issue181144)

reinhold.kainho...@gmail.com schrieb: I haven't tried this out, but some things simply jump out.. http://codereview.appspot.com/181144/diff/1/3 File lily/bar-line.cc (right): http://codereview.appspot.com/181144/diff/1/3#newcode96 lily/bar-line.cc:96: Stencil segno = Font_interface::get_defaul

Re: Patch: issue #659

Neil Puttock schrieb: 2010/1/6 Marc Hohl : I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. Very nice. It's a bit different from the examples posted on the tracker,

Re: Issue 659: alternate segno symbol (issue181144)

Reinhold Kainhofer schrieb: Am Mittwoch, 6. Januar 2010 16:27:14 schrieb Marc Hohl: After consulting wikipedia for several keyboard layouts, you have convinced me. I changed the § sign to an uppercase S, which should be accessible from any latin keyboard. http://codereview.appspot.com

Re: Issue 659: alternate segno symbol (issue181144)

Werner LEMBERG schrieb: -) Compiling the font gives some warnings: Invoking "fontforge -script feta26.pe feta26.pfb"... Copyright (c) 2000-2009 by George Williams. Executable based on sources from 22:35 GMT 22-Jun-2009. Library based on sources from 22:35 GMT 22-Jun-2009. Internal

Re: Patch: issue #659

Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/6 Marc Hohl : I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. Very nice. It's a bit different from the examples pos

Re: Issue 659: alternate segno symbol (issue181144)

n.putt...@gmail.com schrieb: http://codereview.appspot.com/181144/diff/1002/1003 File input/regression/bar-line-segno.ly (right): http://codereview.appspot.com/181144/diff/1002/1003#newcode9 input/regression/bar-line-segno.ly:9: \relative \new StaffGroup << \relative c' Ok, done. I copied this

[PATCH:] Enhancement: Providing ly:grob-set-nested-property!

I posted this patch some time ago, and according to Neil's proposals, I uploaded it to rietveld. This patch features a new function similar to the already existing ly:grob-set-property! http://codereview.appspot.com/183159 ___ lilypond-devel mailing

Re: Patch: issue #659

Neil Puttock schrieb: 2010/1/8 Marc Hohl : Yes, the picture in the tracker has one loop missing, but in all other sources, the sign looked (mainly) as mine. How do they deal with the segno at the end of a line though? The tracker example is aligned as a normal barline (i.e., with

Re: Issue 659: alternate segno symbol (issue181144)

n.putt...@gmail.com schrieb: http://codereview.appspot.com/181144/diff/1009/29 File lily/span-bar.cc (right): http://codereview.appspot.com/181144/diff/1009/29#newcode204 lily/span-bar.cc:204: else if (type == "S") You also need to pick up "S."/".S" here, otherwise you'll get a nasty surprise b

Re: Patch: issue #659

Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Yes, the picture in the tracker has one loop missing, but in all other sources, the sign looked (mainly) as mine. How do they deal with the segno at the end of a line though? The tracker example is aligned as a normal

Re: Patch: issue #659

Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the barlines? I found out how to define a whiteout stencil, but it seems that it is

Re: Patch: issue #659

Trevor Daniels schrieb: Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the

Re: Patch: issue #659

Trevor Daniels schrieb: [...] I would not worry about this. As Alexander has pointed out, examples showing the staff lines extending through the sign and not extending through the sign can be found. It is easy for a user to move the sign to the end of the staff lines with \once \override

Re: Patch: issue #659

Alexander Kobel schrieb: Marc Hohl wrote: Trevor Daniels schrieb: It is easy for a user to move the sign to the end of the staff lines with \once \override Score.BarLine #'extra-offset = #'(1 . 0) \once \override Score.SpanBar #'extra-offset = #'(1 . 0) if th

Re: [PATCH]: New G clef

Carl Sorensen schrieb: Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees clockwise to improve its balance, as suggested by Jan (see <http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/24935/focus=24947>) A 1200-dpi png is available at http://www.hohlart.d

Re: [PATCH]: New G clef

Carl Sorensen schrieb: On 1/23/10 3:19 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees clockwise to improve its balance, as suggested by Jan (see <http://thread.gmane.org/gmane.comp.gnu.lilypond.deve

  1   2   3   4   5   6   7   >