Re: Multiple Endings Problem
On Fri, 2 Jan 2015 03:30:35 +0100 Thomas Morley wrote: >> After inserteing statements for version, language and relative c' i've > got the attached output. > Can't see a problem If you put some measures before this code, you'll notice the |: bar . -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Multiple Endings Problem
On 02/01/2015 12:36, William Marchant wrote:
I am using the code below to set up two different endings for a song.
The code shown automatically puts
a Repeat Start bar line at the beginning of of Bar 29. I would like
to suppress it but can only do so with a Tick Bar Line. This looks a
bit odd. No other Bar Line seems to work. Is there a method for what
I want to do?
Bill
\repeat volta 2 {bf'8~ bf a a g4( f)| } %Bar 29
\alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) \bar ":|."} %Bar 30
31 32
{c2 e4( d' | c1) |c4( c bf) a( |
c4. bf8 a4 bf)} %Bar 33 34 35 36
}
Are you actually repeating, or just allowing allowing two alternative
endings? If the latter, why not use an ossia instead.
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Multiple Endings Problem
> On 2 Jan 2015, at 02:36, William Marchant wrote:
>
> I am using the code below to set up two different endings for a song. The
> code shown automatically puts
> a Repeat Start bar line at the beginning of of Bar 29. I would like to
> suppress it but can only do so with a Tick Bar Line. This looks a bit odd.
> No other Bar Line seems to work. Is there a method for what I want to do?
> Bill
>
> \repeat volta 2 {bf'8~ bf a a g4( f)| } %Bar 29
> \alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) \bar ":|."} %Bar 30 31 32
>{c2 e4( d' | c1) |c4( c bf) a( |
> c4. bf8 a4 bf)} %Bar 33 34 35 36
> }
There may be a bug: with some bars added ahead, one should be able to use \bar
"|", but it still typesets \bar ".|:". One can use \bar "", though.
The \bar ":|.” above is unnecessary. Also, if the \repeat volta does not
encompass all music repeated, \unfoldRepeats will not expand MIDI correctly.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
try : c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
2015-01-02 6:13 GMT+01:00 Ryan Clarin :
> This should be as simple as adding a hyphen with the finger number, but
> they are not showing up. For example, when I try to place a f chord fret
> diagram above a melody note:
>
> c,^markup { \fret-diagram-terse #"2-2;o;1-1;o;" }
>
> It prints a f chord chart but with no fingerings :( help!
>
>
>
> ___
> 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: Multiple Endings Problem
2015-01-02 10:34 GMT+01:00 Hans Aberg :
>
>> On 2 Jan 2015, at 02:36, William Marchant wrote:
>>
>> I am using the code below to set up two different endings for a song. The
>> code shown automatically puts
>> a Repeat Start bar line at the beginning of of Bar 29. I would like to
>> suppress it but can only do so with a Tick Bar Line. This looks a bit odd.
>> No other Bar Line seems to work. Is there a method for what I want to do?
>> Bill
>>
>> \repeat volta 2 {bf'8~ bf a a g4( f)| } %Bar 29
>> \alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) \bar ":|."} %Bar 30 31 32
>>{c2 e4( d' | c1) |c4( c bf) a( |
>> c4. bf8 a4 bf)} %Bar 33 34 35 36
>> }
>
> There may be a bug: with some bars added ahead, one should be able to use
> \bar "|", but it still typesets \bar ".|:". One can use \bar "", though.
>
> The \bar ":|.” above is unnecessary. Also, if the \repeat volta does not
> encompass all music repeated, \unfoldRepeats will not expand MIDI correctly.
\version "2.19.15"
\language "english"
\relative c' {
c1
\once \set Staff.whichBar = #"|"
\repeat volta 2 { bf'8~ bf a a g4( f)| } %Bar 29
\alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) } %Bar 30 31 32
{c2 e4( d' | c1) |c4( c bf) a( |
c4. bf8 a4 bf)} %Bar 33 34 35 36
}
}
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Multiple Endings Problem
The code suggested by Thomas Morley, using the "\once \set Staff"
line solves my problem.
The bug, if it is one seems to lie in the fact that other code precedes
my example code. I did not realise that my code would run correctly
without the preceding code. An ossia would not suit me because I wanted
the horizontal lines which designate which verses of the song the
endings were to follow. Thanks for all the replies.
Bill
On 15-01-02 07:06 AM, Thomas Morley wrote:
2015-01-02 10:34 GMT+01:00 Hans Aberg :
On 2 Jan 2015, at 02:36, William Marchant wrote:
I am using the code below to set up two different endings for a song. The code
shown automatically puts
a Repeat Start bar line at the beginning of of Bar 29. I would like to
suppress it but can only do so with a Tick Bar Line. This looks a bit odd. No
other Bar Line seems to work. Is there a method for what I want to do?
Bill
\repeat volta 2 {bf'8~ bf a a g4( f)| } %Bar 29
\alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) \bar ":|."} %Bar 30 31 32
{c2 e4( d' | c1) |c4( c bf) a( |
c4. bf8 a4 bf)} %Bar 33 34 35 36
}
There may be a bug: with some bars added ahead, one should be able to use \bar "|", but it still
typesets \bar ".|:". One can use \bar "", though.
The \bar ":|.” above is unnecessary. Also, if the \repeat volta does not
encompass all music repeated, \unfoldRepeats will not expand MIDI correctly.
\version "2.19.15"
\language "english"
\relative c' {
c1
\once \set Staff.whichBar = #"|"
\repeat volta 2 { bf'8~ bf a a g4( f)| } %Bar 29
\alternative{ { c2 e4( g4) |f1 | r2 r4 g8( f) } %Bar 30 31 32
{c2 e4( d' | c1) |c4( c bf) a( |
c4. bf8 a4 bf)} %Bar 33 34 35 36
}
}
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
It does not work - I got it to work by including a long override string.
On Friday, January 2, 2015, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> try : c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
>
>
> 2015-01-02 6:13 GMT+01:00 Ryan Clarin >:
>
>> This should be as simple as adding a hyphen with the finger number, but
>> they are not showing up. For example, when I try to place a f chord fret
>> diagram above a melody note:
>>
>> c,^markup { \fret-diagram-terse #"2-2;o;1-1;o;" }
>>
>> It prints a f chord chart but with no fingerings :( help!
>>
>>
>>
>> ___
>> 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: Alternative fonts glyph support
tisimst wrote > That being said, if no one complains too loudly, I think I may remove > support for them. What think ye all? No complaints? That's not a problem. I guess I'll think about it a little more before proceeding... -Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170040.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alternative fonts glyph support
Am 02.01.2015 um 20:35 schrieb tisimst: tisimst wrote That being said, if no one complains too loudly, I think I may remove support for them. What think ye all? No complaints? That's not a problem. Maybe this is because nobody (who noticed the post) really understands the implications? Urs I guess I'll think about it a little more before proceeding... -Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170040.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alternative fonts glyph support
Urs Liska wrote > Am 02.01.2015 um 20:35 schrieb tisimst: >> No complaints? That's not a problem. > > Maybe this is because nobody (who noticed the post) really understands > the implications? > > Urs That's fair. The implication is this: If you need to use more than the standard glyph set (e.g., the common noteheads, clefs, articulations, time signature numerals, accidentals, etc.) then you may have to use Emmentaler instead of, say, Haydn, or at least a mixture of the two. The biggest examples of this are the shape-note noteheads and ancient chant glyphs (i.e., petrucci, kievan, etc.). Does that make more sense? -Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170043.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
Please send us a compilable exemple (showing what goes wrong), e.g. :
\version "2.18.2"
{
c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
}
which, on my side, works perfectly !
2015-01-02 17:38 GMT+01:00 Ryan Clarin :
> It does not work - I got it to work by including a long override string.
>
>
> On Friday, January 2, 2015, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
>> try : c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
>>
>>
>> 2015-01-02 6:13 GMT+01:00 Ryan Clarin :
>>
>>> This should be as simple as adding a hyphen with the finger number, but
>>> they are not showing up. For example, when I try to place a f chord fret
>>> diagram above a melody note:
>>>
>>> c,^markup { \fret-diagram-terse #"2-2;o;1-1;o;" }
>>>
>>> It prints a f chord chart but with no fingerings :( help!
>>>
>>>
>>>
>>> ___
>>> 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: Alternative fonts glyph support
Am 02.01.2015 um 21:21 schrieb tisimst: Urs Liska wrote Am 02.01.2015 um 20:35 schrieb tisimst: No complaints? That's not a problem. Maybe this is because nobody (who noticed the post) really understands the implications? Urs That's fair. The implication is this: If you need to use more than the standard glyph set (e.g., the common noteheads, clefs, articulations, time signature numerals, accidentals, etc.) then you may have to use Emmentaler instead of, say, Haydn, or at least a mixture of the two. The biggest examples of this are the shape-note noteheads and ancient chant glyphs (i.e., petrucci, kievan, etc.). Does that make more sense? Do I get this right: - Currently you create new fonts that contain the same set of glyphs as Emmentaler, but with quite a number of original Emmentaler glyphs. - You suggest to strip these literal copies from the alternative fonts to avoid redundancy. ? Hm ... If these assumptions are correct then I think I'd prefer redundancy in this case because otherwise you'd encounter problems that are hard to understand when LilyPond doesn't seem to print all glyphs anymore. Maybe it would be a good idea to produce glyph tables for the fonts that clearly state which glyphs are Emmentaler copies, but basically I'd prefer complete fonts. Except you could come up with a way to let LilyPond select Emmentaler glyphs as fallback when a glyph is missing from the selected font. That would be a clean solution IMO. HTH Urs -Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170043.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
2015-01-02 21:26 GMT+01:00 Pierre Perol-Schneider
:
> Please send us a compilable exemple (showing what goes wrong), e.g. :
>
> \version "2.18.2"
>
> {
> c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> }
>
> which, on my side, works perfectly !
I think the problem was to print the fretdiagram _with_ fingering.
Try:
\version "2.18.2"
{
c''1^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
\once \override TextScript.fret-diagram-details.finger-code = #'in-dot
c''^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
\once \override TextScript.fret-diagram-details.finger-code = #'below-string
c''^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
}
%% other syntax
{
c''1^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
c''1^\markup
\override #'(fret-diagram-details . ((finger-code . in-dot)))
\fret-diagram-terse #"2-2;o;1-1;o;"
c''1^\markup
\override #'(fret-diagram-details . ((finger-code . below-string)))
\fret-diagram-terse #"2-2;o;1-1;o;"
}
Though, I think it's well covered in the NR.
http://www.lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-fretted-strings#fret-diagram-markups
Ryan could you suggest something how we could improve the docs, so
that the problem finding the relevant explanation will be avoided in
future?
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
I could not find that \override string anywhere. Using the terse form of
fret-diagram, simply adding a hyphen should have put fingerings below
automatically but on mine it does not! This is version 2.18.2. However
another user did send me the override string and I got them to appear.
On Friday, January 2, 2015, Thomas Morley wrote:
> 2015-01-02 21:26 GMT+01:00 Pierre Perol-Schneider
> >:
> > Please send us a compilable exemple (showing what goes wrong), e.g. :
> >
> > \version "2.18.2"
> >
> > {
> > c,^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> > }
> >
> > which, on my side, works perfectly !
>
>
>
> I think the problem was to print the fretdiagram _with_ fingering.
>
> Try:
>
> \version "2.18.2"
>
> {
> c''1^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> \once \override TextScript.fret-diagram-details.finger-code = #'in-dot
> c''^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> \once \override TextScript.fret-diagram-details.finger-code =
> #'below-string
> c''^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> }
>
> %% other syntax
>
> {
> c''1^\markup\fret-diagram-terse #"2-2;o;1-1;o;"
> c''1^\markup
> \override #'(fret-diagram-details . ((finger-code . in-dot)))
> \fret-diagram-terse #"2-2;o;1-1;o;"
> c''1^\markup
> \override #'(fret-diagram-details . ((finger-code .
> below-string)))
> \fret-diagram-terse #"2-2;o;1-1;o;"
> }
>
>
> Though, I think it's well covered in the NR.
>
> http://www.lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-fretted-strings#fret-diagram-markups
> Ryan could you suggest something how we could improve the docs, so
> that the problem finding the relevant explanation will be avoided in
> future?
>
> Cheers,
> Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue Including fingering indications on fret-diagram-terse string
2015-01-02 22:31 GMT+01:00 Ryan Clarin :
> I could not find that \override string anywhere. Using the terse form of
> fret-diagram, simply adding a hyphen should have put fingerings below
> automatically but on mine it does not! This is version 2.18.2.
Why do you think so?
I copy from 2.18.-NR:
"
Fingering indications can be included in the fret-diagram-terse markup string.
<<
\new ChordNames {
\chordmode {
c1 d:m
}
}
\new Staff {
\override Voice.TextScript.fret-diagram-details.finger-code = #'below-string
\clef "treble_8"
1^\markup {
\fret-diagram-terse #"x;3-3;2-2;o;1-1;o;"
}
1^\markup {
\fret-diagram-terse #"x;x;o;2-2;3-3;1-1;"
}
}
>>
"
The IR
http://www.lilypond.org/doc/v2.18/Documentation/internals-big-page#fret_002ddiagram_002dinterface
"
3.2.39 fret-diagram-interface
[...]
fret-diagram-details
[...]
finger-code – Code for the type of fingering indication used. Options
include none, in-dot, and below-string. Default *none* for markup fret
diagrams, below-string for FretBoards fret diagrams.
[...]
"
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alternative fonts glyph support
Am 02.01.2015 um 20:35 schrieb tisimst: > tisimst wrote >> That being said, if no one complains too loudly, I think I may remove >> support for them. What think ye all? > > No complaints? That's not a problem. I guess I'll think about it a little > more before proceeding... Dear Abraham, I didn’t want to complain before I understand your point correctly. To understand it, I wanted to test your fonts how they behave when using such symbols. As I had no time up to now, I just ask my questions, even if I could have found out myself. Could you please clarify, if I understood you correctly? 1. The current situation is: a) If I use a font which has no gregorian chant glyphs, the corresponding Emmentaler glyphs are in that font and they are used. Is that right? b) If it comprises those glyphs, they are used (Profondo), right? 2. You want: a) Writing greg. chant with such a font that does not support it, is not possible anymore. I could however switch to another font for just this context or even a single symbol if I want that (e.g. engrave a VaticanaStaff using Emmentaler and a Staff in the same score using Haydn or I could put a Profondo special symbol in a score that uses Beethoven which does not support this symbol.) b) More exotic glyphs that are present in a font are still available (e.g. greg. chant is still possible with Profondo)? If that is the case, I would prefer complete fonts that can do anything LilyPond can do. But I could also live with that change, given that I can work around this by using different fonts in the same score. Is it possible to implement some kind of cascade in LilyPond: That it uses the chosen font (e.g. Haydn) and if a symbol is not available it has a fallback to Emmentaler which contains all symbols. That way the font would not need to provide the fallback but LP itself. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
programming error: Improbable offset for stencil: nan staff space
Hi First of all: Happy new year to all of you. Does someone knows the meaning of this programming error ?: programming error: Improbable offset for stencil: nan staff space Setting to zero. continuing, cross fingers Searched on the net but couldn't find a reasonable answer. Best K ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alternative fonts glyph support
Am 02.01.2015 um 23:42 schrieb Noeck: Am 02.01.2015 um 20:35 schrieb tisimst: tisimst wrote That being said, if no one complains too loudly, I think I may remove support for them. What think ye all? No complaints? That's not a problem. I guess I'll think about it a little more before proceeding... Dear Abraham, I didn’t want to complain before I understand your point correctly. To understand it, I wanted to test your fonts how they behave when using such symbols. As I had no time up to now, I just ask my questions, even if I could have found out myself. Could you please clarify, if I understood you correctly? 1. The current situation is: a) If I use a font which has no gregorian chant glyphs, the corresponding Emmentaler glyphs are in that font and they are used. Is that right? b) If it comprises those glyphs, they are used (Profondo), right? 2. You want: a) Writing greg. chant with such a font that does not support it, is not possible anymore. I could however switch to another font for just this context or even a single symbol if I want that (e.g. engrave a VaticanaStaff using Emmentaler and a Staff in the same score using Haydn or I could put a Profondo special symbol in a score that uses Beethoven which does not support this symbol.) b) More exotic glyphs that are present in a font are still available (e.g. greg. chant is still possible with Profondo)? If that is the case, I would prefer complete fonts that can do anything LilyPond can do. But I could also live with that change, given that I can work around this by using different fonts in the same score. Is it possible to implement some kind of cascade in LilyPond: That it uses the chosen font (e.g. Haydn) and if a symbol is not available it has a fallback to Emmentaler which contains all symbols. That way the font would not need to provide the fallback but LP itself. Cheers, Joram I have the impression that Joram didn't read my last post before writing his but essentially wrote exactly the same as I did. If that's true I think that should be quite telling, isn't it? Urs ___ 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: Alternative fonts glyph support
> I have the impression that Joram didn't read my last post before writing > his but essentially wrote exactly the same as I did. > If that's true I think that should be quite telling, isn't it? Yes, I only read it afterwards and I agree that it essentially has the same content as yours. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alternative fonts glyph support
Joram and Urs, I appreciate your feedback and comments. I think you both have an clear enough understanding of what the situation is. I only recently considered doing this, but as I've pondered it more and more I've come to realize that isn't really any harder to provide full glyph support in each font than to not. So, I'll probably just continue to support them. That's just the easiest thing to do, I think. -Abraham On Fri, Jan 2, 2015 at 3:43 PM, Noeck [via Lilypond] wrote: > > > Am 02.01.2015 um 20:35 schrieb tisimst: > > tisimst wrote > >> That being said, if no one complains too loudly, I think I may > remove > >> support for them. What think ye all? > > > > No complaints? That's not a problem. I guess I'll think about it a > little > > more before proceeding... > > Dear Abraham, > > I didn’t want to complain before I understand your point correctly. > To > understand it, I wanted to test your fonts how they behave when using > such symbols. As I had no time up to now, I just ask my questions, > even > if I could have found out myself. > > Could you please clarify, if I understood you correctly? > > 1. The current situation is: > a) If I use a font which has no gregorian chant glyphs, the > corresponding Emmentaler glyphs are in that font and they are used. > Is > that right? > > b) If it comprises those glyphs, they are used (Profondo), right? > > 2. You want: > a) Writing greg. chant with such a font that does not support it, is > not > possible anymore. I could however switch to another font for just > this > context or even a single symbol if I want that (e.g. engrave a > VaticanaStaff using Emmentaler and a Staff in the same score using > Haydn > or I could put a Profondo special symbol in a score that uses > Beethoven > which does not support this symbol.) > > b) More exotic glyphs that are present in a font are still available > (e.g. greg. chant is still possible with Profondo)? > > If that is the case, I would prefer complete fonts that can do > anything > LilyPond can do. But I could also live with that change, given that I > can work around this by using different fonts in the same score. > > Is it possible to implement some kind of cascade in LilyPond: That it > uses the chosen font (e.g. Haydn) and if a symbol is not available it > has a fallback to Emmentaler which contains all symbols. That way the > font would not need to provide the fallback but LP itself. > > Cheers, > Joram > > ___ > lilypond-user mailing list > [hidden email] > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > If you reply to this email, your message will be added to the > discussion below: > http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170049.html > To start a new topic under User, email > ml-node+s1069038n...@n5.nabble.com > To unsubscribe from Lilypond, click here. > NAML -- View this message in context: http://lilypond.1069038.n5.nabble.com/Alternative-fonts-glyph-support-tp169988p170053.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: Improbable offset for stencil: nan staff space
Am 03.01.2015 um 00:06 schrieb Karim Haddad: Hi First of all: Happy new year to all of you. Does someone knows the meaning of this programming error ?: programming error: Improbable offset for stencil: nan staff space Setting to zero. continuing, cross fingers Searched on the net but couldn't find a reasonable answer. Happy new year, Karim! In this case, a minimal example of your music that triggers the error is *very* helpful to answer your question, otherwise we'll just poke around in the dark ... Marc Best K ___ 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
