Re: Moving just text, leaving articulations in place?

[Karlin High]

On 4/19/2018 3:34 PM, David Kastrup wrote:

Correct me if I am wrong: I don't use Gmail.


Attached PNG has an annotated screenshot from the Gmail web interface.
--
Karlin High
Missouri, USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

> Correct me if I am wrong: I don't use Gmail.

Gmail completely hides previous messages by default, you have to
manually show them, which is not standard use or google would not hide
it.

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

Re: Moving just text, leaving articulations in place?

[David Kastrup]

Robert Hickman  writes:

>> Also, the LilyPond mailing list rules frown on top-posting.  Please
>> use inline quoting instead.
>
> That is how gmail works by default,

If you mean that it leaves you with the cursor at the start of the fully
quoted material: sure, how else would it prepare you for inline quoting?

It would still appear to be a user choice to just type a reply there and
hit send without doing any editing.

Correct me if I am wrong: I don't use Gmail.

-- 
David Kastrup

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

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

> As described in the Learning Manual, which has been suggested that you read, 
> \once applies to everything happening at that musical moment; \tweak applies 
> to only the object containing the \tweak.
>
> http://lilypond.org/doc/v2.19/Documentation/learning/tweaking-methods
>
> You really *should* take the time to read carefully through the Learning 
> Manual, rather than just trying to figure things out by looking at examples.  
> It will save you time in both the short and the long run.
>

I have read the learning manual but was not clear on that issue.


> Also, the LilyPond mailing list rules frown on top-posting.  Please use 
> inline quoting instead.

That is how gmail works by default, and I was not aware of that rule.

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

Re: Moving just text, leaving articulations in place?

[Carl Sorensen]

On 4/19/18, 3:52 AM, "Robert Hickman"  wrote:

Thanks, as far as I can see lilyponds modification system is based on
a stack based state machine, \override permanently changes that state
while \tweak only changes it once. Where would you use \tweak vs \once
as they appear to do the same thing?

As described in the Learning Manual, which has been suggested that you read, 
\once applies to everything happening at that musical moment; \tweak applies to 
only the object containing the \tweak.

http://lilypond.org/doc/v2.19/Documentation/learning/tweaking-methods

You really *should* take the time to read carefully through the Learning 
Manual, rather than just trying to figure things out by looking at examples.  
It will save you time in both the short and the long run.

Also, the LilyPond mailing list rules frown on top-posting.  Please use inline 
quoting instead.

Thanks,

Carl


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

Re: Moving just text, leaving articulations in place?

[David Kastrup]

Robert Hickman  writes:

> Thanks, as far as I can see lilyponds modification system is based on
> a stack based state machine, \override permanently changes that state
> while \tweak only changes it once. Where would you use \tweak vs \once
> as they appear to do the same thing?





-- 
David Kastrup

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

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

Thanks, as far as I can see lilyponds modification system is based on
a stack based state machine, \override permanently changes that state
while \tweak only changes it once. Where would you use \tweak vs \once
as they appear to do the same thing?

On 19 April 2018 at 07:55, Mark Knoop  wrote:
> At 17:38 on 18 Apr 2018, Robert Hickman wrote:
>>Tried using "\override TextScript.staff-padding" to move the text
>>annotations in the attached image up but it also moves the Larson
>>articulation symbols up as well. I want these to stay in the same
>>place and the text to move up a bit away from them. Is lilypond
>>treating the articulation symbols as text?
>>
>>\header {tagline = ""}
>>
>>{
>>\override TextScript.staff-padding = #5
>>\numericTimeSignature
>>\time 3/8
>>
>>g'4.\cut^\markup {\tiny Cut } |  g'4.\strike^\markup {\tiny
>> Strike } |
>>}
>
> Use \tweak instead of \override, viz:
>
> {
> \numericTimeSignature
> \time 3/8
>
> g'4.\cut -\tweak staff-padding #5 ^\markup {\tiny Cut } |
> g'4.\strike -\tweak staff-padding #5 ^\markup {\tiny Strike } |
> }
>
> --
> Mark Knoop
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: Moving just text, leaving articulations in place?

