Re: TextScript automatically italic in Dynamics context

, dynamics text is always italic? /DynamicText/ yes, but that is a different grob from TextScript, and semantically different. Personally, I fancy having a dedicated semantic level for something like ‘expressive mark’ (Ausdrucksbezeichnung), i.e. /dolce/ and /legato/ &c. So I defined an \ausd

Re: TextScript automatically italic in Dynamics context

huge deal. I was just curious. It looks like its been this way from the conception of the Dynamics context. - Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/TextScript-automatically-italic-in-Dynamics-context-tp180222p180224

Re: TextScript automatically italic in Dynamics context

On 26/08/15 21:42, Abraham Lee wrote: > Why is that? I see no reason that text in this context *must* be italic > by default (and I know it can be changed back). Can someone help me > understand the logic there? > Because, in pretty much every score I know, dynamics text is always italic? Cheers,

TextScript automatically italic in Dynamics context

Why is that? I see no reason that text in this context *must* be italic by default (and I know it can be changed back). Can someone help me understand the logic there? - Abraham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

f issue 1300 succeeds only because TextScript is put in a ScriptColumn with the accent. It collides in the stable release if there is no accent, or a trill in place of the accent. define-grob-properties says 'cross-staff' means that the object can change shape or move relative to its p

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

On 2014/07/26 21:36:12, Keith wrote: On 2014/07/26 06:49:41, janek wrote: > > Setting TextScript.cross-staff property to #f is required to ensure > that there are no collisions between TextScripts and cross-staff notes: > (see also beam-cross-staff-auto-knee.ly) > > As far as

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

On 2014/07/26 06:49:41, janek wrote: Setting TextScript.cross-staff property to #f is required to ensure that there are no collisions between TextScripts and cross-staff notes: (see also beam-cross-staff-auto-knee.ly) As far as I can see, we don't want TextScript.cros

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

Pushed as commit 2371d6ba3b62d4d6dc349ab50fa0d76eadfba044 Author: Janek Warchoł Date: Sun Jun 29 18:25:04 2014 +0200 Issue 4005: Set X-parent of TextScript to NoteColumn instead of PaperColumn This makes TextScripts consistent with DynamicTexts and LyricTexts. This is a follow

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

Fixed all issues identified by David. Thanks for review! Janek https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc File lily/note-column.cc (right): https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc#newcode169 lily/note-column.cc:169: if (head) Okay,

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

New patchset uploaded. https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc File lily/note-column.cc (right): https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc#newcode169 lily/note-column.cc:169: if (head) On 2014/07/11 11:10:10, dak wrote: Why would th

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc File lily/note-column.cc (right): https://codereview.appspot.com/106640043/diff/20001/lily/note-column.cc#newcode169 lily/note-column.cc:169: if (head) Why would this test become required when it wasn't before? Doesn't this

[gmane.comp.gnu.lilypond.auto] Re: Issue 2505 in lilypond: Patch: Doc: NR clarified \footnote command as a TextScript

\footnote command as a TextScript http://code.google.com/p/lilypond/issues/detail?id=2505 Ok, I am officially an idiot. When I proposed using a postevent, I had only thought about notes and rests, but footnotes may appear in a number of other places. And something like \breath <>\fo

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

New patch http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely#newcode1044 Documentation/notation/input.itely:1044: Automatically n

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

LGTM http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely#newcode1044 Documentation/notation/input.itely:1044: Automatically number

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

New Patch. Thanks Keith and Jean-Charles http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1037 Documentation/notation/in

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

Nitpicks, but I had to read twice and carefully the first paragraph and I'm not sure to understand. http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/14003/Documentation

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1075 Documentation/notation/input.itely:1075: \footnote #'(0.5 , 0.5) #'

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

Big change, still very clear. http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1048 Documentation/notation/input.itely:1

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

New patch set uploaded http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1044 Documentation/notation/input.itely:1044: Auto

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

