Re: Footnote documentation error
Hello, On 22 April 2012 04:12, Mark Mathias wrote: > So... as far as the Bug Squad is concerned, are we still waiting for > something or does this need to get added to the tracker? > Thanks, > Mark > As far as the bug squad are concerned - being one myself - we'd like a confirmation that this is a documentation error or an unexpected/inconsistent behaviour in the code. I haven't seen a case for either yet. james ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Oldstyle Figures (OSF) from OpenType Font
> In the issue report you say, LilyPond doesn't currenty (i.e. Nov > 2010) support OpenType features. Yes. > LilyPond does support ligatures and kerning (at least on Linux, it > seems this doesn't work on Windows). Are these no OpenType features? Today, kerning is usually realized with a feature, yes. And having ligatures certainly is. > Or have there been improvements since your report? Features which are activated by default are seen by lilypond also. For example, handling of Arabic needs a lot of OpenType support, and this is provided by Pango automatically. However, we need a mechanism to activate optional features. And to answer your question from the other mail: Yes, this is a non-trivial task to implement. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flatten a tie without hardcoding control points?
At Sat, 21 Apr 2012 11:24:50 +0100,
James wrote:
> If you can come up with a simple example, we (or you even) could add
> it to the LilyPond snippet repository
Like this, perhaps? I can add it if this looks OK.
\version "2.15.36"
\include "english.ly"
\relative c'' {
% normal tie
d4 ~
% Longer ties so you can see the shapes better
% Since the minimum-length is longer, the "normal" but wider tie
% is taller than the normal, short tie.
\override Tie #'minimum-length = #7
d ~
% Low ratio = flattened
\once \override Tie #'details #'ratio = #0.05
d ~
% High ratio = taller than normal
\once \override Tie #'details #'ratio = #1
d ~
% Reduce height = not as tall, but less flat than ratio = 0.05
\once \override Tie #'details #'height-limit = #0.5
d ~
% Large height-limit
% The tie still doesn't reach the full height limit
% because 'ratio' is at its default of 0.333 here.
\once \override Tie #'details #'height-limit = #3
d4 ~
% With both tweaks you get a big, loopy tie.
\once \override Tie #'details #'ratio = #1
\once \override Tie #'details #'height-limit = #3
d4 ~
d4
}
> We don't generally document tweaks directly in the Notation Reference
> manuals - there are some but they are the exception than the rule -
> however we do often link the more useful/commonly asked tweaks as
> 'snippets' if appropriate. They will also appear in the autogenerated
> 'snippets' documentation
>
> http://lilypond.org/doc/v2.14/Documentation/snippets/index.html
Understood. I realized later that what threw me about the Tie reference was the
formatting of 'details:
'((ratio . 0.333) (center-staff-line-clearance . 0.6) (tip-staff-line-clearance
. 0.45) (note-head-gap . 0.2) (stem-gap . 0.35) (height-limit . 1.0)
(horizontal-distance-penalty-factor . 10) (same-dir-as-stem-penalty . 8)
(min-length-penalty-factor . 26) (tie-tie-collision-distance . 0.45)
(tie-tie-collision-penalty . 25.0) (intra-space-threshold . 1.25)
(outer-tie-vertical-distance-symmetry-penalty-factor . 10)
(outer-tie-length-symmetry-penalty-factor . 10)
(vertical-distance-penalty-factor . 7) (outer-tie-vertical-gap . 0.25)
(multi-tie-region-size . 3) (single-tie-region-size . 4) (between-length-limit
. 1.0))
vs, maybe something like this:
'(
(ratio . 0.333)
(center-staff-line-clearance . 0.6)
(tip-staff-line-clearance . 0.45)
(note-head-gap . 0.2)
(stem-gap . 0.35)
(height-limit . 1.0)
(horizontal-distance-penalty-factor . 10)
(same-dir-as-stem-penalty . 8)
(min-length-penalty-factor . 26)
(tie-tie-collision-distance . 0.45)
(tie-tie-collision-penalty . 25.0)
(intra-space-threshold . 1.25)
(outer-tie-vertical-distance-symmetry-penalty-factor . 10)
(outer-tie-length-symmetry-penalty-factor . 10)
(vertical-distance-penalty-factor . 7)
(outer-tie-vertical-gap . 0.25)
(multi-tie-region-size . 3)
(single-tie-region-size . 4)
(between-length-limit . 1.0)
)
In the latter, it's very easy for the eye to scan the "detail" names.
hjh
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: String Bass Notation
I'm a bass player who studied with Larry Hurst in the early 70s and a public school string teacher, so I've seen a lot of notation, but never what you are describing. The snap pizzicato has the line drawn vertically through the top of the circle only and the thumb symbol (a fingering indication --- very unlikely in the situation you describe) is a circle with the vertical line extending downward from the bottom. Both are implemented in LilyPond: c4\snappizzicato c\thumb HTH! Mark On Thu, Apr 19, 2012 at 1:48 PM, Tim Roberts wrote: > -Eluze wrote: > > Tim Roberts wrote: > >> This is a hand-drawn score. I'm thinking that they probably meant snap > >> pizzicato, and it was easier to draw the line all the way through than > >> to stop part way through. Snap pizzicato would fit in the context, and > >> I have found no source that shows the exact "phi" symbol. Have any of > >> you string players seen that notation? > > sorry, I didn't find this score - am i missing something? > > No, I didn't attach an image because I didn't get a chance to grab a > copy. I "assumed" my description would be sufficient... > > -- > Tim Roberts, t...@probo.com > Providenza & Boekelheide, Inc. > > > ___ > 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: Footnote documentation error
So... as far as the Bug Squad is concerned, are we still waiting for something or does this need to get added to the tracker? Thanks, Mark On Fri, Apr 20, 2012 at 1:52 AM, m...@apollinemike.com < m...@apollinemike.com> wrote: > On Apr 20, 2012, at 7:40 AM, James wrote: > > > Hello, > > > > On 20 April 2012 00:40, Nick Payne wrote: > >> The documentation at > >> http://lilypond.org/doc/v2.15/Documentation/notation/creating-footnotesfor > >> both automatic and manual footnotes says that the \footnote command must > >> come *before* the grob to which the footnote is being attached. This > doesn't > >> seem to be the case. Here the \footnote commands are after the notes to > >> which they are attached, and they work fine: > > > > I think this was to do with David's additional work on Mike's a few > > months ago when what he did changed the requirement from the original > > footnote document in earlier versions of 2.15. We did re-write much of > > the examples and obviously missed this. > > > > I actually think this has something to do with David's work on the parser > (could be wrong...). > > This is the postfix variety of footnote, or the one that does not need to > specify a grob and assigns the footnote to whatever grob is created by the > first event that comes down the pipe. I'm actually amazed that it works, > as the NoteHead is facultative - if you replaced it w/ Stem it'd do the > same thing (meaning footnote the NoteHead). > > Cheers, > MS > ___ > 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: Oldstyle Figures (OSF) from OpenType Font
Unfortunately that's not possible because I can't select my font
according to this.
And it's not a show stopper not to have OSF, just an inconvenience.
I assume such an improvement would be a non-trivial issue?
Best
Urs
Am 22.04.2012 02:42, schrieb Nick Payne:
On 22/04/12 08:26, Urs Liska wrote:
Thanks for pointing to this, Werner.
Just a question:
In the issue report you say, LilyPond doesn't currenty (i.e. Nov
2010) support OpenType features.
LilyPond does support ligatures and kerning (at least on Linux, it
seems this doesn't work on Windows). Are these no OpenType features?
Or have there been improvements since your report?
You could use a font that defaults to old style figures. For example,
Spectrum MT:
\relative c'' {
c4^\markup { \override #'(font-name . "SpectrumMT SC") "0123456789" }
}
___
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: Oldstyle Figures (OSF) from OpenType Font
On 22/04/12 08:26, Urs Liska wrote:
Thanks for pointing to this, Werner.
Just a question:
In the issue report you say, LilyPond doesn't currenty (i.e. Nov 2010)
support OpenType features.
LilyPond does support ligatures and kerning (at least on Linux, it
seems this doesn't work on Windows). Are these no OpenType features?
Or have there been improvements since your report?
You could use a font that defaults to old style figures. For example,
Spectrum MT:
\relative c'' {
c4^\markup { \override #'(font-name . "SpectrumMT SC") "0123456789" }
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.15.37 = destroying?
Friedrich Fischer gmail.com> writes: > I will send you a whole piece which was all right up to 2.15.36. > Version 2.15.37 destroys completely the layout Sorry about that. I've made an item on the bug tracker http://code.google.com/p/lilypond/issues/detail?id=2486 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Oldstyle Figures (OSF) from OpenType Font
Thanks for pointing to this, Werner. Just a question: In the issue report you say, LilyPond doesn't currenty (i.e. Nov 2010) support OpenType features. LilyPond does support ligatures and kerning (at least on Linux, it seems this doesn't work on Windows). Are these no OpenType features? Or have there been improvements since your report? Best Urs Am 21.04.2012 19:26, schrieb Werner LEMBERG: I may be mistaken, but I don't believe there is currently a way to do this. Perhaps post to the Bugs list as a feature request? http://code.google.com/p/lilypond/issues/detail?id=1388 Werner ___ 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: Oldstyle Figures (OSF) from OpenType Font
> I may be mistaken, but I don't believe there is currently a way to do > this. Perhaps post to the Bugs list as a feature request? http://code.google.com/p/lilypond/issues/detail?id=1388 Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Oldstyle Figures (OSF) from OpenType Font
> can anybody tell me if I can use the 'Old Style Figure' subset of an > OpenType font in markups? I may be mistaken, but I don't believe there is currently a way to do this. Perhaps post to the Bugs list as a feature request? —Josiah ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.15.37 = destroying?
Friedrich Fischer writes: > I will send you a whole piece which was all right up to 2.15.36. > Version 2.15.37 destroys completely the layout and probably also > plugins in LilypondTool prerelease. Responsible is commit f5abf75fb0a62527ea1c6339861aee34b210cc24 Author: Keith OHara Date: Sat Apr 14 23:52:56 2012 -0700 pure-rest-collision-callback: Remain on staff lines; issue 2468 -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make Tie a Slur
Quoting Nils :
Hello,
I have 70 pieces with ties and slurs here. They are already in Lilypond
with the correct syntax.
Now my publisher says he wants that ties look like slurs.
I couldn't disagree more but I have no choice here.
Any suggestions how make the ties look like slurs without changing them
all manually?
It may be possible to write an engraver that would get tie events,
hide ties and create slurs instead. But I see little motivation to do
something that won't improve music typesetting.
You may want to replace ties with macros that can expand to a slur or
to a tie.
%% Insane publisher
%tieStart = (
%tieEnd = )
% Sane publisher
tieStart = ~
tieEnd = {}
{ c'' \tieStart c'' \tieEnd }
--
Regards,
Pavel Roskin
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
2.15.37 = destroying?
I will send you a whole piece which was all right up to 2.15.36.
Version 2.15.37 destroys completely the layout and probably also plugins
in LilypondTool prerelease.
Regards Friedrich Fischer.
\version "2.15.37"
#(set-global-staff-size 20)
\paper {
ragged-last-bottom = ##f
}
\header {
title = "Ãtudes"
subtitle = "Instructives, faciles et agréables"
composer = "Mauro Giuliani, Op.100"
piece = "â 4 - Allegretto"
breakbefore = ##f
}
\layout {
\context {
\Score
autoBeaming = ##f
}
}
PartPOneVoiceOne = \relative a {
\clef "treble_8" \key a \major \time 3/4
r16 ^"I" a16 [ cis16 e16 ] r8 8 [ r8 8 ] | % 2
r16 gis16 [ d'16 e16 ] r8 8 [ r8 8 ] | % 3
r16 a16 [ cis16 e16 ] r8 8 [ r8 8 ] | % 4
r16 a16 [ cis16 e16 ] r8 8 [ r8 8 ] | % 5
r16 a16 [ b16 fis'16 ] r8 8 [ r8 8 ] | % 6
r16 a16 [ b16 fis'16 ] r8 8 [ r8 8 ] | % 7
r16 gis16 [ b16 e16 ] r8 8 [ r8 8 ] | % 8
r16 gis16 [ b16 e16 ] r8 8 [ r8 8 ] | % 9
r16 a16 [ cis16 e16 ] r8 8 [ r8 8 ] | \barNumberCheck #10
r16 gis16 [ d'16 e16 ] r8 8 [ r8 8 ] | % 11
r16 a16 [ cis16 e16 ] r8 8 [ r8 8 ] | % 12
r16 a16 [ c16 fis16 ] r8 8 [ r8 8 ] | % 13
r16 a16 [ cis!16 e16 ] r8 8 [ r8 8 ] | % 14
r16 b16 [ d16 e16 ] r8 8 [ r8 8 ] | % 15
r16 a16 [ cis16 e16 ] r8 8 [ r8 8 ] | % 16
r16 gis16 [ cis16 eis16 ] r8 8 [ r8 8 ] | % 17
r16 ^"II" a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | % 18
r16 b16 [ cis16 gis'16 ] r8 8 [ r8 8 ] | % 19
r16 a16 [ cis16 a'16 ] r8 8 [ r8 8 ] | \barNumberCheck #20
r16 a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | % 21
r16 b16 [ d16 fis16 ] r8 8 [ r8 8 ] | % 22
r16 b16 [ d16 gis16 ] r8 8 [ r8 8 ] | % 23
r16 ^"I" gis16 [ cis16 eis16 ] r8 8 [ r8 8 ] | % 24
r16 gis16 [ cis16 eis16 ] r8 8 [ r8 8 ] | % 25
r16 ^"II" a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | % 26
r16 ais16 [ cis16 g'16 ] r8 8 [ r8 8 ] | % 27
r16 b16 [ d16 fis16 ] r8 8 [ r8 8 ] | % 28
r16 a16 [ dis16 fis16 ] r8 8 [ r8 8 ] | % 29
r16 a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | \barNumberCheck #30
r16 ^"I" gis16 [ cis16 eis16 ] r8 8 [ r8 8 ] | % 31
r16 ^"II" a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | % 32
r16 a16 [ cis16 fis16 ] r8 8 [ r8 8 ] ^"I" | % 33
r16 ^"II" a16 [ cis16 fis16 ] r8 8 [ r8 8 ] | % 34
r16 a16 [ cis16 fis16 ] r8 8 [ r8 8 ] ^"I" | % 35
2 ^"II" r4 \bar "|."
}
PartPOneVoiceTwo = \relative a, {
\clef "treble_8" \key a \major \time 3/4
a4 a8 [ r8 a8 ] r8 | % 2
b4 b8 [ r8 b8 ] r8 | % 3
cis4 cis8 [ r8 cis8 ] r8 | % 4
a4 a8 [ r8 a8 ] r8 | % 5
d4 d8 [ r8 d8 ] r8 | % 6
dis4 dis8 [ r8 dis8 ] r8 | % 7
e4 e8 [ r8 e8 ] r8 | % 8
d!4 d8 [ r8 d8 ] r8 | % 9
cis4 cis8 [ r8 cis8 ] r8 | \barNumberCheck #10
b4 b8 [ r8 b8 ] r8 | % 11
a4 a8 [ r8 a8 ] r8 | % 12
dis4 dis8 [ r8 dis8 ] r8 | % 13
e4 e8 [ r8 e8 ] r8 | % 14
e,4 e'8 [ r8 e,8 ] r8 | % 15
a4 a8 [ r8 a8 ] r8 | % 16
gis4 gis8 [ r8 cis8 ] r8 | % 17
fis4 fis8 [ r8 fis8 ] r8 | % 18
eis4 eis8 [ r8 eis8 ] r8 | % 19
fis4 fis8 [ r8 fis8 ] r8 | \barNumberCheck #20
fis4 fis8 [ r8 fis8 ] r8 | % 21
d4 d8 [ r8 d8 ] r8 | % 22
b4 b8 [ r8 b8 ] r8 | % 23
cis4 cis8 [ r8 cis8 ] r8 | % 24
cis4 cis8 [ r8 cis8 ] r8 | % 25
fis4 fis8 [ r8 fis8 ] r8 | % 26
e!4 e8 [ r8 e8 ] r8 | % 27
d4 d8 [ r8 d8 ] r8 | % 28
bis4 bis8 [ r8 bis8 ] r8 | % 29
cis4 cis8 [ r8 cis8 ] r8 | \barNumberCheck #30
cis4 cis8 [ r8 cis8 ] r8 | % 31
fis,4 fis8 [ r8 fis8 ] r8 | % 32
fis4 fis8 [ r8 fis8 ] r8 | % 33
fis4 fis8 [ r8 fis8 ] r8 | % 34
fis4 fis8 [ r8 fis8 ] r8 | % 35
fis2 r4
}
% The score definition
\score {
\new Staff {
\override Score.MetronomeMark #'stencil = ##f
\tempo 4 = 92
\set Staff.instrumentName="Guit."
\set Staff.midiInstrument="acoustic guitar (nylon)"
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \voiceOne \PartPOneVoiceOne }
\context Voice = "PartPOneVoiceTwo" { \voiceTwo \PartPOneVoiceTwo }
>>
}
\midi {
}
\layout {
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flatten a tie without hardcoding control points?
James, On 21 April 2012 07:51, James Harkins wrote: > At Fri, 20 Apr 2012 06:31:20 -0500, > David Nalesnik wrote: >> Hi James, >> >> On Fri, Apr 20, 2012 at 3:32 AM, James Harkins wrote: >> >> Maybe a simple question: Is there a way to flatten the curve of a tie >> that is as easy as >> overriding "ratio" for slurs? >> >> You can override 'ratio for ties too: >> >> \override Tie #'details #'ratio = #0.2 >> >> Another possibility is to override 'height-limit: >> >> \override Tie #'details #'height-limit = #0.75 > > Ah, OK, I did see 'details but got lost in the huge pile of parameters :) > Either one of those should do it. > > I'm still learning how to use the tweaking references. That is, on the > supercollider mailing lists, I'm often pointing people to specific parts of > the help, but I've used the help for a long time and I know where things are > and how to read them. With LP, I'm starting to navigate the manuals better > but still haven't developed the 6th sense for finding that one little nugget > quickly in the middle of a long text. It'll come. If you can come up with a simple example, we (or you even) could add it to the LilyPond snippet repository http://lsr.dsi.unimi.it/ We don't generally document tweaks directly in the Notation Reference manuals - there are some but they are the exception than the rule - however we do often link the more useful/commonly asked tweaks as 'snippets' if appropriate. They will also appear in the autogenerated 'snippets' documentation http://lilypond.org/doc/v2.14/Documentation/snippets/index.html James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
