Re: Subject: GDP: index entries for snippets
Not knowing the question to ask is often a problem for me to. You are not alone with this experience. Perhaps he is asking how docbook format works. I'm just guessing about his query myself. > > The html version's indeces. See above for general pointers, there > > really is just one main thing that/which (aargh! you've made me > > realise I have no idea how to use that/which now...) give my skin > > rashes. Namely, how does it work? (You don't have to answer here as I > > already have figured most of it out, but it really would help if > > someone explains it in the docs themselves.) > > Sorry, I don't understand -- you look for the term you want, then > click on the link. I know this sounds like a completely stupid > and useless answer, but I really don't understand the question > "how does it work". However, I'll add this; It is truly frustrating to have a question and not know how to ask it. I know that you all cannot help with this, its a personal struggle (chuckle) we all have had at one time or other. It just happens with Lilypond more often. That isn't a comment on the quality of the workmanship on the project as much as it is a comment on the complexity of the objectives of the project. Written music itself is a major challenge, Western European Music is another order more complex than most. Lilypond not only renders WEM, but adds music of other cultures to the mix. Its sort of like trying to be all things to all people. That Lilypond has gotten as far as it has is something of a miracle in itself! -- David Fedoruk B.Mus. UBC,1986 Certificate in Internet Systems Administration, UBC, 2003 http://recordjackethistorian.wordpress.com "Music is enough for one's life time, but one life time is not enough for music" Sergei Rachmaninov ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
musicxml2ly problems
Message: 5 Date: Sat, 9 Feb 2008 23:38:58 + (UTC) From: Reinhold Kainhofer <[EMAIL PROTECTED]> Subject: Re: musicxml2ly problems To: lilypond-user@gnu.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line 1789, in print_ly_additional_definitions for a in set(needed_additional_definitions): NameError: global name 'set' is not defined Hmm, that's weird. Which version of Python do you have installed? The "set" data type is new in Python 2.3, and is needed in musicxml2ly to prevent duplicate definitions (i.e. I store all needed additional definitions in a list. However, some of them might be needed more than once throughout the piece, so some definitions are duplicate). By converting the list to a set, Python automatically gets rid of any duplicates, and no duplicate definitions should be written to the .ly file... Cheers, Reinhold I have no idea which version of python it is. Just whatever is in Lilypond 2.11.37 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
bug in bendAfter + grace?
Can anyone reproduce this? I'm using lilypond 2.10.33 \override NoteColumn #'X-extent = #'(0 . 1) \bendAfter #4 \grace c' a' \bendAfter #4 \grace c' a' Why does only the first bendAfter show up? Thanks! -cj (NOTE: \glissando and \slur produce a similar notation that works, but \bendAfter is closer to what I want becase it curves and ends at the bottem-left corner of the next note-head -- my intention is to hide the grace notes to produce a 'bend' notation) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Augmentation dot on polyphonic notes a second apart
I'm running 2.11.38. In reviewing the output, I see that in situations where the score contains polyphonic voices, stems in opposing directions, and the upper voice but not the lower has an augmentation dot, the placement of the dot in the output is ambiguous. The source scores I have add horizontal space between the notes to allow the dot to clearly apply to the upper voice. Is this a bug? Is there a tweak? Thanks Steve ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Insufficent space around bar lines
I'm reducing the spacing-increment to #0.80 to get a tightly spaced score. The notes are spaced to my liking except that they crowd the barlines. Is there a way to give the barlines more space? Steve ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Rhythm mark snippet in LSR not 2.11. compatible?
Hi again, I found a wonderful snippet in LSR that explained how to create rhythm marks (http://lsr.dsi.unimi.it/LSR/Item?id=204). I tested it and found out that it doesn't work that well with 2.11.(37). The space between the mark and the staff is much bigger than in the example image. If you have a look at the attached images you'll get the drift. To my eye the code contains pretty normal stuff and I cannot see what affects the spacing but I'm no expert anyway. Do you think there's any hope making it work properly in 2.11? -Risto <><>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: musicxml2ly problems
> File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line > 1789, in print_ly_additional_definitions > for a in set(needed_additional_definitions): > NameError: global name 'set' is not defined Hmm, that's weird. Which version of Python do you have installed? The "set" data type is new in Python 2.3, and is needed in musicxml2ly to prevent duplicate definitions (i.e. I store all needed additional definitions in a list. However, some of them might be needed more than once throughout the piece, so some definitions are duplicate). By converting the list to a set, Python automatically gets rid of any duplicates, and no duplicate definitions should be written to the .ly file... Cheers, Reinhold ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
musicxml2ly problems
Hello, I'm finding some old(er) files on my computer that I'd like to work with again, but this time in Lilypond. I'm converting them from Finale using musicxml. Unfortunately, the files don't convert and this is what I get: James-TiGERmac:/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly -r -v -l deutsch lasciatemi\ morire.xml Reading MusicXML from lasciatemi morire.xml ... Converting to LilyPond expressions... Converting to LilyPond expressions... Converting to LilyPond expressions... Converting to LilyPond expressions... Output to `lasciatemi morire-defs.ly' Traceback (most recent call last): File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line 1926, in ? main() File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line 1921, in main voices = convert (filename, options) File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line 1870, in convert print_ly_additional_definitions (printer, filename) File "/Applications/LilyPond.app/Contents/Resources/bin/ musicxml2ly", line 1789, in print_ly_additional_definitions for a in set(needed_additional_definitions): NameError: global name 'set' is not defined The output of the file is: \version "2.11.37" % automatically converted from lasciatemi morire.xml %% additional definitions required by the score: And I don't get the appropriate lasciatemi\ morire.ly file that I should get. I've been able to do this conversion in the past, but for some reason now it isn't working for me. Did I do something to offend Lilypond? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trills too far left?
Hi Trevor, You ever have the "tr." parts of your trill spanners start showing up too far to the left? [...] Ever seen this one before? Yes! Unfortunately, like your case, mine were in the middle of a large score -- the chamber opera I wrote last year -- and so I never got around to isolating a minimal bug-snippet-example. Good luck, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding a lyrics extender line to an alternate ending
Hi Risto,
Can anyone tell me if there's a way to print a lyrics extender line in
the beginning of the alternate ending?
See attached for a hint.
Hope this helps!
Kieren.
START
\version "2.11.37"
moveLE = \once \override LyricExtender #'extra-offset = #'(-0.8 . 0 )
\paper { ragged-right = ##t }
{
\repeat volta 2
{
c'2 c'2 ~
}
\alternative
{
{ c'1 }
{ c'2\repeatTie c''2 }
}
\bar "|."
}
\addlyrics { Tra la __ \moveLE \markup { "" } __ lah. } % does't work
END
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR account problem
2008/2/9, Libero Mureddu <[EMAIL PROTECTED]>: > I forgot my username and password for LSR, is there a way to get those > infos or should I open a new one? Honestly, you'd better open a new one; it's gonna be faster and simpler :) ... unless Sebastiano can do anything. Seba? Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Trills too far left?
Hi Kieren, You ever have the "tr." parts of your trill spanners start showing up too far to the left? The png attached gives an example from the middle of a large score that I'm almost completely done with. No code snippet, alas, because the problem only seems to show up in the middle of large scores (ugh). Ever seen this one before? Trevor. -- Trevor Bača [EMAIL PROTECTED] <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Adding a lyrics extender line to an alternate ending
Hi,
Can anyone tell me if there's a way to print a lyrics extender line in
the beginning of the alternate ending? Please, have a look at the
image and the example to get a better view what I mean.
I tried to use underscores but they were not vertically aligned with
the extender line. It also seems that there are small gaps between
them. I've tried some other tricks, too, but they didn't work.
-Risto
Start
\version "2.11.37"
\paper { ragged-right = ##t }
{
\repeat volta 2 {
c'2 c'2 ~ } \alternative {{
c'1}{
c'2\repeatTie c''2 }}
\bar "|."
}
\addlyrics { Tra la __ "___" lah. } % not quite
%\addlyrics { Tra la __ "" __ lah. } % does't work
%\addlyrics { Tra la __ " " __ lah. } % does't work
END
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Arabic music half flat accidental shape
On 8 Feb 2008, at 15:02, Reinhold Kainhofer wrote: Am Donnerstag, 17. Januar 2008 schrieb Hans Aberg: A half flat in Arabic music is displayed as a b but with a slash across (It is hard to describe the shape precisely). Is it possible to access such a symbol, and if not, is it possible to add it in the future? Is this what they use on http://www.maqamworld.com/ It seems to me that this is exactly the accidentals.flat.slash character in Lilypond's feta font: http://lilypond.org/doc/v2.11/Documentation/user/lilypond/The-Feta- font Thanks. I just made a file for ARab maqam notation interpretation in 36-ET. The Turkish example in "Snippets", "Pitches", though seems wrong, because it divides the 12-TET whole tone into 9 parts, which leads to 54-ET, whereas the notation in question refers to 53-ET: The major second M is divided into 9 parts, and the minor second m is divided into 4 parts, each part also called a "comma". So it gives 5M+2m = 53 commas, in the full octave. (This is just one of the n-ET approximations of the Pythagorean tuning which can be gotten by computing continued fraction convergents of log_2 3/2, which are 0, 1, 1/2, 3/5 , 7/12, 24/41, 31/53, 179/306 where, for example 7/12 means that key 7 is a good approximation of the pure fifth 3/2 in 12-Et.) Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subject: GDP: index entries for snippets
On Sat, 9 Feb 2008 12:55:06 +0100 "Kess Vargavind" <[EMAIL PROTECTED]> wrote: > First, I love indeces (indexes?) and use them everywhere. Would you be willing to maintain the indeces/indexes? Some of the doc writers (including myself) either aren't good, or aren't interested, in trying to think of potential terms. I'd rather have those people work on the actual documentation text. The idea is this: once we've finished a section of the docs (for example, NR 1.1 Pitches), you take the file and add whatever index entries wherever you want. I won't complain about having too many or too few or if they're in the wrong place or whatever... but in exchange, if anybody complains about the index (too much info, links in the wrong places, whatever), I send those complaints to you. :) Just as a reminder, a few weeks ago I offered a challenge: tell me exactly what index text to add, and I can do so in less than 30 seconds. As a result of that challenge, 1 person offered 1 index entry. Nobody else did anything. > Explanations about the indeces. I always look for a paragraph or two > just before the index itself, that (which?!) explains the > conventions. Especially needed in the html version, if I may say so. > (See below.) Not so important, but might help the user finding what > they want. Easily added. Just send me whatever text you suggest. Ideally something that makes sense for all output formats, but if necessary we could insert HTML-only text. I added examples of this intro text to the GDP site. > Different indeces. This is good and important. At the moment there's > two, though spontaneously I think them to be good choices (a general > one versus one for the commands) they would really further the > indeces' purpose if they truly split up. I mean this, the command > index' coverage is great (but as always, can be tweaked further) but > needs some loving in the formatting and sorting department, while the > general index really needs a work-through. This is easily done -- actually, it was a technical challenge to get them combined in the first place. But when the question first arose two years ago, the general concensus was that the general index should include commands as well. I'm quite open to changing this, but I'd want a fair amount of discussion first. > The command index. A few suggestions: > ___ Sort alphabetically (after usage rather than literally), that is, > do not sort under a leading interpunction symbol. Example order: > ___ Sort under the letters A to Z and one or two others. For instance > that !, /+, ~ & c. are sorted under one heading, e. g. "Symbols". > ___ Always use main head words (although they in > some cases may be contrived and hypothetical, they really help the > > The aboe points hold true in general, but specifically so for the pdf All those things would be nice, but we cannot do this for technical reasons. If you're interested in more information, please see the texinfo manual (ie google for it) and look at their info about indices. Sorry. > The html version's indeces. See above for general pointers, there > really is just one main thing that/which (aargh! you've made me > realise I have no idea how to use that/which now...) give my skin > rashes. Namely, how does it work? (You don't have to answer here as I > already have figured most of it out, but it really would help if > someone explains it in the docs themselves.) Sorry, I don't understand -- you look for the term you want, then click on the link. I know this sounds like a completely stupid and useless answer, but I really don't understand the question "how does it work". Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: GDP: LM 3-4
forgot to copy to list ... calvin mitcham wrote 09 February 2008 00:44 > "LM 3 and LM 4 are quite hard going for > anyone fairly new to LilyPond". thank you > trevor! i am certainly a newbie, and > although i have always found these sections > very confusing, i never spoke up cause i had > no suggestions about how to improve them. > now that i'm trying to help, i'll ramble out > loud here a little... Thanks for taking the time to respond, Calvin. Hearing general impressions like yours is just as helpful as specific comments. > to just read these sections is confusing and > boring. the tweaking is especially hard to read. I'm sure it is. They were not really intended to be "just read"; they were intended to guide the reader through the intricacies of using the Internals Reference to construct tweaks. They are more like a study guide, perhaps to be used when trying to solve a particular layout problem. > i mean i hardly ever have an issue about how > lilypond engraves, and when it is different > than what i'm transcribing, i usually don't > care. Unless you have a good reason to construct tweaks these sections are perhaps best left until you have. > i was proud/relieved recently, when after > ~10 minutes of targetted study, i got a > \once \override Score.MetronomeMark >#'padding = #4 > \tempo 4=88 > \set Score.skipBars = ##t R1*3 > to move the tempo marking above the "3" > for the multi-measure rest. when given a > specific problem to solve like this, Exactly! > the lm and nr docs are quite helpful. > i had to get the naming convention, which > engraver, and the property, and it worked > out pretty quickly. Great! That was our aim :) > but to just peruse the list of objects > and properties is painful. Maybe this is something we could address. Any suggestions? Should it be deleted? Shortened? More examples added? Exercises added? Or maybe the learning process is inherently painful anyway. > now file structure is another confusing > subject where again i have no sugesstion, > but i do wish it were easier for the newbie. > i worked on a couple of pieces for hours > trying to use includes etc to completely > minimize the amount of repeating any typing, > such as putting music notes for violin, > pianoright and pianoleft in separate files, > the combining to print a score, a piano > part with reduced violin above, and a > violin by itself. i got something passable, > but never nailed where some things. for > example, i could not get a piano with smaller > violin staff without repeating the violin > music with a smaller staff, or having the > violin part not show fingerings in the piano > printout. This sort of thing is exactly what we need to know - where difficulties are found - so the sections which deal with this can be revised. Thanks again. Trevor D ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OS X 10.5 Leopard
Yes, it doesn't work. See issue 506 or 508 in the bug list. Cheers, - Graham On Sat, 9 Feb 2008 08:56:08 -0600 Victor Eijkhout <[EMAIL PROTECTED]> wrote: > I've just started Lilypond for the first time since upgrading to > 10.5 and I only get the Apple menu and Lilypond, clicking on the > latter produces no menu. Java problems? I had 2.10.something, but > downloading 2.11.something made no difference. > > Victor. > > > ___ > 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: Dynamics 2
On Fri, 8 Feb 2008 13:47:29 + (UTC), Marco Pagliari wrote: > I'm creating MIDI files for my choir. How can I set different volume levels > for each section, to make one be in evidence among the others? > What I understand by reading section 1.3 is that dynamics can only be > attached > to notes, so I should repeat the dynamic mark for each note. You don't have to repeat the marks. That part of the manual means if you try to attach the dynamic to a bar line, or something else, then it won't work. Attach your dynamic to the first note it should apply to, and Lilypond takes care of things properly. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
OS X 10.5 Leopard
I've just started Lilypond for the first time since upgrading to 10.5 and I only get the Apple menu and Lilypond, clicking on the latter produces no menu. Java problems? I had 2.10.something, but downloading 2.11.something made no difference. Victor. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: LM 3-4
On Fri, 8 Feb 2008 19:44:02 -0500 "calvin mitcham" <[EMAIL PROTECTED]> wrote: > now that i'm > trying to help, i'll ramble out loud here a little... to just read > these sections is confusing and boring. the tweaking is especially > hard to read. i mean i hardly ever have an issue about how lilypond > engraves, and when it is different than what i'm transcribing, i > usually don't care. I'm generally the same way. :) But let's try to un-ramble a bit: - is the tutorial clear? (I don't think anybody has complained about this, but I can never be certain -- if you haven't done so recently, please read the tutorial and try to remember what things confused you in the beginning.) - is LM 3 Fundamental clear? Given your stated interest, I suggest you just focus on that for now. If you're happy with lilypond output, then LM 4 Tweaks is almost completely pointless... and I know from great experience that it's really difficult to read *any* documentation (or, *cough*, textbook :) if you're not interested in the subject and/or don't see an application of that knowledge. > i was proud/relieved recently, when after ~10 minutes of targetted > study, i got a > > \once \override Score.MetronomeMark #'padding = #4 > \tempo 4=88 > \set Score.skipBars = ##t R1*3 As a historical sidenote, try looking at the mailist archives from 5 or more years ago. Having a relatively new user being able to figure this out in 10 minutes is a *huge* improvement in the docs. > to move the tempo marking above the "3" for the multi-measure rest. > when given a specific problem to solve like this, the lm and nr docs > are quite helpful. i had to get the naming convention, which > engraver, and the property, and it worked out pretty quickly. but to > just peruse the list of objects and properties is painful. With doc sections like LM 4.5.2, we've tried to make it so that you don't need to peruse the list of objects in the IR. It'll never be perfect, of course. > now file structure is another confusing subject where again i have no > sugesstion, but i do wish it were easier for the newbie. i worked on a > couple of pieces for hours trying to use includes etc to completely > minimize the amount of repeating any typing, such as putting music > notes for violin, pianoright and pianoleft in separate files, the > combining to print a score, a piano part with reduced violin above, > and a violin by itself. i got something passable, but never nailed > where some things. for example, i could not get a piano with smaller > violin staff without repeating the violin music with a smaller staff, > or having the violin part not show fingerings in the piano printout. Again, please read LM 3 in detail, and let us know exactly which section was confusing. ie LM 3.1.1: understandable? LM 3.1.2: understandable? ... etc. Don't try to jump ahead and read 3.1.3 if 3.1.2 isn't clear! This will be very helpful for us. I know that this kind of job is harder on the first few readers, but the agony you go through will indicate exactly what/how to improve the docs, which will benefit all future readers. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
BassFigure vertical alignment
I need to typeset a figured bass/organo part with the figures _above_
the bassline. I do this, by simply placing the FiguredBass context
between the two staves of the organo part. The problem is, however,
that the figures are still vertically aligned to the top. I tried
setting BassFigureAlignment.stacking-dir to #up, which aligns the
numbers properly to the bottom, but unfortunately also reverses the
order of the figures, i.e. placing the <3> of the last chord in the
attached example on top and the <6> at the bottom. To clarify even
more, the result should look something like this:
6
5 4
2 3 3
Any ideas, how I can easily align the bass figures to the bottom
baseline without reversing the stacking direction?
Mike
\version "2.11.37"
\context PianoStaff = "Organo" {
<<
\context Staff = "Organo Discanto" {
\relative c' {
\clef "treble"
\key f \major
\time 4/4
4|
}
}
\context FiguredBass = "Organo Numeri" {
\figuremode {
<_>4 <2> <5 3> <6 4 3> |
}
}
\context Staff = "Organo Basso" {
\relative c' {
\clef "bass"
\key f \major
\time 4/4
g4 f e d |
}
}
>>
}
This message was sent using IMP, the Internet Messaging Program.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: recorder fingering chart
Hi Tim and list,
actually I just discovered that there are already articulation signs
for closed and open.
Here is an example with half positions in between.
However, the articulations are closer to the staff than the markups.
Is there a way to make them at the same distance from the staff?
I tried different solutions without success.
Best regards,
Libero
\version "2.11.38"
\include "english.ly"
centermarkup = {
\once \override TextScript #'self-alignment-X = #CENTER
\once \override TextScript #'X-offset =#(ly:make-simple-closure
`(,+
,(ly:make-simple-closure (list
ly:self-alignment-interface::centered-on-x-parent))
,(ly:make-simple-closure (list
ly:self-alignment-interface::x-aligned-on-self
}
\score
{\relative c'
{
g\open
\once \override TextScript #'staff-padding = #-1.0 \centermarkup
g^\markup{\combine \musicglyph #"scripts.open" \musicglyph
#"scripts.tenuto"}
\centermarkup g^\markup{\combine \musicglyph #"scripts.open"
\musicglyph #"scripts.stopped"}
g\stopped
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to shorten a TrillSpanner
Hi Trevor, There's now a *much* better way of shortening one end of a trill spanner manually: using the new (as of 2.11.something) #'bound-details list. [...] TrillSpanner implements all the goodies in the #'bound- details list Thanks for the update -- this is wonderful news! Best regards, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: recorder fingering chart
Thanks Tim, it works well,
however, if I try to put those signs as markup, the "plus" doesn't work.
Bug or I'm doing something wrong?
Libero
Example follows:
\version "2.11.38"
\include "english.ly"
\score
{\relative c'
{
g^\markup{\musicglyph #"scripts.flageolet"}
g^\markup{\musicglyph #"scripts.plus"}
}
}
>
>
> Would this work for you?
>
> \version "2.11.38"
> \include "english.ly"
> \score
> {\relative c'
> {
> c-+ d-+ e-\flageolet f-\flageolet
> }
>
> Tim Reeves
--
Libero Mureddu
Vanha Viertotie, 21 as 417
00350 Helsinki
Finland
http://webusers.siba.fi/~limuredd/
http://www.myspace.com/liberomureddu
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
LSR account problem
Hi, I forgot my username and password for LSR, is there a way to get those infos or should I open a new one? ciao libero - http://webusers.siba.fi/~limuredd/ http://www.myspace.com/liberomureddu ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subject: GDP: index entries for snippets
Ho,
As a librarian-in-training I have to agree with Jay (it generally hurts more
omitting an entry than including it, especially in a open project like this
that/which doesn't really have page limits to think about). I've been
thinking on speaking up about the indeces for quite some while now but have
never really bothered taking my time to formulate what could be done to make
them more usable (at least to me).
First, I love indeces (indexes?) and use them everywhere. Though trying to
use the ones in the current manual I'm most often giving up, them not
working the way I assume. Below, some thoughts about the behaviour I assume,
why it does/doesn't work at the moment and what I suggest.
- - - - -
Explanations about the indeces. I always look for a paragraph or two just
before the index itself, that (which?!) explains the conventions. Especially
needed in the html version, if I may say so. (See below.) Not so important,
but might help the user finding what they want.
Different indeces. This is good and important. At the moment there's two,
though spontaneously I think them to be good choices (a general one versus
one for the commands) they would really further the indeces' purpose if they
truly split up. I mean this, the command index' coverage is great (but as
always, can be tweaked further) but needs some loving in the formatting and
sorting department, while the general index really needs a work-through.
The command index. A few suggestions:
• Sort alphabetically (after usage rather than literally), that is, do not
sort under a leading interpunction symbol. Example order: \addlyrics,
arranger, \autoBeamOff
• Sort under the letters A to Z and one or two others. For instance that !,
/+, ~ & c. are sorted under one heading, e. g. "Symbols".
The general index. A few suggestions.
• Remove the commands! They already are in the command index and as it is
now clutters the general one. True, in some usage cases it is great to have
them combined like that, but in others it is oppositely so. And already
having them available in a separate index, the commands are never long away,
so I say, purge them from the general index immediately. ;)
• Always use main head words (although they in some cases may be contrived
and hypothetical, they really help the index looker quickly find their need,
remember that the head words musn't always point to a specific page or
somewhere at all) and further narrowed entries come "beneath" (indented that
is). Example ("···" symbolising an indent), note the unreferencee notion of
the headword:
beams
···and line breaks 49 [or: "···line breaks, and"]
···automatic29
···feathered53
···kneed49
···manual 47, 52
The aboe points hold true in general, but specifically so for the pdf
version. One thing I personally love in the pdf is how the page numbers
themselves constitutes the links and the entries are ordinary,
"un-clickable" text. The html version though, some work is needed to.
The html version's indeces. See above for general pointers, there really is
just one main thing that/which (aargh! you've made me realise I have no idea
how to use that/which now...) give my skin rashes. Namely, how does it work?
(You don't have to answer here as I already have figured most of it out, but
it really would help if someone explains it in the docs themselves.)
This index really, really needs an explanatory paragraph! A few pointers.
• For each entry, there are two links, what's the difference?
• What's text after each head word?
To me, a more logical structure would be something like:
• The headwords themselves link to the relevant place
• No section names (that is, only the head words remain)
• Sorting as mentioned further above
• Whether subentries are grouped beneath a group headword or not as I
suggested for the pdf isn't as important or obvious here, as I
believe/assume the usage of indeces work a bit differently in a more
inherently electronic text
Or, a structure more similar to the one right now:
• Example entry: "Clef: Clef" and "Clef: Accidentals" (which otherwise could
be differentiated with explanatory/narrowed subentries, with number
appendages or the like)
• The index looker should with a quick glance understand the structure and
function of the index
• For instance, the head word remains as is now but without link (really
helps differentiating what is what, and what needs to be clicked)
• The section names remain with their links but if a certain headword point
to several sections (as "Clef" do), then merge them onto the same line)
- - - - -
No offence meant, if taken. I always have had a hard time forming my
understanding into words, especially so into a foregin language. And. Many
thanks for all's good work and for reading my personal purging urgings
through! :)
Love,
Kess
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/
Re: how to shorten a TrillSpanner
2008/2/9, Trevor Bača <[EMAIL PROTECTED]>: > [I can't remember if I've mailed this one out before or not, but as I had to > spend a couple of minutes rediscovering it myself, I thought I'd share. Also > mental note to check and add to LSR ...] Sure. Feel free to comment the code that does not work yet, and add the "version-specific" tag so I can track it later :-) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: index entries for snippets
2008/2/8, Graham Percival <[EMAIL PROTECTED]>: > Of course, I famously never use the index, so I'm not the best > person to judge whether certain index entries are helpful or not. Neither am I :-) Anyone else? Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