On Sat, 12 May 2012 12:11:45 -0700, wrote: \breathe c2 \footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe } Not exactly the most intuitive order I have to say. True. Good to document it, I guess. http://codereview.appspot.com/6137050/diff/8003/Documentation/not

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

On 2012/05/12 19:25:34, dak wrote: On 2012/05/12 19:11:44, dak wrote: > On 2012/05/12 18:36:56, Keith wrote: > > > http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely > > File Documentation/notation/input.itely (right): > > > > > http://codereview.appspot.com/

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

On 2012/05/12 19:11:44, dak wrote: On 2012/05/12 18:36:56, Keith wrote: > http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely > File Documentation/notation/input.itely (right): > > http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.i

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

On 2012/05/12 18:36:56, Keith wrote: http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1073 Documentation/notation/inp

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

Looks good to me. I honestly tried to use a footnote a couple months ago, but gave up trying to figure it out. Now I think the docs are pretty clear. http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://code

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

See inline. One more patch will be needed. http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1050 Documentation/notation/

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1050 Documentation/notation/input.itely:1050: is to be attached but in t

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

New patch set uploaded for the <> change. http://codereview.appspot.com/6137050/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

On 2012/05/04 20:21:14, t.daniels_treda.co.uk wrote: wrote Friday, May 04, 2012 8:43 PM > > I think that makes more sense to explain. Definitely! I totally agree. Only allow articulation footnotes. Much clearer. Make a convert-ly rule that gives a warning if you ha

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

wrote Friday, May 04, 2012 8:43 PM Ok, everybody will love me for my late thinking again. But here we go: :) we have two cases of footnotes: one that will attach itself to whatever happens at a given point of time, being an independent event. I propose we _always_ let them try to attach

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

Ok, everybody will love me for my late thinking again. But here we go: we have two cases of footnotes: one that will attach itself to whatever happens at a given point of time, being an independent event. Those footnotes, having a natural duration of 0, come (unless they are in simultaneous musi

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

can also be attached as a On 2012/05/04 08:57:14, Trevor Daniels wrote: On 2012/05/02 06:01:47, J_lowe wrote: > if TextScript and Grob are interchangeable They're not. A TextScript is one particular type of Layout Object. It's not really a Graphical Object (grob), although th

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

/input.itely:1050: footnote is being attached but can also be attached as a On 2012/05/02 06:01:47, J_lowe wrote: if TextScript and Grob are interchangeable They're not. A TextScript is one particular type of Layout Object. It's not really a Graphical Object (grob), although the distincti

Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)

: footnote is being attached but can also be attached as a On 2012/04/30 07:39:21, Graham Percival wrote: isn't a textscript also a grob? if so, you don't need to add that in the text. The example carries that story. Possibly, I don't actually know the technical difference, I wa

Doc: NR clarified \footnote command as a TextScript (issue 6137050)

can also be attached as a isn't a textscript also a grob? if so, you don't need to add that in the text. The example carries that story. http://codereview.appspot.com/6137050/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lis

Re: [PATCH]: Fix #661: Unwanted TextScript offset when overriding TrillSpanner style (zigzag)

LGTM. On Thu, Sep 25, 2008 at 3:04 PM, Neil Puttock <[EMAIL PROTECTED]> wrote: > Hi there, > > Please review this patch here: http://codereview.appspot.com/6056 > > Regards, > Neil > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http:/

[PATCH]: Fix #661: Unwanted TextScript offset when overriding TrillSpanner style (zigzag)

Hi there, Please review this patch here: http://codereview.appspot.com/6056 Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

self-alignment-interface in TextScript

Hi, I have this working: \once \override Voice.TextScript #'self-alignment-X = #1 But in recent versions I found in define-grobsscm: ;; todo: add X self alignment? So is this interface not supported any more? Or is it a question of supporting it? Or what? Bert ___

Re: markup{} vs TextScript

: "Mats Bengtsson" <[EMAIL PROTECTED]> To: "Graham Percival" <[EMAIL PROTECTED]> Cc: "Stephen" <[EMAIL PROTECTED]>; "lilypond devel" Sent: Wednesday, May 11, 2005 4:43 AM Subject: Re: markup{} vs TextScript Related to the answer on \mark v

