Re: German translation Part 2 3
Till Rettig [EMAIL PROTECTED] writes: Ok, now I found that the README file in the GIT online is much better than the one I got via git pull onto my computer (or is this just that I didn't update last day?) Anyways, now this patch things seemed to work for me, here are the changes I applied yesterday, they should contain all files from cathegory 2 and 3. (I am not sure though if I got everything right with the commitish number on top of the files). Thanks, this is great. Can you pull from GIT, add an entry for the news page, similar to the Spanish one, and send it in a new patch? Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme Problem
Am 31. Dezember 2006, 15:23 Uhr (+1100) schrieb Brett Duncan:
But when I put
\compFor #16
into my .ly file, the following error occurs:
syntax error, unexpected NUMBER_IDENTIFIER, expecting DIGIT or UNSIGNED
\repeat unfold
\lilyvartmpb { r4 }
Can someone point out to me where I'm going wrong?
I don't know the exact reason but somehow the expansion into a scheme
construct doesn't work for variables in the \repeat unfold construct
(the parser expects a number but obviously doesn't resolve the $beats
before seeing it).
You can get it done this way: Look at the expansion of your function
with \displayMusic after replacing the variable with a real number (to
avoid the error) and then use the output of lilypond for defining your
music-function:
compFor = #(define-music-function (parser location beats) (number?)
#{
\override Rest #'stencil =
#ly:percent-repeat-item-interface::beat-slash
\override Rest #'thickness = #'0.48
\override Rest #'slope = #'1.7
\repeat unfold 16 { r4 }
\revert Rest #'stencil
#})
\displayMusic
\compFor #16
---
In the output of lilypond, you replace the 16 with the variable name
beats and copy that into the definition of your music function. It's
not really convenient and there's probably another way to get it done,
but at least it works.
---
The result is like this (and that works as expected):
\version 2.11.2
compFor = #(define-music-function (parser location beats) (number?)
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'context-type
'Bottom
'element
(make-music
'OverrideProperty
'pop-first
#t
'grob-property-path
(list (quote stencil))
'grob-value
ly:percent-repeat-item-interface::beat-slash
'symbol
'Rest))
(make-music
'ContextSpeccedMusic
'context-type
'Bottom
'element
(make-music
'OverrideProperty
'pop-first
#t
'grob-property-path
(list (quote thickness))
'grob-value
0.48
'symbol
'Rest))
(make-music
'ContextSpeccedMusic
'context-type
'Bottom
'element
(make-music
'OverrideProperty
'pop-first
#t
'grob-property-path
(list (quote slope))
'grob-value
1.7
'symbol
'Rest))
(make-music
'UnfoldedRepeatedMusic
'elements
'()
'repeat-count
beats
'element
(make-music
'SequentialMusic
'elements
(list (make-music
'EventChord
'elements
(list (make-music
'RestEvent
'duration
(ly:make-duration 2 0 1 1)))
(make-music
'ContextSpeccedMusic
'context-type
'Bottom
'element
(make-music
'RevertProperty
'grob-property-path
(list (quote stencil))
'symbol
'Rest)
\compFor #16
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: transpose just the midi
you'll want to use the \transposition command
On 12/30/06, Neuro [EMAIL PROTECTED] wrote:
Excuse me, one small questions.
How can I transpose just the midi output?
for example, French horn is in F; we want it sounds fifth lower than
written.
Here are the examples,
0 %% file horn.ly
1 horn = {
2 \set Staff.instrumentName = \markup { \column { Horn \line { in
F } } }
3 \set Staff.midiInstrument = french horn
4 \clef treble
5 \key c \major
6 \time 4/4
7 c' 1 \ppp
8 \bar |.
9 }
00 %% file music.ly
01 \version 2.10.5
02 \include horn.ly
03 \header { }
04 \score {
05 \horn
06 \layout { }
07 \midi{
08 \context {
09 \Voice
10 \remove Dynamic_performer
11 \remove Span_dynamic_performer
12 }
13 }
14 }
# so we can run
# lilypond music.ly
Now, the printed music is good, but the midi is not in tune.
It's in concert pitch C, but I want it written pitch C as in F horn,
that
is concert pitch F.
... sure we can transpose the horn (for example to the fwllowing file),
make
a whoe set of scores, re-run the lilypond for the midi.
0 %% file horn.ly
1 horn = \transpose f c {
2 \set Staff.instrumentName = \markup { \column { Horn \line { in
F } } }
3 \set Staff.midiInstrument = french horn
4 \clef treble
5 \key c \major
6 \time 4/4
7 c' 1 \ppp
8 \bar |.
9 }
00 %% file music_for_horn_in_F_midi.ly
01 \version 2.10.5
02 \include horn_for_midi.ly
03 \header {}
04 \score {
05 \horn
06 \layout { }
07 \midi{
08 \context {
09 \Voice
10 \remove Dynamic_performer
11 \remove Span_dynamic_performer
12 }
13 }
14 }
# so we can run
# lilypond music_for_horn_in_F_midi.ly
But, is there a simler way? perhaps like ...
\midi {
\transpose f c \horn
}
%% or
\midi {
\context {
\transpose f c \horn
}
}
%% or
\midi {
\context {
\voice {
\transpose f c \horn
}
}
}
Thank you very much.
and
Nappy New Year
Neuro
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme Problem
http://code.google.com/p/lilypond/issues/detail?id=208can=1q=fixed_2_10_7 Brett Duncan escreveu: The following function is an attempt on my part to learn how to create such functions, based on what appears in the User Manual. The function itself is not really important, just a problem I set for myself. It's supposed to take a number as its argument and produce the equivalent number of slashes, the idea being to use the slash as a comping symbol, and substituting the slash for the normal appearance of a quarter rest. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Time signature in French baroque music
Quoting Manuel [EMAIL PROTECTED]:
Franek,
I recently and finally managed to solve the problem for an
Allemaigne, changig the time signature of the Recoupe from 3/4 to a
single 3. I include the file here, you can see the special command:
\override Staff.TimeSignature #'style = #'single-digit
\time 3/4
which I had to put in both parts separately. I don't know exactly
what you are trying to do, but maybe it will help.
If you only want to do it once, you can do
\override Score.TimeSignature #'style = #'single-digit
so the setting applies to the full score instead of only the
current Staff context. Even better is probably to redefine the default
definition of Staff context:
\score{
... % The actual music comes here
\layout{
\context {
\Staff
\override TimeSignature #'style = #'single-digit
}
}
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme Problem
Hi Brett,
Just a thought - the normal syntax for \repeat is
\repeat unfold 9 { music statements }
in your declaration you've put the keyword in quotes. Does it help if you
remove them? E.g.
compFor = #(define-music-function (parser location beats) (number?)
#{
\override Rest #'stencil =
#ly:percent-repeat-item-interface::beat-slash
\override Rest #'thickness = #'0.48
\override Rest #'slope = #'1.7
\repeat unfold $beats { r4 }
\revert Rest #'stencil
#})
I don't know any of the Lilypond or Scheme internals but there's a chance
that this could be confusing a parser or lexical analyzer somewhere along
the line. Software diagnostic messages are sometimes just an opener for
negotiation...
Cheers,
Ian
Brett Duncan-2 wrote:
The following function is an attempt on my part to learn how to create
such functions, based on what appears in the User Manual. The function
itself is not really important, just a problem I set for myself. It's
supposed to take a number as its argument and produce the equivalent
number of slashes, the idea being to use the slash as a comping symbol,
and substituting the slash for the normal appearance of a quarter rest.
compFor = #(define-music-function (parser location beats) (number?)
#{
\override Rest #'stencil =
#ly:percent-repeat-item-interface::beat-slash
\override Rest #'thickness = #'0.48
\override Rest #'slope = #'1.7
\repeat unfold $beats { r4 }
\revert Rest #'stencil
#})
But when I put
\compFor #16
into my .ly file, the following error occurs:
syntax error, unexpected NUMBER_IDENTIFIER, expecting DIGIT or UNSIGNED
\repeat unfold
\lilyvartmpb { r4 }
Can someone point out to me where I'm going wrong?
Thanks,
Brett
--
Brett Duncan
[EMAIL PROTECTED]
Always do right - this will gratify some and astonish the rest.
Mark Twain
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
View this message in context:
http://www.nabble.com/Scheme-Problem-tf2900758.html#a8107195
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Transposable Fret Diagrams for Guitar
I'm proposing a method for getting transposable fret diagrams for the guitar. The method I propose is different from the current FretBoard functionality. The FretBoard context takes a set of notes and determines a fingering that will allow the playing of that set of notes. This is a very useful too, and I appreciate Rick for sponsoring it. I've asked Han-Wen about the cost for sponsoring a modification to FretBoards that will allow it also to take the name of a chord and determine a chord diagram. There would be a default set of chord diagrams (one for each chord name) that I would enter based on a standard chord reference for guitar. Then, the input to FretBoards would be a set of chord names (which Lilypond will change into a set of chords). If the sequence were transposed, the chords would be transposed. The diagrams would be looked up in a hash table and included in the score. Any chords not found in the hash table would be treated just as in the current FretBoards context -- a fingering would be determined by FretBoards. Of course, if users wished, they'd be able to define their own chord library (I assume the library will be defined in a .ly file), or replace entries in the existing chord library. And the current functions of FretBoard will still be available. The cost for sponsoring this feature is eur 150. I'm hoping to get a couple of people to help me sponsor this feature. Any takers? Thanks, Carl Sorensen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: German translation Part 2 3
Yes, I wrote a short message, but I don't now get the git to work out this patch, forgot how to update an already existing file, so I will send it this time directly. I just addes the message to the site/news.html file, hope that was right. Here ist the message also alone: /dd dtbttlilypond.org/tt auf deutsch/b - em31. Dezember 2006/em dd Die LilyPond-Webseiten sind jetzt auch auf deutsch uuml;bersetzt! /dd Hope this is sufficient. Thank you! Till PS: I got a lot of unresolved messages about all the files I sent in the patches: they got somehow saved with another name and the new version came from git with the original name. Is this about the commitish number or why could they not be merged? Jan Nieuwenhuizen wrote Thanks, this is great. Can you pull from GIT, add an entry for the news page, similar to the Spanish one, and send it in a new patch? Jan. lilypond.org auf deutsch - 31. Dezember 2006 Die LilyPond-Webseiten sind jetzt auch auf deutsch bersetzt! LilyPond 2.11.6 available - December 30, 2006 This release supports arbitrary fractional alterations, allowing music with different microtonal conventions to be typeset. (Bugfixes, Changes, Download) LilyPond 2.10.6 available - December 30, 2006 New! Improved! With even more bugfixes! (Bugfixes, Changes, Download) lilypond.org en español - December 29, 2006 ¡Ya está disponible la versión en español del sitio web de LilyPond! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
setting Midi tempo
Hi,
I am trying to set a Midi tempo of 90 dotted quarter notes per minute.
According to the Lilypond docs, the correct syntax is:
\midi { \tempo 4 . = 90 }
However, I keep getting a syntax error (unexpected tempo). Since it's a
dotted note, there is supposed to be a space after the 4. I have tried
all sorts of combinations here of leaving and eliminating the spaces,
but no luck.
Does anyone know how to resolve this?
Thanks.
--
Chris
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: setting Midi tempo
Christopher A. LaFond wrote:
I am trying to set a Midi tempo of 90 dotted quarter notes per minute.
According to the Lilypond docs, the correct syntax is:
\midi { \tempo 4 . = 90 }
However, I keep getting a syntax error (unexpected tempo). Since it's a
dotted note, there is supposed to be a space after the 4. I have tried
all sorts of combinations here of leaving and eliminating the spaces,
but no luck.
The syntax has changed; please see the same page in the latest 2.11 docs.
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Vertical alignment of lyrics to multiple voices
Happy new year!
I have been navigating the lilypond world for the past six months and have
been primarily exploring lilypond as a tool for creating leadsheets and
songbooks.
My main interest is figuring out how to create an efficient template
for creating a leadsheet (or fakebook style sheet) for all types of modern
guitar-vocal based songs.
I am wrestling with the formatting for lyrics. I am aiming for a modular
approach
to constructing lilypond input so that I can format sheets for a wide variety
of
song styles. The main problem I am having is the vertical alignment of lyrics
assigned to one or more voice contexts. I will start off with a small example
to exemplify the problem. In the following example, I am printing off the
melody
and lyrics to Frere Jacques. I creating separated voice contexts for each
section of the song, and am assigning lyrics to each section. The resulting
output properly assigns the correct lyric to the correct voice, but the
different lyrics are rendered on the same vertical line- each successive
lyric is placed lower than the one preceding it.
How do I change this so that each lyric snippet is vertically aligned? All my
keyword searcing through the archives and manual hasn't come up with
anything that seems to work (I've tried overriding the minimum-Y-extent and
Y-offset of the lyric context with no discernable change).
Any suggestions welcomed!
Thanks,
Jack
--
code snippet:
\version 2.8
\include english.ly
melodya = {
\clef treble
\key c \major
\time 4/4
c'4 d'4 e'4 c'4 | c'4 d'4 e'4 c'4 |
}
melodyb = {
e'4 f'4 g'2 | e'4 f'4 g'2 |
}
melodyc = {
g'8 a'8 g'8 f'8 e'4 c'4 | g'8 a'8 g'8 f'8 e'4 c'4 |
}
melodyd ={ c'4 g4 c'2 | c'4 g4 c'2 \bar||}
melody = {\new Voice = a {\melodya} \new Voice = b {\melodyb} \new Voice =
c {\melodyc} \new Voice = d {\melodyd}}
texta = \lyricmode {
Fre -- re Jacqu -- es,
Fre -- re Jacqu -- es,
}
textb = \lyricmode {
Dor -- mez Vous?
Dor -- mez vous?
}
textc = \lyricmode {
Sonn -- ez les ma -- tin -- es,
Sonn -- ez les ma -- tin -- es,
}
textd = \lyricmode {
Din, din don!
Din, din don!
}
\score {
\new Voice = whole {\new Voice =a {\melodya} \new Voice=b {\melodyb}
\new Voice=c {\melodyc} \new Voice=d {\melodyd}}
\new Lyrics\lyricsto a \texta
\new Lyrics\lyricsto b \textb
\new Lyrics\lyricsto c \textc
\new Lyrics\lyricsto d \textd
\layout { }
}
---
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Transposable Fret Diagrams for Guitar
Carl D. Sorensen wrote: Rick H wrote: A user-maintained table of chord shapes wouldn't be transposable. It's using the Lilypond chord naming structure that makes the transposing work, IMO. This functionality wouldn't work for you, because you're an excellent guitar player. It would work for my purposes -- creating introductory guitar books of campfire songs to help novices have fun with the guitar. Thanks for your feedback, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user By a table lookup were you thinking of something like this? I think as long as the table knew what the root note is and what the slash note is (if present) then it could also transpose, (because thats the only two note letters it would ever encounter in a chord name). So to depict a common chord in the key of C like: Bm7b5 (the chord built on the 7th degree of the C major scale ) the table entry could separate the root name from the chord name in two dimensions: B,m7b5 For slash chords you can use a three dimension table entry so for Bm7b5/F: B,m7b5,F The fourth dimension could be a simple enumerator (to break duplicate name ties): B,m7b5,F,1 The fifth dimension would be the desired fretboard markup: B,m7b5,F,1,my notes go here So if you have to store 10 different forms of a Bm7b5 chord you have numerous ways to avoid duplicates names in the hash table and can support a robust library of names. B,m7b5,F,1,my notes go here B,m7b5,F,2,my notes go here B,m7b5,G,1,my notes go here B,m7b5,,1,my notes go here B,m7b5,,2,my notes go here etc... The transpose algorithm would always know to transpose dimensions 1 and 3 of the table entry as these are named notes. Typically you would probably only maintain all the names with C roots then use traspose to do the lookup, this way you only need to maintain 1/12 of the number of chord names in the library table. The my notes go here above would be interpreted by the current FretBoards and depicted as frets. Rick -- View this message in context: http://www.nabble.com/Transposable-Fret-Diagrams-for-Guitar-tf2901891.html#a8110445 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: A contribution to the Wiki
Is the lilypond extension available on this wiki site. I can't figure out how to display lilypond in the best way on this site. John Mandereau [EMAIL PROTECTED] writes: Good, please add such small contributions to the wiki without asking permission. If you plan to contribute regularly, you are encouraged to create a user account and introduce yourself. Only big changes or restructurations may need to be discussed first. Speaking of, the Resources links section becomes too big; sooner or later it should be splitted into several pages. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: setting Midi tempo
Graham Percival wrote: The syntax has changed; please see the same page in the latest 2.11 docs. - Graham Thanks for the update. However, it's still giving me a syntax error when I try to use a dotted note in the tempo. So while: tempoWholesPerMinute = #(ly:make-moment 90 4) works fine, the following does not: tempoWholesPerMinute = #(ly:make-moment 90 4.) Is this something that needs fixing, or is there something that I'm missing? -- ° Chris° ° ° Christopher A. LaFond [EMAIL PROTECTED] http://www.celticharper.net You guys got something against spam? (Vriess, in _Alien 4_) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
problem with \global and key signature
Hi, I am arranging a piece for 3 harps, and I am using the string quartet template in the docs as a model. When I use the \global setting, the score correctly includes the time signature in all staves, but does not set the key signature on the staves themselves, rather it uses accidentals throughout the piece to compensate. The template for string quartet is in c major, so you can't see this in the docs. But I used \key g \major, and it just inserted accidentals on all the f notes. I still need to set the key in each of the staves. -- ° Chris° ° ° Christopher A. LaFond [EMAIL PROTECTED] http://www.celticharper.net After things go from bad to worse, the cycle will repeat itself. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
utf-8 and lilypond 2.10.5
Dear list, Another question about utf-8. When I put a file with utf-8 (tradition Chinese) code (filename say utf-8.ly) for lilypond, it says: [user path/dir]$ lilypond utf-8.ly GNU LilyPond 2.10.5 Processing `utf-8.ly' Parsing... Interpreting music... [1] Preprocessing graphical objects... programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000543E, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10009EE8, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10006240, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10005B97, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10004E09, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10006C11, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10004E3B, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10007FA9, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers Layout output to `utf-8.ps'... Converting to `utf-8.pdf'... [EMAIL PROTECTED] ~/www/lilypond/test]$ lilypond utf-8.ly GNU LilyPond 2.10.5 Processing `utf-8.ly' Parsing... Interpreting music... [1] Preprocessing graphical objects... programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000543E, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10009EE8, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10006240, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10005B97, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10004E09, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10006C11, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10004E3B, file /usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10007FA9,
Page Break in Markup block
It's easy to break pages inside a Score block, but I need to break the page before a Markup block before the score. Paul ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: utf-8 and lilypond 2.10.5
programming error: FT_Get_Glyph_Name returns error
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming.
Skipping glyph U+1000543E, file
/usr/local/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf
Uuh, note the leading `1' in U+1000543E -- there is no such Unicode
glyph at all. There must be a bug somewhere. It works fine with
2.11.5, BTW.
btw, this particular utf-8.ly is like this, if you are interested,
( And this file is indeed coded in ut-8. )
The ugliest hymn which exists on earth :-)
However,...
chinese = \lyricmode { 三民主義 吾黨所宗 }
This is not correct. You have to insert spaces between the characters
(since you want a syllable per note).
Werner
PS: lilypond emits a strange warning for \key c \major:
Warning: No ordering for key signature alterations
This is not appropriate here...
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
