Re: Regarding the new Table of Contents in the GUB docs
I don't understand these references to "the Complete Table of Contents". As I see it, there are at least 5 separate "Tables of Contents", with no easy way to move from one to another: Learning Manual Notation Reference Internals Reference Application Usage Snippets List And once I'm in one of these 5 "documents", I have no link to take me to another document. I'm stuck and I'm forced to use the back button or the address bar, both of which are cumbersome. As a REAL LilyPond user, I use NR, IR, and AU, and I commonly need to move from one to the other, and the difficulty in doing so gets frustrating sometimes. I can't imagine how confusing this would be to a newbie. Reading the recent posts, it's as if NR exists in a vaccuum. It seems that any reference to the "documentation" is actually a reference to the NR. Am I missing something? Okay, of the 14 bullet-points on the Documentation Index, only two destinations have return-links: Developers Resources - "Go back to the Documentation index." Translations Status - "Up to documentation index." Why don't the other 12 bullet-points have this? I know I've mentioned this quite a bit recently, but is anybody working on this? Is it harder to implement than I'm led to believe? I don't want to sound annoying, but can someone PLEASE take care of this? Thanks, Mark Re: WANTED: Design for documentation (Photoshop power users!) http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00715.html Similar proposal from Robin Barrister: Re: WANTED: Design for documentation (Photoshop power users!) http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00770.html the docs need a link back to the main directory: http://lists.gnu.org/archive/html/lilypond-devel/2008-09/msg00374.html Reinhold's response: > Yes, that's a wish often heard, and I've noted it. That would be really easy > to implement (e.g. just hardcode a link to "../" at the top of the TOC. I > just never got around to implement it. ( from http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00781.html ) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
Reinhold Kainhofer wrote: Ahm, sorry if I sound destructive, but: How hard is it to click on "[Contents]", which is located in EVERY gray navigation bar on EVERY page Does anyone else feel like we're doomed to follow Reinhold having good ideas only weeks after he's already had them;) Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
On Mon, Sep 29, 2008 at 3:03 PM, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Montag, 29. September 2008 schrieb Mats Bengtsson: >> I haven't had the time to read all the discussions related to the new >> web layout of the 2.11 documentation, but wonder if I'm the only one >> who miss the possibility to view the full table of contents with all >> subsections expanded. > > Ahm, sorry if I sound destructive, but: How hard is it to click > on "[Contents]", which is located in EVERY gray navigation bar on EVERY page? > > It leads you to: > http://kainhofer.com/~lilypond/Documentation/user/lilypond/index_toc.html Awesome! Then I withdraw my suggestion. :-) Would it be possible to add a "Note" box to the top of the doc index pages? I think this would be incredibly helpful for everyone. Something like: **Note: For the complete Table of Contents, click the "Contents" link. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 29. September 2008 schrieb Valentin Villenave: > 2008/9/29 Mats Bengtsson <[EMAIL PROTECTED]>: > > I haven't had the time to read all the discussions related to the new > > web layout of the 2.11 documentation, but wonder if I'm the only one who > > miss the possibility to view the full table of contents with all > > subsections expanded. > > Hi Mats, > > I definitely agree with you! Wouldn't it be possible to have the > *complete* detailed TOC, at least at > http://kainhofer.com/~lilypond/Documentation/user/lilypond/ ? > > The tocframe div on the left is great the way it is, but we definitely > do need to have a detailed TOC on the first page. If you really all think that the start page already should contain the full TOC, although I'd rather not do that, we can easily change that in the .init file by simply setting $Texi2HTML::Config::INLINE_CONTENTS = 1; Then, however, there is no separate Contents page generated, but the TOC is inserted only where @contents appears in the texinfo file... All [Contents] links in the navigation bars will of course still work, but bring the user right to the TOC on the start page. Personally, however, I have always been annoyed by the excessively long title page, so I was quite happy that texi2html only put a short TOC on the start page and provided a separate page for the full, page-long TOC. BTW, I just realized that it is now much simpler to go to the full TOC than before, because the links are right there on every page, while with the 2.10 docs you first had to go up several times until you got to the start page of the manual... Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI4VgtTqjEwhXvPN0RAoKAAJ9HzD7fU06I2Wz6gz9eMvYqk6g2JgCeO6gR XQcJRHnKnZV0c/iK02EcFn8= =x2mW -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
Reinhold, you wrote Monday, September 29, 2008 11:03 PM Am Montag, 29. September 2008 schrieb Mats Bengtsson: I haven't had the time to read all the discussions related to the new web layout of the 2.11 documentation, but wonder if I'm the only one who miss the possibility to view the full table of contents with all subsections expanded. Ahm, sorry if I sound destructive, but: How hard is it to click on "[Contents]", which is located in EVERY gray navigation bar on EVERY page? It leads you to: http://kainhofer.com/~lilypond/Documentation/user/lilypond/index_toc.html That's perfect! I should know by now to press every button to see what it does :( Ah well, at least you enjoyed answering! Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
Quoting Reinhold Kainhofer <[EMAIL PROTECTED]>: Ahm, sorry if I sound destructive, but: How hard is it to click on "[Contents]", which is located in EVERY gray navigation bar on EVERY page? Sorry! It's the eyes that get blind first, right? /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 29. September 2008 schrieb Mats Bengtsson: > I haven't had the time to read all the discussions related to the new > web layout of the 2.11 documentation, but wonder if I'm the only one > who miss the possibility to view the full table of contents with all > subsections expanded. Ahm, sorry if I sound destructive, but: How hard is it to click on "[Contents]", which is located in EVERY gray navigation bar on EVERY page? It leads you to: http://kainhofer.com/~lilypond/Documentation/user/lilypond/index_toc.html > I'm very used to search for some word in the > table of contents, when I want to find the appropriate section in the > manual, but this is no longer possible if I want to find the title > of a level 3 section. For example, an email the other day mentioned > the subsection "Distances and measurements" and I actually had to run > grep in the Documentation source code to find out that it was located > in section 5.4.3. The only difference to before is that you now don't go to the start page, but to the Contents page. Same number of clicks, only the start page is less long ;-) > I certainly realize that it might take too much space to have this > fully expanded table of contents in the left margin all the time, but > it should at least be possible to select to view the full version > in the main window. I totally agree, that's why we have the "Contents" page ;-) Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFI4VCbTqjEwhXvPN0RAku9AJi7/yjKZXo2WWi3GFz7nApkQ2JcAKCWuMsc hcXlwugrPAl2RKwwvgU3SQ== =gDiV -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
Yes, I missed the full ToC too. Although if you had looked up "distances" in the index it would have directed you to "5.4.3 Distances and measurements". But this is a fortuitous example. In spite of the excellent work by Ralph to add @cindexes everywhere the section headings are not in general indexed. Maybe they should be. I wonder if they could be added automatically? If not, should we go through and add them manually? Trevor - Original Message - From: "Mats Bengtsson" <[EMAIL PROTECTED]> To: "Mailinglist lilypond-user" Sent: Monday, September 29, 2008 10:10 PM Subject: Regarding the new Table of Contents in the GUB docs Hi, I haven't had the time to read all the discussions related to the new web layout of the 2.11 documentation, but wonder if I'm the only one who miss the possibility to view the full table of contents with all subsections expanded. I'm very used to search for some word in the table of contents, when I want to find the appropriate section in the manual, but this is no longer possible if I want to find the title of a level 3 section. For example, an email the other day mentioned the subsection "Distances and measurements" and I actually had to run grep in the Documentation source code to find out that it was located in section 5.4.3. Similarly, I myself referred to the "Piano centered dynamics" template in a recent email and you cannot locate it easily if you search for "centered" in the table of contents. Even if everybody made it a habit to always include the section number when referring to a section on the mailing list, you can be certain that these section numbers will change more often than the titles themselves so if somebody looks into the mailing list archives 3 years later I'm sure that the section numbers will have changed so it will be hard to find the section. I certainly realize that it might take too much space to have this fully expanded table of contents in the left margin all the time, but it should at least be possible to select to view the full version in the main window. /Mats ___ 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: RhythmicStaff - gray-scaling and getting rid of double heads for chords
> "V" == Vivian Barty-Taylor <[EMAIL PROTECTED]> writes:
V> The "doubled" Noteheads come about because RhythmicStaff
V> interprets all pitches as the same. I don't know what effect you
V> are wanting exactly
Thanks.
Im after what ive understood RhythmicStaff was meant for, a simple way
of wrapping an existing and unmodified set of music inside a context
outputting only the rhytmic line, apart from avoiding the double
note-heads coming from offsetting multiple notes in different columns.
Below is some code reproducing the problem.
<>
Yes indeed, it can be done quite simply with a scheme-function to filter
every 2-or-more length 'element of 'EventChord and consing up the result
inside a 'ContextSpeccedMusic, or setting up a one-line staff and
generating special versions of the input-data. But hoping to avoid
these kinds of hacks in general tasks would be my main objective to move
towards lilypond.
Ive tried setting up the context with various removes, ie:
RhythmicStaff \with {
\remove Collision_engraver
\remove OtherPlausibleCandidates_engraver
} {...}
- but no bingo yet. I hope to learn more along the way, and im sure
theres something silly or simple (or even complex, as long as its a
general solution) thing i have disregarded.
tmp.ly
Description: example of problem
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
2008/9/29 Mats Bengtsson <[EMAIL PROTECTED]>: > I haven't had the time to read all the discussions related to the new > web layout of the 2.11 documentation, but wonder if I'm the only one who > miss the possibility to view the full table of contents with all > subsections expanded. Hi Mats, I definitely agree with you! Wouldn't it be possible to have the *complete* detailed TOC, at least at http://kainhofer.com/~lilypond/Documentation/user/lilypond/ ? The tocframe div on the left is great the way it is, but we definitely do need to have a detailed TOC on the first page. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Regarding the new Table of Contents in the GUB docs
On Mon, Sep 29, 2008 at 2:10 PM, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > Hi, > > I haven't had the time to read all the discussions related to the new > web layout of the 2.11 documentation, but wonder if I'm the only one who > miss the possibility to view the full table of contents with all > subsections expanded. I'm very used to search for some word in the table of > contents, when I want to find the appropriate section in the manual, but > this is no longer possible if I want to find the title > of a level 3 section. For example, an email the other day mentioned > the subsection "Distances and measurements" and I actually had to run grep > in the Documentation source code to find out that it was located in section > 5.4.3. Similarly, I myself referred to the "Piano centered dynamics" > template in a recent email and you cannot locate it easily if you search for > "centered" in the table of contents. > Even if everybody made it a habit to always include the section number > when referring to a section on the mailing list, you can be certain that > these section numbers will change more often than the titles themselves > so if somebody looks into the mailing list archives 3 years later I'm sure > that the section numbers will have changed so it will be hard to find the > section. > > I certainly realize that it might take too much space to have this > fully expanded table of contents in the left margin all the time, but it > should at least be possible to select to view the full version > in the main window. That's not a bad idea, IMO. Some people have commented that too much space is being *wasted* in the Table of Contents pane, but I assume they are viewing the docs with a large monitor or in high resolution. On my laptop with 1280x800 resolution, the current TOC layout is the perfect width, but on the 1920x1200 monitor I am currently using, a fully-expanded Table of Contents would look very nice. Hopefully if we can implement a search box in the TOC pane with server-side scripting, the documentation will be much easier to navigate. But this might have to wait until after the 2.12 release. Regards, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Regarding the new Table of Contents in the GUB docs
Hi, I haven't had the time to read all the discussions related to the new web layout of the 2.11 documentation, but wonder if I'm the only one who miss the possibility to view the full table of contents with all subsections expanded. I'm very used to search for some word in the table of contents, when I want to find the appropriate section in the manual, but this is no longer possible if I want to find the title of a level 3 section. For example, an email the other day mentioned the subsection "Distances and measurements" and I actually had to run grep in the Documentation source code to find out that it was located in section 5.4.3. Similarly, I myself referred to the "Piano centered dynamics" template in a recent email and you cannot locate it easily if you search for "centered" in the table of contents. Even if everybody made it a habit to always include the section number when referring to a section on the mailing list, you can be certain that these section numbers will change more often than the titles themselves so if somebody looks into the mailing list archives 3 years later I'm sure that the section numbers will have changed so it will be hard to find the section. I certainly realize that it might take too much space to have this fully expanded table of contents in the left margin all the time, but it should at least be possible to select to view the full version in the main window. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff - gray-scaling and getting rid of double heads for chords
Hi Anders,
I'm not sure about the colouring issue. Hoping someone else has some
ideas.
The "doubled" Noteheads come about because RhythmicStaff interprets
all pitches as the same. I don't know what effect you are wanting
exactly, but if you want a single staff line with Noteheads on either
side of it you could use a normal Staff and set #'line-count to #1
( the exact syntax for doing this is \override Staff.StaffSymbol
#'line-count = #1 ) You can put a percussion clef on this staff with
\clef "percussion" in which case the central pitch is c' .
I'm impressed by your Scheme function to set up the Context. Lilypond
also has a native syntax for altering contexts ( where you can,
indeed, add and remove engravers. ) See 9.2.6 Changing context
default settings and 9.2.4 Modifying context plug-ins in the manual.
You can find a complete list of Engravers in the Program Reference .
A simpler way to change staff size is:
#(set-global-staff-size value) which scales everything.
See:
11.2.1 Setting the staff size
Footnotes:
[1] I am honestly doing some research before asking here. Before
asking
here im looking in the manuals ive got, searching the .info pages, and
finally the web.
No need for this apology! Many people ask much simpler questions here.
All the best,
Vivian.
On Sep 29, 2008, at 2:57 PM, [EMAIL PROTECTED] wrote:
Id like to make a smaller RhythmicStaff with some special qualities,
like smaller font etc. This one works fine, but i have a couple of
things id like to fix[1] (see below):
rytmestaff = #(define-music-function (parser location navn rytmer)
(string? ly:music?)
#{
\context RhythmicStaff = $navn {
\set Staff.fontSize = #-3
\override Staff.StaffSymbol #'color = #(x11-color 'gray60)
\override Staff.StaffSymbol #'staff-space = #(magstep -3)
$rytmer
}
#})
1) Id like to gray-scale the whole staff. Is there a simple way[2]
instead
of overriding zillions of objects w. properties to draw everything
inside the RhythmicStaff context in 'gray80? Ie:
\override Staff.StaffSymbol #'color = #(x11-color 'grey60)
\override Staff.TimeSignature #'color = #(x11-color 'grey60)
\override Staff.Clef #'color = #(x11-color 'grey60)
\override Staff.NoteHead #'color = #(x11-color 'grey60)
\override Staff.Stem #'color = #(x11-color 'grey60)
\override Staff.BarLine #'color = #(x11-color 'grey60)
\override Staff.Beam #'color = #(x11-color 'grey60)
2) For every chord in the input i get a 'doubled' note-head in the
RhythmicStaff? How to get rid of those? Is there a chord-engraver or
notecolumn-engraver i can grab and do something with inside this
context?
Footnotes:
[1] I am honestly doing some research before asking here. Before
asking
here im looking in the manuals ive got, searching the .info pages, and
finally the web.
[2] Guess what, im starting to beleive there is...
Thanks,
-anders
___
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
stem direction \longa
Hi, the \stemUp command does not work for \longa in my score. Any solutions? Thank you, Alan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics, Staff and dynamics
Note that this template is old and that "Dynamic_engraver" should be replaced with "New_dynamic_engraver" and "Dynamic_line_engraver" See http://lists.gnu.org/archive/html/lilypond-user/2008-07/msg00242.html On Monday, September 29, 2008, at 12:11PM, "Dmytro O. Redchuk" <[EMAIL PROTECTED]> wrote: >2008/9/29 Mats Bengtsson <[EMAIL PROTECTED]>: >> Why not use the "Dynamics" context, defined in the template for >> Piano with centered dynamics? >Great. Thanks! :-) > >> /Mats > >-- >Dmytro O. Redchuk > > >___ >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
RhythmicStaff - gray-scaling and getting rid of double heads for chords
Id like to make a smaller RhythmicStaff with some special qualities,
like smaller font etc. This one works fine, but i have a couple of
things id like to fix[1] (see below):
rytmestaff = #(define-music-function (parser location navn rytmer) (string?
ly:music?)
#{
\context RhythmicStaff = $navn {
\set Staff.fontSize = #-3
\override Staff.StaffSymbol #'color = #(x11-color 'gray60)
\override Staff.StaffSymbol #'staff-space = #(magstep -3)
$rytmer
}
#})
1) Id like to gray-scale the whole staff. Is there a simple way[2] instead
of overriding zillions of objects w. properties to draw everything
inside the RhythmicStaff context in 'gray80? Ie:
\override Staff.StaffSymbol #'color = #(x11-color 'grey60)
\override Staff.TimeSignature #'color = #(x11-color 'grey60)
\override Staff.Clef #'color = #(x11-color 'grey60)
\override Staff.NoteHead #'color = #(x11-color 'grey60)
\override Staff.Stem #'color = #(x11-color 'grey60)
\override Staff.BarLine #'color = #(x11-color 'grey60)
\override Staff.Beam #'color = #(x11-color 'grey60)
2) For every chord in the input i get a 'doubled' note-head in the
RhythmicStaff? How to get rid of those? Is there a chord-engraver or
notecolumn-engraver i can grab and do something with inside this
context?
Footnotes:
[1] I am honestly doing some research before asking here. Before asking
here im looking in the manuals ive got, searching the .info pages, and
finally the web.
[2] Guess what, im starting to beleive there is...
Thanks,
-anders
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Input big score in Latex
Have you, by chance, included a \book{...} block in your score.ly file?
If that's the case, then I can understand
that you get this problem. If you don't have any explicit
\book{...} block, then you can get a page break between
any score line (system), so you shouldn't get the problem
you describe (well, unless you have an orchestral full score
where each system fills the whole page).
/Mats
Quoting Marcos di Silva <[EMAIL PROTECTED]>:
Hi,
I'm trying to input a large score (more than 20 pages) in a Latex
document. I have a code like:
...
\chapter{Score}
\begin{lilypond}
\input{score.ly}
\end{lilypond}
...
The first page is cut because the chapter name position pushes the
score down. I think I can solve the problem changing first page size
or bottom margin.
Is it possible?
--
Marcos di Silva
http://www.marcosdisilva.net/
___
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: Input big score in Latex
> "Marcos" == Marcos di Silva <[EMAIL PROTECTED]> writes:
Marcos> I'm trying to input a large score (more than 20 pages) in a Latex
Marcos> document. I have a code like:
Marcos> ...
Marcos> \chapter{Score}
Marcos> \begin{lilypond}
Marcos> \input{score.ly}
Marcos> \end{lilypond}
Marcos> ...
Marcos> The first page is cut because the chapter name position pushes the
Marcos> score down. I think I can solve the problem changing first page size
Marcos> or bottom margin.
Marcos> Is it possible?
I don't think that should happen, but I would have said:
\chapter{Score}
\lilypondfile{score.ly}
And when I do that, things seem to work ok.
--
Laura (mailto:[EMAIL PROTECTED] http://www.laymusic.org/ )
(617) 661-8097 233 Broadway, Cambridge, MA 02139
Solitary Observation Brought Back From A Sojourn In Hell
At midnight tears
Run into your ears.
Louise Bogan
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Scheme function for tempo marking -- "hash" for names?
Hi, all,
i'm sorry, this is, probably, purely-scheme-related-question.
Sorry, i'm not a programmer.
I wanted to align tempo mark ("Adagio", "Moderato" etc)
left-side-centered on key signature
if it is not C-dur or A-moll, otherwise aligned left-side above left
side of time signature.
I wrote small function for tempo marking:
tempoMark =
#(define-music-function (parser location mark anchor offset)
(string? list? number?)
#{
\once \override Score.RehearsalMark #'self-alignment-X = #-1
\once \override Score.KeySignature
#'break-align-anchor-alignment = #CENTER
\once \override Score.TimeSignature
#'break-align-anchor-alignment = #LEFT
\once \override Score.RehearsalMark
#'break-align-symbols = #$anchor
\once \override Score.RehearsalMark #'Y-offset = #$offset
\mark \markup { \bold \smaller $mark }
#})
I use it like this:
\tempoMark "Moderato" #'(key-signature) #0
Next, let's say, i would like to have tempo marking translated into Ukrainian
("Швидко" instead of "Allegro" etc.). But i'm not sure that i will not
change those
translations, so i would like to have a function like this:
moderato =
#(define-music-function (parser location anchor offset)
(list? number?)
#{
\tempoMark "Помірно" $anchor #$offset
#})
and to use it like this:
\moderato #'(key-signature) #0
So, if i decide to "translate back", or to change translations, i can
modify function definition.
But in this case i need to write a lot of identical functions.
So, two questions:
1. Is it possible to define a "hash" (key->value) and use it in a
single function?
I am not a programmer [*], so please give me a clue.
2. May be, i am quite *wrong*, and should use some different approach?
Thank you.
* I know how to program this in Python, perl, awk, bash;
however i'm not a programmer at all, that's why i'm asking
for "keyword" or "template", or smth like this.
--
Dmytro O. Redchuk
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics, Staff and dynamics
2008/9/29 Mats Bengtsson <[EMAIL PROTECTED]>: > Why not use the "Dynamics" context, defined in the template for > Piano with centered dynamics? Great. Thanks! :-) > /Mats -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Input big score in Latex
Hi,
I'm trying to input a large score (more than 20 pages) in a Latex
document. I have a code like:
...
\chapter{Score}
\begin{lilypond}
\input{score.ly}
\end{lilypond}
...
The first page is cut because the chapter name position pushes the
score down. I think I can solve the problem changing first page size
or bottom margin.
Is it possible?
--
Marcos di Silva
http://www.marcosdisilva.net/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics, Staff and dynamics
Quoting Risto Vääräniemi <[EMAIL PROTECTED]>: 2008/9/29 Dmytro O. Redchuk <[EMAIL PROTECTED]>: i guess: since dynamics are "parts" of Voice context, and Lyrics is a separate context (of "the same level") -- it is impossible to place dynamics far from staff than lyrics (to place lyrics between staff and dynamics). I've been wondering that too and I've found no easy solution so far. However, I must admit that I've been naughty and used extra-offset to do the trick. :-) Why not use the "Dynamics" context, defined in the template for Piano with centered dynamics? /Mats -Risto ___ 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: Lyrics, Staff and dynamics
2008/9/29 Dmytro O. Redchuk <[EMAIL PROTECTED]>: > i guess: since dynamics are "parts" of Voice context, > and Lyrics is a separate context (of "the same level") -- > it is impossible to place dynamics far from staff than lyrics > (to place lyrics between staff and dynamics). I've been wondering that too and I've found no easy solution so far. However, I must admit that I've been naughty and used extra-offset to do the trick. :-) -Risto ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to stop melisma line?
Another solution, (and the one that I use), is to put the notes for which the
words are different into a different voice context, and then add lyrics to that
voice. It requires a bit more planning before you begin to typeset, but it
makes files a little easier to navigate, in my opinion, and I can separate
things out a bit easier.
soprano = \relative c'' {
\context Voice = "soprano 1" {
c4 c c c ~
c1 ~
c4 } c r c
\context Voice = "soprano 2" { c4 c c c }
}
alto = \relative a' {
a4 a a a
a a a a
a a a a
a a a a
}
sopranolyricsone = \lyricmode {
la -- la -- la -- la __
}
sopranolyricstwo = \lyricmode {
la -- la -- la
}
altolyrics = \lyricmode {
la -- la -- la -- la,
la -- la -- la -- la,
la -- la -- la -- la,
la, la -- la -- la!
}
\score {
<<
\new Staff = "staff" <<
\context Voice = "soprano" { \voiceOne \soprano }
\context Voice = "alto" { \voiceTwo \alto }
>>
\new Lyrics \with { alignAboveContext = "staff" } \lyricsto "soprano 1"
\sopranolyricsone
\new Lyrics \with { alignAboveContext = "staff" } \lyricsto "soprano 2"
\sopranolyricstwo
\new Lyrics \lyricsto "alto" \altolyrics
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyrics, Staff and dynamics
Hi all, i guess: since dynamics are "parts" of Voice context, and Lyrics is a separate context (of "the same level") -- it is impossible to place dynamics far from staff than lyrics (to place lyrics between staff and dynamics). Is that true? Thank you. -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to stop melisma line?
Hi Dmytro,
replace uplyr by the following:
uplyr = \lyricmode {
la -- la -- la -- la __ "" _ _
la -- la -- la
}
You should know, that _ does the same as \skip 1, but is easier to write.
Hope this helps!
Dominic
2008/9/29 Dmytro O. Redchuk <[EMAIL PROTECTED]>:
> Hi, all.
>
> In vocal scores i often put soprano and alto in one staff
> and use soprano lyrics with a lot of skips, so soprano has lyrics only
> if it differs from alto's lyrics.
>
> Please, masters, take a look at this fragment -- melisma line in soprano voice
> extends too far, over skips, rests and skips again:
>
> \version "2.11.42" % is this the problem?
>
> upper = \relative c'' {
> c4 c c c ~
> c1 ~
> c4 c -"skip!" r c -"skip!"
> c4 -"skip!" c c c
> }
>
> lower = \relative a' {
> a4 a a a
> a a a a
> a a a a
> a a a a
> }
>
> uplyr = \lyricmode {
> la -- la -- la -- la __
> \repeat "unfold" 3 { \skip 1 }
> la -- la -- la
> }
>
> lolyr = \lyricmode {
> la -- la -- la -- la,
> la -- la -- la -- la,
> la -- la -- la -- la,
> la, la -- la -- la!
> }
>
> \score {
> \new Staff = "staff" <<
>\new Voice = "upper" { \voiceOne \upper }
>\new Lyrics \with { alignAboveContext = "staff" } \lyricsto "upper" \uplyr
>\new Voice = "lower" { \voiceTwo \lower }
>\new Lyrics \lyricsto "lower" \lolyr
> >>
> }
>
> Thank you.
>
> --
> Dmytro O. Redchuk
>
>
> ___
> 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