[Mark Knoop]

At 17:38 on 18 Apr 2018, Robert Hickman wrote:
>Tried using "\override TextScript.staff-padding" to move the text
>annotations in the attached image up but it also moves the Larson
>articulation symbols up as well. I want these to stay in the same
>place and the text to move up a bit away from them. Is lilypond
>treating the articulation symbols as text?
>
>\header {tagline = ""}
>
>{
>\override TextScript.staff-padding = #5
>\numericTimeSignature
>\time 3/8
>
>g'4.\cut^\markup {\tiny Cut } |  g'4.\strike^\markup {\tiny
> Strike } |
>}

Use \tweak instead of \override, viz:

{
\numericTimeSignature
\time 3/8

g'4.\cut -\tweak staff-padding #5 ^\markup {\tiny Cut } |  
g'4.\strike -\tweak staff-padding #5 ^\markup {\tiny Strike } |
}

-- 
Mark Knoop

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

Re: Moving just text, leaving articulations in place?

[Andrew Bernard]

Hi Robert and Simon,

I posted a code example here of how to recast the Larsen library as
articulations, not markup. You can take it from there and convert the whole
lot the same way.

Andrew


On 19 April 2018 at 08:25, Simon Albrecht  wrote:

> On 18.04.2018 18:38, Robert Hickman wrote:
>
>> Tried using "\override TextScript.staff-padding" to move the text
>> annotations in the attached image up but it also moves the Larson
>> articulation symbols up as well. I want these to stay in the same
>> place and the text to move up a bit away from them. Is lilypond
>> treating the articulation symbols as text?
>>
>
> Yes, it does, because that’s how they are implemented. ^\markup ""
> generates a TextScript grob.
> Sorry I can’t help with how to generate proper custom articulations (that
> generate Script grobs) right now – surely somebody else will be able to
> chime in.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

Is it possible to create a local context around just the text to move
them up individually and 'fake it'? I only need these secondary
annotations in this example so it woulden't be a problem overall.

I don't want to resort to hand editing the image if I can at all avoid
it. For instance if screen DPI increases and I need to re render the
images. They are automatically converted by my CMS, so I'd only need
to change the dpi and purge the cache. Anything changed manually would
need to be re done manually and would probably be forgotten about. I
am not using SVG due to a font sizing inconsistency I've noted before
and can't be bothered to look into.

On 18 April 2018 at 23:25, Simon Albrecht  wrote:
> On 18.04.2018 18:38, Robert Hickman wrote:
>>
>> Tried using "\override TextScript.staff-padding" to move the text
>> annotations in the attached image up but it also moves the Larson
>> articulation symbols up as well. I want these to stay in the same
>> place and the text to move up a bit away from them. Is lilypond
>> treating the articulation symbols as text?
>
>
> Yes, it does, because that’s how they are implemented. ^\markup "" generates
> a TextScript grob.
> Sorry I can’t help with how to generate proper custom articulations (that
> generate Script grobs) right now – surely somebody else will be able to
> chime in.
>
> Best, Simon

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

Re: Moving just text, leaving articulations in place?

[Simon Albrecht]

On 18.04.2018 18:38, Robert Hickman wrote:

Tried using "\override TextScript.staff-padding" to move the text
annotations in the attached image up but it also moves the Larson
articulation symbols up as well. I want these to stay in the same
place and the text to move up a bit away from them. Is lilypond
treating the articulation symbols as text?


Yes, it does, because that’s how they are implemented. ^\markup "" 
generates a TextScript grob.
Sorry I can’t help with how to generate proper custom articulations 
(that generate Script grobs) right now – surely somebody else will be 
able to chime in.


Best, Simon

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

Moving just text, leaving articulations in place?

[Robert Hickman]

Tried using "\override TextScript.staff-padding" to move the text
annotations in the attached image up but it also moves the Larson
articulation symbols up as well. I want these to stay in the same
place and the text to move up a bit away from them. Is lilypond
treating the articulation symbols as text?

