Re: [Patch:] Tablature: provide custom fret labels

Am 27.11.2010 21:12, schrieb Carl Sorensen: Marc, Do you have a regtest file that uses the custom fret label? Now I do ;-) Thanks, Marc >From a34ec51095cdc2f5e06e847c85fcd86b95ae7b1e Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Tue, 23 Nov 2010 21:18:25 +0100 Subject: [PA

Re: [Patch:] Tablature: provide custom fret labels

Marc, Do you have a regtest file that uses the custom fret label? Thanks, Carl On 11/27/10 11:46 AM, "Marc Hohl" wrote: > Am 27.11.2010 15:27, schrieb Carl Sorensen: >> [...] >> TabNoteHead supports the text-interface, which has a 'text property. It's >> in the Internals reference. >> >

Re: [Patch:] Tablature: provide custom fret labels

Am 27.11.2010 15:27, schrieb Carl Sorensen: [...] TabNoteHead supports the text-interface, which has a 'text property. It's in the Internals reference. Thanks for clarification - I just saw that you included this in your recent patch, in combination with the harmonic/parentheses stuff - gr

Re: [Patch:] Tablature: provide custom fret labels

On 11/27/10 2:24 AM, "Marc Hohl" wrote: > Am 27.11.2010 02:41, schrieb Carl Sorensen: >> >> >> On 11/24/10 12:40 AM, "Marc Hohl" wrote: >> >> >>> Am 24.11.2010 00:41, schrieb Neil Puttock: >>> On 23 November 2010 23:30, Carl Sorensen wrote: > Pushed,

Re: [Patch:] Tablature: provide custom fret labels

Am 27.11.2010 02:41, schrieb Carl Sorensen: On 11/24/10 12:40 AM, "Marc Hohl" wrote: Am 24.11.2010 00:41, schrieb Neil Puttock: On 23 November 2010 23:30, Carl Sorensen wrote: Pushed, thanks. That was quick, thanks! I'm sorry I'm a bit late, but thi

Re: [Patch:] Tablature: provide custom fret labels

On 11/24/10 12:40 AM, "Marc Hohl" wrote: > Am 24.11.2010 00:41, schrieb Neil Puttock: >> On 23 November 2010 23:30, Carl Sorensen wrote: >> >> >>> Pushed, thanks. >>> > That was quick, thanks! >> I'm sorry I'm a bit late, but this >> >> +(define-markup-command (customFretLabel >> +

Re: [Patch:] Tablature: provide custom fret labels

On 24 November 2010 07:40, Marc Hohl wrote: > I attached a patch to remove the unnecessary markup definition. Thanks, applied. Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Patch:] Tablature: provide custom fret labels

for the fret numbers, so I removed the font stuff. I attached a patch to remove the unnecessary markup definition. Regards, Marc Cheers, Neil From 87fc9dbd0217658c85fa120c8e2aa0afcf3b492a Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Wed, 24 Nov 2010 08:37:07 +0100 Subject: [PATCH] Tablat

Re: [Patch:] Tablature: provide custom fret labels

On 23 November 2010 23:30, Carl Sorensen wrote: > Pushed, thanks. I'm sorry I'm a bit late, but this +(define-markup-command (customFretLabel +layout props fret-label) (string?) seems unncessary; it's just an inferior version of vcenter. There's nothing about i

Re: [Patch:] Tablature: provide custom fret labels

On 11/23/10 1:23 PM, "Marc Hohl" wrote: > Hello everybody, > > this small patch extends lilypond's tablature features. > It provides a custom callback to print a given string instead of the > fret number. > > This patch is needed for providing proper harmonics support (i.e. declaring > guita

[Patch:] Tablature: provide custom fret labels

From a34ec51095cdc2f5e06e847c85fcd86b95ae7b1e Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Tue, 23 Nov 2010 21:18:25 +0100 Subject: [PATCH] tablature: provide custom fret labels --- scm/tablature.scm | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/scm/tablatur

Re: [Patch:] tablature support for text spanners in full notation

Marc Hohl schrieb: Hello all, here is a small patch that provides proper support for text spanners in combination with \tabFullNotation. ... or is anything wrong with it? (I know, tablature is not important for most users, but still ... :-) Marc Greetings, Marc --

[Patch:] tablature support for text spanners in full notation

Hello all, here is a small patch that provides proper support for text spanners in combination with \tabFullNotation. Greetings, Marc From 9ca52bd5be89a5e03b7a4c930154081c1c84f9d5 Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Fri, 1 Oct 2010 08:36:45 +0200 Subject: [PATCH] tablature

Re: patch: tablature and MultiMeasureRestNumber

On 10/16/09 2:04 AM, "Trevor Daniels" wrote: >> > > Thanks Marc - pushed to origin/master. > > (Hope that's OK, Carl) Perfect! I've been off the web, so haven't been able to respond. Thanks! Carl > > Trevor > > > > ___ lilypond-devel m

Re: patch: tablature and MultiMeasureRestNumber

Marc Hohl wrote Friday, October 16, 2009 7:30 AM 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

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 a

Re: patch: tablature and MultiMeasureRestNumber

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 a reworked patch Look

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

2009 7:14 AM Subject: 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

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

[PATCH]: Tablature support

I've posted Marc Hohl's excellent work on improved tab support on rietveld for your review. Please review the patch, located at Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.g

Re: [PATCH] Tablature stem spacing correction

Hi, -0.45 works fine in my setup, it should be good for others, but I don't know. By default the noteheads seem to be aligned to the tab lines, just over them, as in this picture: http://personales.ya.com/v_s_d/tab_default.png The correct offset should place them so the line crosses them

Re: [PATCH] Tablature stem spacing correction

I must be very tired to have posted such an obvious wrong patch. It does of course not fix the problem (the fix was that I at the same time did an \override TabNoteHead #'extra-offset = #'(0 . -0.4)). Sorry 'bout the confusion.On 6/13/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Erlend Aasland w

Re: [PATCH] Tablature stem spacing correction

On Sunday 12 June 2005 23.58, Erlend Aasland wrote: > Hi Han-Wen > > Tablature noteheads misaligned (they are too high above the lines). Please > apply this fix: > > 2005-06-12 Erlend Aasland <[EMAIL PROTECTED]> > > * scm/define-grobs.scm: spacing correction for tablature noteheads Vincent said th

Re: [PATCH] Tablature stem spacing correction

Erlend Aasland wrote: Hi Han-Wen Tablature noteheads misaligned (they are too high above the lines). Please apply this fix: 2005-06-12 Erlend Aasland <[EMAIL PROTECTED] > * scm/define-grobs.scm: spacing correction for tablature noteheads How does this patch rela

[PATCH] Tablature stem spacing correction

Hi Han-Wen Tablature noteheads misaligned (they are too high above the lines). Please apply this fix: 2005-06-12  Erlend Aasland  <[EMAIL PROTECTED]> * scm/define-grobs.scm: spacing correction for tablature noteheads stemcorrect.patch Description: Binary data __

[PATCH] Tablature + doc

[EMAIL PROTECTED] writes: > Hi ! > > This patch (for the CVS) includes a few documentation (in refman.itely) and > fixes some bug: > > - stringTunings now has a doc string > - default tuning is (should be ? ;-) now right > - tablature with even number of strings works. > > Jiba ok, added to

[PATCH] Tablature + doc

Hi ! This patch (for the CVS) includes a few documentation (in refman.itely) and fixes some bug: - stringTunings now has a doc string - default tuning is (should be ? ;-) now right - tablature with even number of strings works. Jiba tab-lily-5.patch Description: Binary data

Re: [PATCH] Tablature

Lamy Jean-Baptiste wrote: > - default string tuning is now at the right octavo Eh, no, you transposed the wrong direction, now it is TWO octaves off. The high e-string should end up between the two upper note-lines when notated in the "G_8"-clef. -Rune __

[PATCH] Tablature

[EMAIL PROTECTED] writes: > Hi ! > > This patch (intended to be applied to the CVS) fix the following bugs : > > - stringTunings property is now declared > - Accidental are now totally removed (before, there were just transparent, > but it seems it can cause crash) > - default string tuning i

[PATCH] Tablature

Hi ! This patch (intended to be applied to the CVS) fix the following bugs : - stringTunings property is now declared - Accidental are now totally removed (before, there were just transparent, but it seems it can cause crash) - default string tuning is now at the right octavo - up-to-staff S

Re: [PATCH] Tablature in LilyPond

On Wed, Jun 05, 2002 at 05:23:41PM +0200, Han-Wen Nienhuys wrote: >[EMAIL PROTECTED] writes: >> I would really like if you would stick to no-direction >> finger-markings in the example (i.e. c'-2 instead of c'^2). This way >> we allow for c_3 and c^3 to mean other things in the future - I still >>

Re: [PATCH] Tablature in LilyPond

[EMAIL PROTECTED] writes: > I would really like if you would stick to no-direction finger-markings > in the example (i.e. c'-2 instead of c'^2). This way we allow for c_3 > and c^3 to mean other things in the future - I still like the idea of > entering notes by fret instead of by string. Anot

Re: [PATCH] Tablature in LilyPond

Rune Zedeler wrote: > Of course this is not a real problem when > custom string tunings are introduced. (soon, hopefully?) Sorry, silly me. Well, the comment about TabNoteHead \override #'string-tunings is antiquated, though... -Rune ___ Lilypon

Re: [PATCH] Tablature in LilyPond

Okay, I took a loog at the patch. Generally it looks very nice! :-) I have a few comments though. The string tuning is an octave off! I know that guitar traditionally is notated an octave above where it actually sounds, but I prefer solving this by keeping the tunings in their real octave and t

Re: [PATCH] Tablature in LilyPond

Lamy Jean-Baptiste wrote: > Here is the third version of the tablature patch; this one should be > applied on the CVS version of Lilypond (which already contains the previous > patch). I applied from cvs. I have problems with building the documentation: ... Processing stem-interface ... Process

Re: [PATCH] Tablature in LilyPond

Lamy Jean-Baptiste <[EMAIL PROTECTED]> writes: > Here is the third version of the tablature patch; this one should be > applied on the CVS version of Lilypond (which already contains the previous > patch). This looks very nice, but aren't the numbers a bit small and thin? In LilyPond we try to u

Re: [PATCH] Tablature in LilyPond

[EMAIL PROTECTED] writes: > Changelog > - The example "tablature.ly" has been modified so it now display both > tablature and normal staff. > - The new Stem property "up-to-staff" can be used to have all stem ending > out of the staff (as it is in typical tab) > - The following feature has been

Re: [PATCH] Tablature in LilyPond

Hi, Here is the third version of the tablature patch; this one should be applied on the CVS version of Lilypond (which already contains the previous patch). Changelog - The example "tablature.ly" has been modified so it now display both tablature and normal staff. - The new Stem property "up-t

[PATCH] Tablature in LilyPond

[EMAIL PROTECTED] writes: > Here is the new version of the tablature patch for Lilypond (1.5.55) ! > > The input/test/tablature.ly file is an exemple. I've added your code with minor modifications to CVS. Is this code production quality (ie. ready for unsuspecting users)? If so, some documentat

[PATCH] Tablature in LilyPond

Hi, Here is the new version of the tablature patch for Lilypond (1.5.55) ! The input/test/tablature.ly file is an exemple. > >+\translator { > >+ \StaffContext > >+ > > you'll probably want to insert \name TabStaff over here, so you can > use normal and tab staffs in the same