Re: multiple volta spanners...
On 2012-08-26 23:17, Marc Hohl wrote: In nearly every case, it is wise to insert bar checks |, then one finds very quickly that A very good advice! I added the bar checks and withing 10 seconds I discovered the problem! Thank you very much! // Anders -- English isn't my first language. So any error or strangeness is due to the translation. Please correct my English so that I may become better. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Il 24/08/2012 22:12, Davide Liessi ha scritto: The main meaning of "estensore" is "something that extends something else" (also in anatomy) which seems better, but still isn't perfect: a spanner _does not_ extend something over notes, it is _itself_ extended; however it could be acceptable, since one could think of the spanner as a tool extending _a mark_ over notes. I can see the difference but I think that the second interpretation works anyway. So in the end I am left with "indicazione estesa" (Gianluca D'Orazio, "extended mark/indication") and "oggetto esteso" (Francisco Vila, "objeto de extensión", "extended object"), that both have the right meaning in our context. The former is more precise, but the latter sounds better to my ear. I'd really like to have one word, because the word spanner is often used along with the actual object which spans and a three (or more) word expression would be quite "heavy". Also I'd like to use a word which gives the idea of an action, as in english: spanner -> something which spans So I would use "estensore" or keep it untranslated. What do you prefer? Thanks for the feedback! -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Il 25/08/2012 23:23, Davide Liessi ha scritto: What you observed is part of the reasons because I think that "indicazione estesa" or "oggetto esteso" would be the best choices: despite the fact that these are two-word terms, they convey the exact concept we need to describe, so if one tries to guess what they are, chances are he gets the right meaning, in my opinion. Furthermore, I think that they look technical enough to suggest to read the manual. I'm not convinced :) Think about "slur spanner": "Indicazione estesa della legatura di portamento". It's too long and also not straightforward. And I believe that "estensore" looks more technical because it is not related at all with music notation, while someone may be lead to think that "indicazione estesa" is a notation concept instead of a lilypond concept. So in the end I am convinced that they satisfy all the "requirements" (accurate meaning, easy to guess, technical appearance) with the only disadvantage of being two-word expressions. I changed my mind also about the order of preference: I would choose "indicazione estesa" and keep "oggetto esteso" as a substitution. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to update the makerhythm-snippet
- Original Message - From: "Gilles" To: ; "David Kastrup" Sent: Sunday, August 26, 2012 11:35 PM Subject: Re: how to update the makerhythm-snippet it really serves no purpose to use it [event-chord-wrap!] in snippets So i propose to delete this snippet 390 because it is no more useful. Gilles I think only an LSR editor (like me) can do this. You want me to go ahead and delete it? -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accompaniment of accordion (accords)
Jens Liebenau writes: > Dear LilyPond user(s), > > How can I realise an accompaniment of accordions (accords) in > LilyPond? > > I want to do it like the music publisher did in the attached sheet of > music: with lower-case and capitalised letters for the different > accords. Because I am not very well versed in accordions, could > someone explain this notation to me? > Or is that notation more unusual? > > Thank you very much in advance! Please don't post copyrighted material to the list, except in excerpts required for discussing the technical questions, for which one or two bars should be more than enough. We certainly don't want cover pages and advertisements, and no copyrighted performable material. Apart from taking bandwidth, it is legally problematic. At the current point of time, LilyPond does not have much support for accordion built-in. Basically, you would use chords, and write just the chord and bass names as markups in text sub- and superscripts. That is not all that satisfactory, since it does not adapts itself to transposition, but that is also the case for the notes themselves (transposing accordion chords usually implies the bass note and the chord notes staying in the same octave). -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
2012/8/27 Federico Bruni: > Il 24/08/2012 22:12, Davide Liessi ha scritto: > >> The main meaning of "estensore" is "something that extends something >> else" (also in anatomy) which seems better, but still isn't perfect: a >> spanner _does not_ extend something over notes, it is _itself_ >> extended; however it could be acceptable, since one could think of the >> spanner as a tool extending _a mark_ over notes. > > I can see the difference but I think that the second interpretation works > anyway. That's the reason because I originally kept "estensore" as a possible (although not preferred) translation. Actually I am quite ambivalent towards "estensore". Reading again my previous message I noticed I was categorically excluding also "estensore" along with the other single-word terms, which I don't think I meant; my objection was mainly about "tensore" and the main meaning of "estensore", but I still thought that the second interpretation of "estensore" could be valid. > I'd really like to have one word, because the word spanner is often used > along with the actual object which spans and a three (or more) word > expression would be quite "heavy". > Think about "slur spanner": "Indicazione estesa della legatura di > portamento". It's too long and also not straightforward. You're right: expressions like that would be really "heavy" and rather unclear. > Also I'd like to use a word which gives the idea of an action, as in > english: spanner -> something which spans > And I believe that "estensore" looks more technical because it is not > related at all with music notation, while someone may be lead to think that > "indicazione estesa" is a notation concept instead of a lilypond concept. These also are good points. > So I would use "estensore" or keep it untranslated. > What do you prefer? Given what we all said, both "indicazione estesa" and "oggetto esteso" are unsuitable, so I agree that these are the options. In the end I prefer "estensore": I think the advantage of having a translation is worth the risk that the translation could be slightly misleading (given the fact that the term would be explained in detail in the manuals). > Thanks for the feedback! I've been using Lilypond for a couple of years and I think it really is an amazing software. I think that having a good translation of the manual is the best way to help spreading the use of Lilypond, so I am happy this whole discussion was useful. As a side note, unfortunately in this period I don't have much spare time, but in the future I really would like to actively help with the translation. Best wishes, Davide P.S. By the way, I just recalled another meaning of "estensore", in a legal context: "estensore di un documento, di un atto, di una sentenza", which means the person who actually writes an official document, a certificate, the judgements of a court. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Il 27/08/2012 11:55, Davide Liessi ha scritto: > So I would use "estensore" or keep it untranslated. > What do you prefer? Given what we all said, both "indicazione estesa" and "oggetto esteso" are unsuitable, so I agree that these are the options. In the end I prefer "estensore": I think the advantage of having a translation is worth the risk that the translation could be slightly misleading (given the fact that the term would be explained in detail in the manuals). Agreed. > Thanks for the feedback! I've been using Lilypond for a couple of years and I think it really is an amazing software. I think that having a good translation of the manual is the best way to help spreading the use of Lilypond, so I am happy this whole discussion was useful. As a side note, unfortunately in this period I don't have much spare time, but in the future I really would like to actively help with the translation. Great, just write me an email when you have time to help. I already have a precious proofreading help from Luca (who reads this mailing list but didn't join this discussion.. maybe it's in vacation), but of course more help is welcomed. The maintenance of translated files has recently made easier and I hope I'll speed up the translation of Notation Reference in the coming months. Ciao -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to update the makerhythm-snippet
Dear Gilles, thanks, it worke now. You are right, it's not longer necessery, but I have some older files wich use this script. I will try to update them and use changepitch instead. > Dear community, > > I wanted to update this snippet: > > http://lsr.dsi.unimi.it/LSR/Snippet?id=390 > > But without sucess. Any ideas how this can be done? > > The snipped 390 has to be considered as deprecated because the snippet > http://lsr.dsi.unimi.it/LSR/Item?id=654 > does the same thing but is more powerful (it accepts for example > articulations). > So I would not mind to delete it, but if people do want to use it, we can, > as > usual now, use the Scheme function event-chord-wrap! > (see http://lilypond.org/doc/v2.16/Documentation/changes/index.html ). > > So the line 76 (in the end of the makeRhythm function) : >m))) > would become : >(event-chord-wrap! m > > Gilles > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
problem with addTenuto
Dear community, I've used quite frequently the addTenuto function, which You can find at http://lsr.dsi.unimi.it/LSR/Snippet?id=696. Although lilypond doesn't complain about errors, it doesn't work as expected. I also would like to update it. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
problem with "acciaccatura"
how can i decide if the acciaccatura note is link to the higher or the lower note of chord that follow? when i write acciaccatura to a chord, in default mode, it link to the lower note ps: i wish you can understand, i'm not good with english. if there's someone italian i will be happy to speak italian \acciaccatura d'8 .. thanx! fabio ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
On Thu, Aug 23, 2012 at 2:05 PM, Federico Bruni wrote: > Dear italian users, > > do you have any good idea about how to translate "spanner"? > I had this doubt in the past, see end of this page: > http://lists.linux.it/pipermail/tp/2011-February/021547.html stepping back for a bit: why do you want to translate this at all? It is a lilypond specific term, so whatever word you pick , you have to explain it to the user anyway. You might as well leave it in its original state and stop agonizing over it. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with "acciaccatura"
Il 27/08/2012 14:48, fabio gabbianelli ha scritto:
how can i decide if the acciaccatura note is link to the higher or
the lower note of chord that follow? when i write acciaccatura to a
chord, in default mode, it link to the lower note
ps: i wish you can understand, i'm not good with english. if there's
someone italian i will be happy to speak italian
\acciaccatura d'8..
You can temporarily change the slur direction this way:
\relative c' {
\slurUp
\acciaccatura d'8
\slurDown
}
You can read more here:
http://lilypond.org/doc/v2.16/Documentation/notation/direction-and-placement
Ciao
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Han-Wen Nienhuys writes: > On Thu, Aug 23, 2012 at 2:05 PM, Federico Bruni wrote: >> Dear italian users, >> >> do you have any good idea about how to translate "spanner"? >> I had this doubt in the past, see end of this page: >> http://lists.linux.it/pipermail/tp/2011-February/021547.html > > stepping back for a bit: why do you want to translate this at all? It > is a lilypond specific term, so whatever word you pick , you have to > explain it to the user anyway. You might as well leave it in its > original state and stop agonizing over it. While this is not likely relevant to the topic of Italian, in German, "ein Spanner" is a Peeping Tom. That could be motivation to choose a less suggestive term in longer treatises. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Il 27/08/2012 15:06, Han-Wen Nienhuys ha scritto: On Thu, Aug 23, 2012 at 2:05 PM, Federico Bruni wrote: Dear italian users, do you have any good idea about how to translate "spanner"? I had this doubt in the past, see end of this page: http://lists.linux.it/pipermail/tp/2011-February/021547.html stepping back for a bit: why do you want to translate this at all? It is a lilypond specific term, so whatever word you pick , you have to explain it to the user anyway. You might as well leave it in its original state and stop agonizing over it. I'm about to send the updated po file to the translationproject robot. I've not translated yet the documentation parts where spanners are explained. So if an italian user sees an output message about "estensore", he won't understand what it is. So I'll leave it untranslated until I've translated the relevant parts of NR and the term has entered in the italian user's vocabulary. In general, a translator should try to translate as much as possible. At least this is what I've learned from other italian translators. I think it's also a kind of cultural matter: in North Europe you are more used to english words and language, while in Italy, France and Spain it's different (for example, we overdub any foreign movie). -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with "acciaccatura"
Hello fabio,
you can use an override:
\relative c' {
\once \override Slur #'direction = #UP
\acciaccatura d'8
}
That leaves any slurUp/slurDown/slurNeutral intact and changes direction
only for this particular slur.
HTH
Jan-Peter
On 27.08.2012 14:48, fabio gabbianelli wrote:
how can i decide if the acciaccatura note is link to the higher or the lower
note of chord that follow? when i write acciaccatura to a chord, in default
mode, it link to the lower note
ps: i wish you can understand, i'm not good with english. if there's someone
italian i will be happy to speak italian
\acciaccatura d'8 ..
thanx!
fabio
___
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: problem with "acciaccatura"
Il 27/08/2012 15:45, Jan-Peter Voigt ha scritto:
\relative c' {
\once \override Slur #'direction = #UP
\acciaccatura d'8
}
That leaves any slurUp/slurDown/slurNeutral intact and changes direction
only for this particular slur.
More elegant solution :)
Fabio, it is explained here:
http://lilypond.org/doc/v2.16/Documentation/learning/within_002dstaff-objects.it.html
It's the last chapter of Learning Manual I still have to translate and
I'll do it in the coming days.
--
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
Federico Bruni writes: > In general, a translator should try to translate as much as > possible. At least this is what I've learned from other italian > translators. > I think it's also a kind of cultural matter: in North Europe you are > more used to english words and language, while in Italy, France and > Spain it's different (for example, we overdub any foreign movie). A friend of mine once came across a PostScript tutorial which suffered significantly in usability by the translators not just translating all variable names in the examples, but also the standard operators. The point is that if "spanner" is mostly used to relate to things written in the LilyPond code base and corpus, translating it is not going to help. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [for Italian users] how to translate "spanner"?
2012/8/27 David Kastrup : > Federico Bruni writes: > >> In general, a translator should try to translate as much as >> possible. At least this is what I've learned from other italian >> translators. >> I think it's also a kind of cultural matter: in North Europe you are >> more used to english words and language, while in Italy, France and >> Spain it's different (for example, we overdub any foreign movie). > > A friend of mine once came across a PostScript tutorial which suffered > significantly in usability by the translators not just translating all > variable names in the examples, but also the standard operators. We are good translators. We don't do that. > The point is that if "spanner" is mostly used to relate to things > written in the LilyPond code base and corpus, translating it is not > going to help. 99 percent or more of computer languages use English keywords, and a manual for them can be translated. LilyPond has keywords, but spanner is not one, it's technical, it's specific, but it's not a keyword or operator. One could leave it untranslated for clarity or brevity only. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Complete Ossia stave colored ?
Hi, Is it possible to completly color an Ossia stave ? I can do most symbols like the note heads, the stem, accidentals, etc. all seperate, but then the underlying lines? Regards, Wim. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Complete Ossia stave colored ?
mail-136 wrote > > Hi, > > Is it possible to completly color an Ossia stave ? > > I can do most symbols like the note heads, the stem, accidentals, etc. all > seperate, but then the underlying lines? > > see http://lsr.dsi.unimi.it/LSR/Item?id=443 Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Complete-Ossia-stave-colored-tp131383p131385.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
Seeking an editorial advisor
I am engraving a work for piano, and would appreciate the advice of someone with an experienced eye for reviewing piano music for clarity and aesthetics. I don't mean Lilypond's aesthetics, which as we know are quite good, I mean things more like choice of enharmonic spellings, notation of rhythms using tied eighths versus syncopated quarter notes, possible tweaking of ties in odd note clusters or colliding voices, overlapping right- and left-hand voices on one staff versus separate, etc. This is not a for-profit venture, but rather a labor-of-love as a thank-you for a former teacher of many years ago. It also involves copyrighted material, so sending it to the list for a mass critique isn't suitable. The piece is short (under 100 measures of piano staff, presently five pages), not very technically difficult, and I pledge not to squander your time with too many questions. If you'd like to see some of my puzzlements before you assess whether you have time to help me with my questions, I'd be happy to reply off-list. Thank you for your time! Jim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypondfile
pabuhr writes:
> I cannot get the direct output from lilypond to match the output from
> lilypondfile with lilypond book. Below I have the source file and a PDF file
> where page 1 is the direct output from lilypond and page 2 is generated by
> lilypond book using:
>
> \lilypondfile{Mary_Lamb.ly}
>
> The problem is the vertical spacing is compressed in lilypond book.
> I'd like the output in lilypond book to look the same as the direct
> output.
The vertical spacing between systems in lilypond-book is established by
LaTeX, not LilyPond, so most spacing parameters will not be effective.
Intersystem spacing in lilypond-book is documented in the usage manual,
though possibly not really obvious:
Each snippet will call the following macros if they have been
defined by the user:
* `\preLilyPondExample' called before the music,
* `\postLilyPondExample' called after the music,
* `\betweenLilyPondSystem[1]' is called between systems if
`lilypond-book' has split the snippet into several PostScript
files. It must be defined as taking one parameter and will be
passed the number of files already included in this snippet. The
default is to simply insert a `\linebreak'.
So you need to define betweenLilyPondSystem to insert space, something
like
\newcommand\betweenLilyPondSystem[1]{\linebreak\vspace{5mm}}
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypondfile
The vertical spacing between systems in lilypond-book is established by LaTeX, not LilyPond, so most spacing parameters will not be effective. Ouch! 8-( Having to fuss with vertical spacing in two places is unfortunate, especially since the latex version only gives a fixed spacing whereas lilypond allows control at multiple levels. I don't think knowing the "number of files already included in this snippet" is going to be helpful. Maybe I need to directly include PS/PDF output from lilypond if I want them to be the same. 8-( Intersystem spacing in lilypond-book is documented in the usage manual, though possibly not really obvious: Yes, I saw those macros but never imagined I would need them unless I have to tweak after the fact. Ok, I'll have to go back and rethink this one. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.16.0 released!
Please send such questions to lilypond-user; hopefully somebody can help you with this and if you have a bug it can get to bug-lilypond. - Graham On Mon, Aug 27, 2012 at 10:18:40AM -0500, Fredric Dannen wrote: > > Graham, > > I'm having a problem with 2.16 that may have a simple solution, and perhaps > you > can advise me. All of my self-produced scores are in 2.14. But even when I use > the convert-ly -e *.ly function, 2.16 will not open any of them. Based on the > log files, it appears to be a case of outmoded syntax, for which 2.14 was > tolerant, but 2.16 is not. I can't figure it out. Is this a known issue, and > is > there a solution? > > Many thanks, > Fred ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.16.0 released!
Thanks, Graham!
I figured out what my problem was - the syntax in odd and even headers. I like
my page numbers in the usual spot -- even left, odd right -- and the headers
centered on all pages starting from page 2.
In 2.14, I was using this syntax:
oddHeaderMarkup = \markup \fill-line {
" "
\on-the-fly #not-first-page \fromproperty #'header:title
\on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
\fromproperty #'page:page-number-string
}
evenHeaderMarkup = \markup \fill-line {
\on-the-fly #print-page-number-check-first \fromproperty
#'page:page-number-string
\on-the-fly #not-first-page \fromproperty #'header:composer
" "
}
But 2.16 will not accept this syntax, nor create a PDF. And the convert-ly -e
*.ly function won't fix the problem, or even identify it.
But this works:
oddHeaderMarkup = \markup \fill-line {
" "
\on-the-fly #not-first-page \fromproperty #'header:title
\on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
\fromproperty #'page:page-number-string }
evenHeaderMarkup = \markup \fill-line {
\on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
\fromproperty #'page:page-number-string
\on-the-fly #not-first-page { \center-align \fromproperty #'header:composer
} " " }
}
Fred___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with "acciaccatura"
On 27/08/12 23:45, Jan-Peter Voigt wrote:
Hello fabio,
you can use an override:
\relative c' {
\once \override Slur #'direction = #UP
\acciaccatura d'8
}
That leaves any slurUp/slurDown/slurNeutral intact and changes
direction only for this particular slur.
Having to do this happens frequently enough that I define
onceSlurDown = \once \override Slur #'direction = #DOWN
onceSlurUp = \once \override Slur #'direction = #UP
and use those abbreviations in scores, and for situations where for some
reason I can't or don't want to change the slur direction, \shape can be
used:
\version "2.16.0"
\relative c'' {
\shape Slur #'((0.2 . 0.8)(0 . 1.3)(0 . 1.7)(0 . 1.9))
\appoggiatura d8 4
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.16.0 released!
Fredric Dannen wrote
>
>
> In 2.14, I was using this syntax:
>
> oddHeaderMarkup = \markup \fill-line {
> " "
> \on-the-fly #not-first-page \fromproperty #'header:title
> \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> \fromproperty #'page:page-number-string
> }
> evenHeaderMarkup = \markup \fill-line {
> \on-the-fly #print-page-number-check-first \fromproperty
> #'page:page-number-string
> \on-the-fly #not-first-page \fromproperty #'header:composer
> " "
> }
>
> But 2.16 will not accept this syntax, nor create a PDF. And the convert-ly
> -e *.ly function won't fix the problem, or even identify it.
>
> But this works:
>
> oddHeaderMarkup = \markup \fill-line {
> " "
> \on-the-fly #not-first-page \fromproperty #'header:title
> \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> \fromproperty #'page:page-number-string }
>
> evenHeaderMarkup = \markup \fill-line {
> \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> \fromproperty #'page:page-number-string
> \on-the-fly #not-first-page { \center-align \fromproperty
> #'header:composer } " " }
> }
>
it's always good to send a (potentially) compiling code or the full code to
reproduce the error
when I complete the missing parts I see no error
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Lilypond-2-16-0-released-tp131313p131431.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: Lilypond 2.16.0 released!
Thanks..!
On Tue, Aug 28, 2012 at 12:36 AM, eluze wrote:
>
> Fredric Dannen wrote
> >
> >
> > In 2.14, I was using this syntax:
> >
> > oddHeaderMarkup = \markup \fill-line {
> > " "
> > \on-the-fly #not-first-page \fromproperty #'header:title
> > \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> > \fromproperty #'page:page-number-string
> > }
> > evenHeaderMarkup = \markup \fill-line {
> > \on-the-fly #print-page-number-check-first \fromproperty
> > #'page:page-number-string
> > \on-the-fly #not-first-page \fromproperty #'header:composer
> > " "
> > }
> >
> > But 2.16 will not accept this syntax, nor create a PDF. And the
> convert-ly
> > -e *.ly function won't fix the problem, or even identify it.
> >
> > But this works:
> >
> > oddHeaderMarkup = \markup \fill-line {
> > " "
> > \on-the-fly #not-first-page \fromproperty #'header:title
> > \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> > \fromproperty #'page:page-number-string }
> >
> > evenHeaderMarkup = \markup \fill-line {
> > \on-the-fly #not-first-page \on-the-fly #print-page-number-check-first
> > \fromproperty #'page:page-number-string
> > \on-the-fly #not-first-page { \center-align \fromproperty
> > #'header:composer } " " }
> > }
> >
>
> it's always good to send a (potentially) compiling code or the full code
> to
> reproduce the error
>
> when I complete the missing parts I see no error
>
> Eluze
>
>
>
> --
> View this message in context:
> http://lilypond.1069038.n5.nabble.com/Re-Lilypond-2-16-0-released-tp131313p131431.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
>
--
*Nesmotren govori kao da mačem probada, a jezik je mudrih iscjeljenje.
Izreke 12:18*
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypondfile
Is there a way to generate an eps file directly as for a ps file? I need the bounding box to include the exact output into latex (I'm not using pdflatex). I tried manually converting the ps to eps: ps2pdf generates a file that is unusable (go figure), and "convert" generates a low quality image (maybe one of the many parameters can fix this). Using command-line option "backend=eps" does generate a eps file but it's not the same as the original because it is for lilypond-book (and it generates a lot of extra files). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypondfile
On 2012-08-28 02:12, pabuhr wrote: Is there a way to generate an eps file directly as for a ps file? I need the bounding box to include the exact output into latex (I'm not using pdflatex). I tried manually converting the ps to eps: ps2pdf generates a file that is unusable (go figure), and "convert" generates a low quality image (maybe one of the many parameters can fix this). Using command-line option "backend=eps" does generate a eps file but it's not the same as the original because it is for lilypond-book I see no reason why there should be a difference. the eps backend is used by lilypond-book, but it should be usable on its own, too. lilypond -dbackend=eps file.ly should generate the exact same layout as the pdf file (except that the output is cropped). In fact, lilypond first does the whole layout and only then generates the output file (ps/pdf, eps, png, svg, ...) from the final layout. (and it generates a lot of extra files). lilypond -dhelp shows that there is an aux-files=#f option to lilypond: lilypond -dbackend=eps -daux-files=#f file.ly should be what you are after... Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://www.kainhofer.com * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * Edition Kainhofer, Music Publisher, http://www.edition-kainhofer.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Question about Lilypond
On 12-08-26 05:50 AM, stefano cucuzzella wrote: Hello, I had a question about Lilypond, it seems like this kind of command # (override-auto-beam-setting '(end * * * *) 1 4)doesn´t work anymore, and the program reads it as mistake. Is there something new in the new version that does the same job? Many thanks, Stefano Without pretending to have much grasp of tweaks and overrides, Stefano, I'm forwarding this to the user list, and perhaps http://lilypond.org/doc/v2.16/Documentation/notation/the-override-command might help. You don't say which version of lilypond you are using, and there has been a lot of new work done on commands such as the one in your question. Certainly, if you are still on 2.12, it would be well worth the effort to update to 2.16 which is the newest stable release. If you do update your lilypond, be sure to run convert-ly on your existing scores! Frescobaldi, which is my lilypond editor of choice both on Windows and Linux, has convert-ly built in, so the process is very simple. Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypondfile
> Is there a way to generate an eps file directly as for a ps file? I need the > bounding box to include the exact output into latex (I'm not using pdflatex). > I tried manually converting the ps to eps: ps2pdf generates a file that is > unusable (go figure), and "convert" generates a low quality image (maybe one of > the many parameters can fix this). Using command-line option "backend=eps" does > generate a eps file but it's not the same as the original because it is for > lilypond-book I see no reason why there should be a difference. There is a small shift left and up that is different from lilypondfile, which is what I was previously using. I can compensate in latex. lilypond -dbackend=eps -daux-files=#f file.ly should be what you are after... Perfect, except it still generates a PDF file, which I don't need and I could not find an command-line option to prevent the PDF from being created. But that's what a Makefile is for: I just delete the PDF. Thanks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
header font size
As I crank up the global-staff-size, the heading text gets LARGE. I'd like to uniformly reduce the size of the heading text like this: \override Score.HeaderText #'font-size = #-1 but "HeaderText" is not the magic word. Is there a magic word? I did look and could not find it. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Question about Lilypond
On 12-08-26 05:50 AM, stefano cucuzzella wrote: Hello, I had a question about Lilypond, it seems like this kind of command # (override-auto-beam-setting '(end * * * *) 1 4)doesn´t work anymore, and the program reads it as mistake. Is there something new in the new version that does the same job? Have you read this page? http://lilypond.org/doc/v2.16/Documentation/notation/beams#setting-automatic-beam-behavior If you have a problem, please send a minimal example¹ of what you want to achieve. 1. http://lilypond.org/website/tiny-examples.it.html -- Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