Re: markup{} vs TextScript

On 11-May-05, at 2:43 AM, Mats Bengtsson wrote: Related to the answer on \mark versus \markup that I just sent, I don't fully agree on the change below, since \markup can be used in several different contexts, not just for text scripts. I'd forgotten about that. Thanks for the other email, Mats. I

Re: markup{} vs TextScript

is a flat sym -- bol: \markup{\flat } } \mark \markup{...} c4^\markup{...} /Mats Graham Percival wrote: On 10-May-05, at 10:16 AM, Stephen wrote: Thinking about it even more, I realise that having a link to TextScript in the programming reference somewhere under 7.4 Text markup instead of just

Re: markup{} vs TextScript

That is a hard one because they are both accurate terms in their own right, but they stem from different sources or contexts. I think maybe markup is a false analogy and textscript is a bit more literal. Still, I am no expert and I suspect both terms are equally accurate and descriptive, which

markup{} vs TextScript

On 10-May-05, at 10:16 AM, Stephen wrote: Thinking about it even more, I realise that having a link to TextScript in the programming reference somewhere under 7.4 Text markup instead of just under 5.7.5 Text scripts to make up for the confusion in terminology that Text script and Text markup

Re: TextScript

Thinking about it even more, I realise that having a link to TextScript in the programming reference somewhere under 7.4 Text markup instead of just under 5.7.5 Text scripts to make up for the confusion in terminology that Text script and Text markup are two terms that basically describe the

Re: TextScript

|" That in the second example, you have to change the padding for RehearsalMark, TextScript padding won't affect the rehearsal mark. The two examples are nearly identical. The advantage of the second is that you can line it up to the barline explicitly instead of eyeballing it and lining

Re: TextScript

tsson" <[EMAIL PROTECTED]> To: "Stephen" <[EMAIL PROTECTED]> Cc: "lilypond devel" Sent: Tuesday, May 10, 2005 3:16 AM Subject: Re: TextScript Exactly what feature is it you want to illustrate? the padding or the \translate markup command or? By the way, wh

Re: TextScript

Sent: Tuesday, May 10, 2005 9:18 AM Subject: Re: TextScript Just add \once \override Score.RehearsalMark #'self-alignment-X = #right Simple, isn't it? :-) /Mats Stephen wrote: Sometimes, quite often really, \translate will not raise text, only move it left or right, but increasing padd

Re: TextScript

e shifting would still be necessary, although maybe right or left alignment would work better using Rehearsal Mark. Stephen - Original Message - From: "Mats Bengtsson" <[EMAIL PROTECTED]> To: "Stephen" <[EMAIL PROTECTED]> Cc: "lilypond devel" Sent: T

Re: TextScript

I think the thing I did not find intuitive is that something called TextScript affects markup. If is was just mentioned under 1.4 Text markup that TextScript affects all text markup, I would have figured that out a lot sooner. Any example that uses TextScript demonostrating that subsequent uses

Re: TextScript

On 9-May-05, at 3:17 PM, Stephen wrote: I think an example should be added to the documentation using TextScript under 5.7.5 Text scripts or 7.4 Text markup or 7.2.1 Common tweaks like this: \override Voice.TextScript #'padding = #1.2 c4 c8. c16 c4^\markup { \translate #(cons 1.75 0)

Re: TextScript

lMark #'break-visibility = #begin-of-line-invisible \mark "Fine" \bar "||" /Mats Stephen wrote: I think an example should be added to the documentation using TextScript under 5.7.5 Text scripts or 7.4 Text markup or 7.2.1 Common tweaks like this: \override Voice.TextScript

TextScript

I think an example should be added to the documentation using TextScript under 5.7.5 Text scripts or 7.4 Text markup or 7.2.1 Common tweaks like this: \override Voice.TextScript #'padding = #1.2 c4 c8. c16 c4^\markup { \translate #(cons 1.75 0) "Fine" } \breathe \bar "||&quo