Complete below, my code is at the bottom:

\version "2.18.2"

% Copyright © 2014, Bret Pimentel. http://bretpimentel.com


% HOW TO USE

  % 1. Put this file in the same folder as the .ly file you are
working on, or, even better, somewhere in your Lilypond include path.
  % 2. Add the following line near the top of your .ly file, under the
"version" line (do not include the percent sign):
  %  \include "larsen-symbols.ily"
  % 3. Add symbols to notes using this syntax (no percent sign):
  %  c\crann
  % The following symbols are available:
  %cut
  %strike
  %slideUp
  %slideDown
  %longRoll
  %shortRoll
  %longDoubleCutRoll
  %shortDoubleCutRoll
  %crann
  %shortCrann
  %trill
  %singleTrill
  %shake
  %breathe
  % ("trill" and "breathe" are already built into Lilypond, but are
listed here because they form part of Mr. Larsen's system of symbols.)
  % For a thorough introduction to Mr. Larsen's excellent
ornamentation system, buy this book (affiliate link):
http://www.amazon.com/gp/product/0786649429/ref=as_li_tl?ie=UTF8=1789=390957=0786649429=as2=bretpimewood-20=DQYNUO6ZFISH6REA


% OPTIONS -- ADJUST AS DESIRED

  larsenSymbolsScale = #1.5
% Adjust this to scale all symbols up or down (default #1.5).
Known issue: adjusting this affects the spacing of the components of
the long and short double-cut roll symbols.

  larsenSymbolsOutlineWidth = #.065
% Adjust this to change outline thicknesses for all symbols.

% DON'T CHANGE ANYTHING BELOW HERE UNLESS YOU KNOW WHAT YOU'RE DOING


% SOME VARIABLES
  larsenSymbolsHalignFactor = #(+ (* larsenSymbolsScale ( / 2 3 ) )
.15 ) % this is an arbitrary number discovered by trial and error; it
helps keep the symbols roughly aligned with noteheads if the symbols
are resized using \larsenSymbolsScale
  larsenSymbolsHalfSize = #(* .5 larsenSymbolsScale)
  larsenSymbolsFlipVertical = #(* -1 larsenSymbolsScale)

% SYMBOL: CUT

  cutCoordinates =   #'(
(.4 .9)
(.55 .825)
  )

  cutStencil =
\markup \halign #(/ -3 larsenSymbolsHalignFactor) \stencil
#(make-connected-path-stencil
  cutCoordinates
  larsenSymbolsOutlineWidth
  larsenSymbolsScale
  larsenSymbolsScale
  #t
  #t
)

  cut = ^\cutStencil

  tinyCutStencil = % The "tiny cut" is used as a component of some of
the more complex symbols
\markup \stencil
#(make-connected-path-stencil
  cutCoordinates
  larsenSymbolsOutlineWidth
  larsenSymbolsHalfSize
  larsenSymbolsHalfSize
  #t
  #t
)

  tinyCut = \tinyCutStencil

  tinyCuts =
\markup
  \halign #(/ -6.25 larsenSymbolsHalignFactor) \raise #(/ .35
larsenSymbolsHalignFactor)
  \combine
\tinyCut
\halign #(/ .25 larsenSymbolsHalignFactor) \raise #(/ .2
larsenSymbolsHalignFactor) \tinyCut

% SYMBOL: STRIKE

  strikeStencil = \markup \halign #(/ -1.75 larsenSymbolsHalignFactor) \stencil
#(make-connected-path-stencil
  '(
(.234 .831)
(.156 .831)
(-.012 .317)
(-.156 .831)
(-.293 .831)
   )
  larsenSymbolsOutlineWidth
  larsenSymbolsScale
  larsenSymbolsScale
  #t
  #t
)

  strike = ^\strikeStencil

%-
\header {tagline = ""}

{
\override TextScript.staff-padding = #5
\numericTimeSignature
\time 3/8

g'4.\cut^\markup {\tiny Cut } |  g'4.\strike^\markup {\tiny Strike } |
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user