Re: add-grace-properties in TabVoice context
Neil Puttock schrieb: 2009/7/9 Marc Hohl m...@hohlart.de: I have changed your improved parentheses handler to get the font-size for the parentheses from the TabNoteHead, so parentheses around grace notes are scaled properly in tablature. Looks good. Thank you! Let's just hope tablature users don't want to tweak the font-size of parentheses directly. ;) Why on earth should someone do this? They look just great! ;-) Marc Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: string-lines
Its the Chaconne from BWV1004. Matthieu Jacquot has the Lilypond source code of his arrangement for guitar available under a Creative Commons license on his web site, though that contains the notes without any fingering indications. See http://theshadylanepublishing.googlepages.com/transcriptions2. Nick From: lilypond-user-bounces+nick.payne=internode.on@gnu.org [mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] On Behalf Of Mario Moles Sent: Friday, 10 July 2009 8:50 AM To: lilypond-user@gnu.org Subject: Re: string-lines È possibile avere il file ly dell'esempio che riporti? Il file png è interessante! Grazie ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: string-lines
On Fri, 10 Jul 2009 10:55:35 +0200, Nick Payne nick.pa...@internode.on.net wrote: It’s the Chaconne from BWV1004. Matthieu Jacquot has the Lilypond source code of his arrangement for guitar available under a Creative Commons license on his web site, though that contains the notes without any fingering indications. See http://theshadylanepublishing.googlepages.com/transcriptions2. Nick Hello, That's true that I don't put any fingering in this piece, but I used to in others. I use two functions (for up and down orientation, I attach them, I hope it will work) I can't remember where I found them, I just made a few changes to adapt them to string numbers. The problem is that it creates problems with octaves. I will have a look at yours. By the way I've a new website (same content) http://theshadylanepublishing.com have a look at the Syrinx transcription preview (click on the picture) where I use these functions. Regards Matthieu -- Matthieu JACQUOT The Shady Lane Publishing: http://theshadylanepublishing.com (nouveau site!) fctguitar.ly Description: Binary data fctguitar2.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
2009/7/10 Graham Percival gra...@percival-music.ca: http://percival-music.ca/blogfiles/out/lilypond-general_1.html Now we're talking! Much, much better. Pretty cool, actually. No, I'd even go with handsome. Actually, seeing this website really made me want to give this little project of yours a try (what's it called already? Lilly... something?) There's now an Examples section, thanks to Jonathan Kulp. - currently, most examples have a click-to-expand thing. Some of them don't work expanded, others don't work non-expanded. But there's enough working stuff for you to get the idea. Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ More importantly, we need help. I recently re-iterated my claim that the lilypond community should have the program/bugs/documentation/website they deserve, but currently this isn't happening -- Patrick and I have spent a ton of time and effort on this website. I am probably familiar enough with the texinfo and CSS syntax to give you guys a hand. For instance, I should be able to handle the blinking Help wanted boxes (this looks sooo 1996 btw). The sub(sub)menus are still a little bit confusing (for instance when you click on manuals). But I think this is just a look-and-feel issue, not a structural problem. Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On Fri, Jul 10, 2009 at 11:37:15AM +0200, Valentin Villenave wrote: 2009/7/10 Graham Percival gra...@percival-music.ca: There's now an Examples section, thanks to Jonathan Kulp. - currently, most examples have a click-to-expand thing. Some of them don't work expanded, others don't work non-expanded. But there's enough working stuff for you to get the idea. Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ No javascript. Besides, the display isn't the issue; what's at issue is generating the images in an automatic, system-independent way. (as in not what's in the current makefile and examples/ dir) More importantly, we need help. I recently re-iterated my claim that the lilypond community should have the program/bugs/documentation/website they deserve, but currently this isn't happening -- Patrick and I have spent a ton of time and effort on this website. I am probably familiar enough with the texinfo and CSS syntax to give you guys a hand. For instance, I should be able to handle the blinking Help wanted boxes (this looks sooo 1996 btw). That's deliberate. We had to specially look up how to make it blink. My specific instructions were make it as ugly as possible. We want to handle the help wanted stuff by doing the required work. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: string-lines
In data venerdì 10 luglio 2009 11:24:56, hai scritto: On Fri, 10 Jul 2009 10:55:35 +0200, Nick Payne nick.pa...@internode.on.net wrote: It’s the Chaconne from BWV1004. Matthieu Jacquot has the Lilypond source code of his arrangement for guitar available under a Creative Commons license on his web site, though that contains the notes without any fingering indications. See http://theshadylanepublishing.googlepages.com/transcriptions2. Nick Hello, That's true that I don't put any fingering in this piece, but I used to in others. I use two functions (for up and down orientation, I attach them, I hope it will work) I can't remember where I found them, I just made a few changes to adapt them to string numbers. The problem is that it creates problems with octaves. I will have a look at yours. By the way I've a new website (same content) http://theshadylanepublishing.com have a look at the Syrinx transcription preview (click on the picture) where I use these functions. Regards Matthieu Ok Matthieu ora è bellissimo ma.. sarebbe ancora più bello se si riuscisse ad attaccare corda e linea alla nota. Esempi: -- oiram/bin/selom attachment: non.jpgattachment: yes.jpg___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Graham Percival wrote: On Fri, Jul 10, 2009 at 11:37:15AM +0200, Valentin Villenave wrote: 2009/7/10 Graham Percival gra...@percival-music.ca: There's now an Examples section, thanks to Jonathan Kulp. - currently, most examples have a click-to-expand thing. Some of them don't work expanded, others don't work non-expanded. But there's enough working stuff for you to get the idea. Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ No javascript. Besides, the display isn't the issue; what's at issue is generating the images in an automatic, system-independent way. (as in not what's in the current makefile and examples/ dir) More importantly, we need help. I recently re-iterated my claim that the lilypond community should have the program/bugs/documentation/website they deserve, but currently this isn't happening -- Patrick and I have spent a ton of time and effort on this website. I am probably familiar enough with the texinfo and CSS syntax to give you guys a hand. For instance, I should be able to handle the blinking Help wanted boxes (this looks sooo 1996 btw). That's deliberate. We had to specially look up how to make it blink. My specific instructions were make it as ugly as possible. We want to handle the help wanted stuff by doing the required work. Right! We don't need nicer-looking help boxes, we need to get rid of them! Folks, please, send something to me if you have nice-looking examples with some wow to them in any of these categories: 1. tablature 2. orchestra/opera/wind ensemble--something really big (surely someone has something better than my piece!) 3. pop music (something with a free enough license that we can use it) 4. some kind of world music 5. Something for use in music theory classes or other educational purposes that looks better than my counterpoint example--something with text balloons, colored noteheads, or whatever might be used in teaching music. Thanks! Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On do, 2009-07-09 at 21:55 -0700, Graham Percival wrote:
http://percival-music.ca/blogfiles/out/lilypond-general_1.html
Great. Thanks!
- I'm wasting a lot of time on mundane jobs. For example, the old
news page needs to be put into the new website source. This
means going through a bunch of things like
h2New German translaton! Aug 07, 2006/h2
pIch nein katza, a href=http://blah;auf blitzen/a drie./p
and turning it into
@subheading New German Translation! 2006 Aug 07
Ich nein katza, @uref{http://blah, auf blitzen} drie.
Not hard. I could even train an undergraduate to do this job!
git pull -r, see texinfo/news-to-texi.py. That should help.
Greetings,
Jan.
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl| http://lilypond.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On vr, 2009-07-10 at 02:41 -0700, Graham Percival wrote: No javascript. Why not? It would be nice to have the pages work a bit, without javascript, but as far as I'm concerned, we should use it. Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
I often browse the LilyPond homepage with a mobile phone. I would hate if JavaScript were needed. No problem though, if JavaScript-enabled users had a better experience. Bert Jan Nieuwenhuizen wrote: On vr, 2009-07-10 at 02:41 -0700, Graham Percival wrote: No javascript. Why not? It would be nice to have the pages work a bit, without javascript, but as far as I'm concerned, we should use it. Jan. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
ANN: LilyPondTool 2.12.858 Release Candidate
Hi, thanks to the bug hunters, I created an improved, fixed, shinier version of LilyPondTool. This is the Release Candidate before I release this to the jEdit plugin repository for the widest public. It contains some enhancements and many fixes, especially for the PDF viewer. Now you can turn the page back and not just forward for example :) (Though I just found a bug about turning the page, then clicking on a note.) Download it from: https://sourceforge.net/projects/lily4jedit/files/lily4jedit/lily4jedit-2.12.858.zip/download And unzip to the jEdit settings folder: $HOME/.jEdit, where $HOME is you home folder In the final release there will be documentation as well :) Cheers, Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
basic questions
Below is a open guitar-scale without tempo. I have 2 problems. And I have tried
to do due-diligence before posting to see if the information is available in
either the LSR or LilyPond Notation Reference, but I found nothing using my
search parameters.
1. The low E in the scale is too close to the treble clef. The C ledger-line
touches the clef. I tried to move the scale to the right by inserting s1
at the start; however, no change occurred in the output. I don't understand
why there is no change. If I put a hidden note in place of the s1, it does
what I want. So what is the best way to push the notes to the right to fix
this problem?
2. I tried to change the font-name and font-size for the lyrics (guitar
form-numbers).
\override Lyrics #'font-name = #times
\override Lyrics #'font-size = #-2
However, I don't know the grob name. What is the correct name? Or maybe I'm
not doing this right at all!
May I make a small suggestion (and it may already be done). Someplace in the
LilyPond manual, there needs to be a list of all the grob names and what they
do. I find I spend a lot of time linearly searching the manual hoping I'll come
across the right grob-name for something I want to change. In several cases, an
educated guess generates the right name. I tried that for Lyrics, but no
banana.
Cheers, and thanks
===
\version 2.13.3
\include english.ly
#(set-default-paper-size letter)
#(set-global-staff-size 25)
\paper {
line-width = 6.625\in
} % paper
\layout {
indent = 0.0
\context {
\Staff
\remove Time_signature_engraver
} % context
} % layout
notes = \relative c {
\key e \major
\override Staff.OctavateEight #'font-name = #times
\override Staff.OctavateEight #'font-size = #-2
\override NoteHead #'font-size = #-2
\clef treble_8
\cadenzaOn
%\hideNotes e,1 \unHideNotes
s1
\once \override NoteHead #'color = #red e,1 fs gs a b cs ds
\once \override NoteHead #'color = #red e fs gs a b cs ds
\once \override NoteHead #'color = #red e fs gs a b cs ds
\once \override NoteHead #'color = #red e fs
\bar |
} % relative
text = \lyricmode {
\override Lyrics #'font-name = #times
\override Lyrics #'font-size = #-2
_ I II III IV V VI VII I II III IV V VI VII I II III IV V VI VII I II
}
\score {
\context Voice = one {
\notes
}
\lyricsto one \new Lyrics \text
} % score
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: basic questions
Peter Buhr wrote: 1. The low E in the scale is too close to the treble clef. The C ledger-line touches the clef. I tried to move the scale to the right by inserting s1 at the start; however, no change occurred in the output. I don't understand why there is no change. If I put a hidden note in place of the s1, it does what I want. So what is the best way to push the notes to the right to fix this problem? That is very odd to my eye. It looks like a \cadenzaOn bug, but I've learned to be very hesitant in calling something a bug. I'll look into it. 2. I tried to change the font-name and font-size for the lyrics (guitar form-numbers). \override Lyrics #'font-name = #times \override Lyrics #'font-size = #-2 However, I don't know the grob name. What is the correct name? Or maybe I'm not doing this right at all! \override Lyrics . LyricText #'font-name = #times \override Lyrics . LyricText #'font-size = #-2 The space around the period is needed, see the last paragraph here: http://lilypond.org/doc/v2.13/Documentation/user/lilypond/File-structure May I make a small suggestion (and it may already be done). Someplace in the LilyPond manual, there needs to be a list of all the grob names and what they do. Documentation Index Internals Reference 3. Backend 3.1 All layout objects http://lilypond.org/doc/v2.13/Documentation/user/lilypond-internals/All-layout-objects Nice questions! - Mark ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: LilyPondTool 2.12.858 Release Candidate
Note: You can work around that bug, if you turn off Follow caret feature (and only turn on temporarily when looking for a note's position in the score). Bertalan Fodor (LilyPondTool) wrote: Hi, thanks to the bug hunters, I created an improved, fixed, shinier version of LilyPondTool. This is the Release Candidate before I release this to the jEdit plugin repository for the widest public. It contains some enhancements and many fixes, especially for the PDF viewer. Now you can turn the page back and not just forward for example :) (Though I just found a bug about turning the page, then clicking on a note.) Download it from: https://sourceforge.net/projects/lily4jedit/files/lily4jedit/lily4jedit-2.12.858.zip/download And unzip to the jEdit settings folder: $HOME/.jEdit, where $HOME is you home folder In the final release there will be documentation as well :) Cheers, Bert ___ 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: ANN: LilyPondTool 2.12.858 Release Candidate
Bertalan Fodor wrote: Note: You can work around that bug, if you turn off Follow caret feature (and only turn on temporarily when looking for a note's position in the score). Maybe Follow Caret should be unselected by default? Clicking on Hide Toolbar forces the user to open the Plugin Options window. Maybe you could add a menu item called Show/Hide Toolbar in Plugins LilyPondTool Process/view. PDF Viewer Even better. Thanks for the manual zoom stuff! Virtual Piano Strange that it would be difficult to make the buttons smaller. Of course I know nothing about developing for jEdit, so I'm not complaining -- it's still a cool feature! BTW I got the permission denied error again, but maddeningly, I can't figure out what I did to trigger it. The error output is below. Hope this helps. - Mark java.lang.NullPointerException at console.Console.handleMessage(Console.java:291) at org.gjt.sp.jedit.EditBus.send(EditBus.java:148) at org.gjt.sp.jedit.gui.DockableWindowManagerImpl$3.actionPerformed(DockableWindowManagerImpl.java:569) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.AbstractButton.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: LilyPondTool 2.12.858 Release Candidate
That's a bug in the Console plugin and/or jEdit itself. I'll file a bug report. Hope this helps. - Mark ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: basic questions
On 10.07.2009, at 16:19, Peter Buhr wrote: May I make a small suggestion (and it may already be done). Someplace in the LilyPond manual, there needs to be a list of all the grob names and what they do. I find I spend a lot of time linearly searching the manual hoping I'll come across the right grob-name for something I want to change. In several cases, an educated guess generates the right name. I tried that for Lyrics, but no banana. Cheers, and thanks Note there are very important distinctions between the Learning Manual and the Notation Reference. (And the Internals Reference too.) A lot of questions about where to find grobs and engravers, and the syntax that they all use are introduced or explained in the learning manual, and after reading it, it makes it much easier to understand where to find the answers to questions, even though the question probably isn't directly answered. Also, the Learning Manual (and the Notation Reference to a lesser degree) is not well-suited to the search and find method of question answering. It is more a primer, intended to be read through, before really attempting to notate anything with LilyPond. And while searches in the Notation Reference are considerably more effective, they benefit from having read through the Learning Manual at least once to become familiar with the terminology that LilyPond uses. James E. Bailey ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
minor chord names
Hello pond comrades,
some time ago I asked about displaying minor chord names as lowercase
letters without the m modifier, as it is common (at least) in German
folk songbooks.
I.e.
\context ChordNames {
\germanChords % or whatever
\chordmode { a:m }
}
should print as a instead of Am.
Is this possible nowadays, and how?
There's nothing appropriate in
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-chords
Since I don't need fancy jazz chords, perhaps there's a possibility
using chordNameExceptions?
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond and Jazz chords
Carl D. Sorensen wrote:
On 6/23/09 5:19 PM, Tim McNamara tim...@bitstream.net wrote:
On Jun 23, 2009, at 12:24 PM, Carl D. Sorensen wrote:
On 6/23/09 9:16 AM, Grammostola Rosea
rosea.grammost...@gmail.com wrote:
Tim McNamara wrote:
On Jun 15, 2009, at 2:00 PM, Kieren MacMillan wrote:
Wol et al:
Would it be reasonable to separate the functions of putting notes on
the staff and chord names above the staff, and let the user spell
out
the chord names separately from the notes on the staff? Doing so
might really simplify this discussion and result in better
control of
the final output.
To me (but I'm not a real experienced jazz musician or lilypond
user) I
agree with this comment.
Keep things simple!?
But this facility
a) doesn't exist in LilyPond
b) would require changes to the parser, and
c) has nobody who is willing to pursue doing it.
I think I may have written my comment poorly. What I meant was
having LilyPond *not* parse c e g b into a Cmaj7 chord name above
the staff at all. The parser is just going to run into trouble
trying to interpret something like e c e ges bes d as C9b5/E
because it can't read the intent of the user, only the notes in the
bracket about which it can only make its best guess. It would
probably come up with Em7b5sus4 or something which is not the same
thing in terms of musical intent, and musical intent is what the
musician playing the piece wants to know.
I think I understood your intent. The problem is that the *only* way we
have to input chords is in formats that enter notes (either e c' e ges bes
d or \chordmode {c:9.5-/e}). There is *no* facility in LilyPond for
entering chords as text.
The parsing of c:9.5-/e converts that string into a set of pitches, along
with a bass and an inversion (at least I think it does; I haven't reviewed
it carefully for a while, and when I did review it I wasn't as familiar with
LilyPond as I am now).
The project that Thomas is working on is making sure that when the output of
\chordmode{c:9.5-/e} is passed to the chordnames context, it will give bag
c9b5/E in the appropriate format.
I would recommend requiring the user to write the chord names out in
a text entry format (e.g., c1:9.5-/e or something like that) *if*
they want chord names above the staff and not parsing note entry to
get chord names (if indeed LilyPond can do this at all, I've never
looked into it). This makes the most sense to me (and I hope my
intent is clearer).
Right now, the ChordNames context works much better with chords entered in
\chordmode, because it knows the root and the inversion, rather than having
to try to guess the chord.
I suspect that there won't be a lot of effort right now trying to deal with
inversions or added basses, but that may come in the future.
In my opinion, the biggest problem we currently have is that we don't always
get good chord names out of \chordmode chords. But I think Thomas will have
that fixed shortly
How far is this guys?
\r
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On Fri, Jul 10, 2009 at 2:41 AM, Graham Percivalgra...@percival-music.ca wrote: On Fri, Jul 10, 2009 at 11:37:15AM +0200, Valentin Villenave wrote: 2009/7/10 Graham Percival gra...@percival-music.ca: There's now an Examples section, thanks to Jonathan Kulp. - currently, most examples have a click-to-expand thing. Some of them don't work expanded, others don't work non-expanded. But there's enough working stuff for you to get the idea. Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ No javascript. Besides, the display isn't the issue; what's at issue is generating the images in an automatic, system-independent way. (as in not what's in the current makefile and examples/ dir) Well, we're already using (very simple) JavaScript to clear the search box upon focus, so I think this is okay. And I know we want Reinhold's AJAX search box for the docs, and that also involves scripting... Valentin, I've never used jquery before, but if you can implement this, and the site is still functional with scripting *disabled*, then I think we should definitely use it. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On Fri, Jul 10, 2009 at 2:37 AM, Valentin Villenavev.villen...@gmail.com wrote: I am probably familiar enough with the texinfo and CSS syntax to give you guys a hand. For instance, I should be able to handle the blinking Help wanted boxes (this looks sooo 1996 btw). :-) Yeah, that was intentional. The sub(sub)menus are still a little bit confusing (for instance when you click on manuals). But I think this is just a look-and-feel issue, not a structural problem. Yes, I'm out of ideas for submenu look and feel. When you look at the CSS, you'll see that the submenus are painstakingly positioned. A change for one position value or dimension value might throw the entire placement off, or might disrupt cross-browser compatibility. So, be careful! :-) If you can find better colors for the boxes and submenu that would be great. As you can tell, the idea is to link the colors of the boxes to the appropriate piece of the submenu, as well as to create *contrast* between the boxes. But the color scheme should still blend, IMO. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Graham Percival wrote:
I'll volunteer for css and/or proofreading. I also don't have a job or
girlfriend;) I'll be in Peru much of August though and looking for a
job after that. Put me to work. (Although I'll have to confess, as far
as css goes, the current new stuff is looking great already!)
Patrick
http://percival-music.ca/blogfiles/out/lilypond-general_1.html
There's now an Examples section, thanks to Jonathan Kulp.
- currently, most examples have a click-to-expand thing. Some
of them don't work expanded, others don't work non-expanded.
But there's enough working stuff for you to get the idea.
IS THIS WORTH IT? Making it work nicely in small+expanded
versions is turning out to be a pain. I'm wondering if we
should just stick to small examples, which are approximately
infinitely times easier to create/modify/regenerate.
More importantly, we need help. I recently re-iterated my claim
that the lilypond community should have the
program/bugs/documentation/website they deserve, but currently
this isn't happening -- Patrick and I have spent a ton of time and
effort on this website.
- Patrick wants to spend time programming lilypond. I also want
him to spend time programming. He's doing nifty stuff like
fixing the SVG output, fixing misc bugs, and cleaning up a ton
of advanced documentation.
WE NEED A NEW CSS PERSON.
- I'm wasting a lot of time on mundane jobs. For example, the old
news page needs to be put into the new website source. This
means going through a bunch of things like
h2New German translaton! Aug 07, 2006/h2
pIch nein katza, a href=http://blah;auf blitzen/a drie./p
and turning it into
@subheading New German Translation! 2006 Aug 07
Ich nein katza, @uref{http://blah, auf blitzen} drie.
Not hard. I could even train an undergraduate to do this job!
WE NEED SOMEBODY TO WRITE TEXT.
- I tend to rewrite / reword sentences as I work on them, but I
have a nasty habit of not reading the once I erase stuff and
write new material. The result is by native English speakers,
although it may slightly confusing. Not what we in a shiny
new website, that's for certain!
(also, many sentences on the website could be rewritten to
reduce the words, reduce the complexity -- remember, we have
a fair chunk of non-native English readers, so let's not
elaborate our missives with loquatious (sp) verbitage)
WE NEED SOMEBODY TO PROOFREAD TEXT.
- Some of the examples could be improved... fancier formatting,
adding more text to the theory example, etc.
WE NEED SOMEBODY TO WORK ON .LY FILES.
Now, I'm *completely* capable of doing any of those tasks (even
self-proofreading, once I get into the mood)... but
a) I don't think I should be doing so much work on this, and
b) if somebody does those jobs, I can tackle harder stuff.
I'm *really* not doing much this summer other than lilypond -- I
have no job, no studies, no girlfriend -- so it's mainly a
question of what parts of lilypond do I work on, not will I
work on something. So, just like we all benefit from having
Patrick *not* working on CSS stuff, I think we would all benefit
from me *not* working on the website so much.
Cheers,
-Graham
___
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: minor chord names
On 7/10/09 11:17 AM, fiëé visuëlle fiee.visue...@gmx.net wrote:
Hello pond comrades,
some time ago I asked about displaying minor chord names as lowercase
letters without the m modifier, as it is common (at least) in German
folk songbooks.
I.e.
\context ChordNames {
\germanChords % or whatever
\chordmode { a:m }
}
should print as a instead of Am.
Is this possible nowadays, and how?
As far as I know, it is not yet possible. It is on a feature request list
for Thomas's rewrite of the chord naming functions.
There's nothing appropriate in
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-chords
Since I don't need fancy jazz chords, perhaps there's a possibility
using chordNameExceptions?
Unfortunately, there is no built-in way of doing it that I know about.
As written, chordNameExceptions modifies everything that comes after the
root name, but not the root name itself.
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: LilyPondTool 2.12.858 Release Candidate
It contains some enhancements and many fixes, especially for the PDF viewer I like the button to adapt the zoom to the page width. Very usefull. Now you can turn the page back and not just forward for example :) yes it works. Thank you ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: basic questions
Mark Polesky wrote: That is very odd to my eye. It looks like a \cadenzaOn bug, but I've learned to be very hesitant in calling something a bug. I'll look into it. Not a bug. You need to insert \bar at appropriate places. See: http://lilypond.org/doc/v2.13/Documentation/user/lilypond/Displaying-rhythms#Known-issues-and-warnings-45 Also, get rid of the spacer rest -- it only makes it worse. You might need to readjust line-width, too, but I don't know what your needs are. HTH. - Mark ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Great! Install git, and then follow the instructions here:
http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00348.html
More git instructions here (just follow the above email for the
getting the source code)
http://lilypond.org/doc/v2.13/Documentation/devel/contrib-guide/index
Once you have the source, look in texinfo/*.texi and
texinfo/css/lilypond-general.css
Find some typo, or misspelling, or rewrite some sentence or
whatever, then send me a patch. (instructions in the CG)
(an absolutely trivial patch is fine; the important thing right
now is just to get used to git and sending patches)
Cheers,
- Graham
On Fri, Jul 10, 2009 at 12:49:01PM -0700, Patrick Horgan wrote:
Graham Percival wrote:
I'll volunteer for css and/or proofreading. I also don't have a job or
girlfriend;) I'll be in Peru much of August though and looking for a
job after that. Put me to work. (Although I'll have to confess, as far
as css goes, the current new stuff is looking great already!)
Patrick
http://percival-music.ca/blogfiles/out/lilypond-general_1.html
There's now an Examples section, thanks to Jonathan Kulp.
- currently, most examples have a click-to-expand thing. Some
of them don't work expanded, others don't work non-expanded.
But there's enough working stuff for you to get the idea.
IS THIS WORTH IT? Making it work nicely in small+expanded
versions is turning out to be a pain. I'm wondering if we
should just stick to small examples, which are approximately
infinitely times easier to create/modify/regenerate.
More importantly, we need help. I recently re-iterated my claim
that the lilypond community should have the
program/bugs/documentation/website they deserve, but currently
this isn't happening -- Patrick and I have spent a ton of time and
effort on this website.
- Patrick wants to spend time programming lilypond. I also want
him to spend time programming. He's doing nifty stuff like
fixing the SVG output, fixing misc bugs, and cleaning up a ton
of advanced documentation.
WE NEED A NEW CSS PERSON.
- I'm wasting a lot of time on mundane jobs. For example, the old
news page needs to be put into the new website source. This
means going through a bunch of things like
h2New German translaton! Aug 07, 2006/h2
pIch nein katza, a href=http://blah;auf blitzen/a drie./p
and turning it into
@subheading New German Translation! 2006 Aug 07
Ich nein katza, @uref{http://blah, auf blitzen} drie.
Not hard. I could even train an undergraduate to do this job!
WE NEED SOMEBODY TO WRITE TEXT.
- I tend to rewrite / reword sentences as I work on them, but I
have a nasty habit of not reading the once I erase stuff and
write new material. The result is by native English speakers,
although it may slightly confusing. Not what we in a shiny
new website, that's for certain!
(also, many sentences on the website could be rewritten to
reduce the words, reduce the complexity -- remember, we have
a fair chunk of non-native English readers, so let's not
elaborate our missives with loquatious (sp) verbitage)
WE NEED SOMEBODY TO PROOFREAD TEXT.
- Some of the examples could be improved... fancier formatting,
adding more text to the theory example, etc.
WE NEED SOMEBODY TO WORK ON .LY FILES.
Now, I'm *completely* capable of doing any of those tasks (even
self-proofreading, once I get into the mood)... but
a) I don't think I should be doing so much work on this, and
b) if somebody does those jobs, I can tackle harder stuff.
I'm *really* not doing much this summer other than lilypond -- I
have no job, no studies, no girlfriend -- so it's mainly a
question of what parts of lilypond do I work on, not will I
work on something. So, just like we all benefit from having
Patrick *not* working on CSS stuff, I think we would all benefit
from me *not* working on the website so much.
Cheers,
-Graham
___
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: basic questions
2009/7/10 Mark Polesky markpole...@yahoo.com: Also, get rid of the spacer rest -- it only makes it worse. You might need to readjust line-width, too, but I don't know what your needs are. If adjusting line-width isn't an option, packed spacing might help: \override Score.SpacingSpanner #'packed-spacing = ##t Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: minor chord names
Am 2009-07-10 um 22:06 schrieb Carl Sorensen: Is this possible nowadays, and how? As far as I know, it is not yet possible. It is on a feature request list for Thomas's rewrite of the chord naming functions. Thank you, then I must still wait - I hope it will work in september, since I'll do a big songbook then and have to comply with the publisher's standards. Can I speed it up with some money? Greetlings from Lake Constance --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
On Fri, Jul 10, 2009 at 12:21:17PM -0700, Patrick McCarty wrote: On Fri, Jul 10, 2009 at 2:41 AM, Graham Percivalgra...@percival-music.ca wrote: Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ No javascript. Besides, the display isn't the issue; what's at issue is generating the images in an automatic, system-independent way. (as in not what's in the current makefile and examples/ dir) Valentin, I've never used jquery before, but if you can implement this, and the site is still functional with scripting *disabled*, then I think we should definitely use it. Ok, but the important questions still remain: 1. Do we want to display *different* images after a click, or just *expanded* images? 2. Is this an important feature? (if so, we can't use javascript) 3. Who's going to create the .ly files, write the makefile, etc? If the first two answers are no, no, then I'll do the third. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Graham Percival wrote: On Fri, Jul 10, 2009 at 12:21:17PM -0700, Patrick McCarty wrote: On Fri, Jul 10, 2009 at 2:41 AM, Graham Percivalgra...@percival-music.ca wrote: Although I'm not fond of JavaScript, I think the solution here is called thickbox: http://jquery.com/demo/thickbox/ No javascript. Besides, the display isn't the issue; what's at issue is generating the images in an automatic, system-independent way. (as in not what's in the current makefile and examples/ dir) Valentin, I've never used jquery before, but if you can implement this, and the site is still functional with scripting *disabled*, then I think we should definitely use it. Ok, but the important questions still remain: 1. Do we want to display *different* images after a click, or just *expanded* images? I vote for expanded images, not different ones, just so people can see them at a higher resolution and see how nice they look. 2. Is this an important feature? (if so, we can't use javascript) 3. Who's going to create the .ly files, write the makefile, etc? If the first two answers are no, no, then I'll do the third. Cheers, - Graham -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: difficulty implementing grob-suicide! for spanned bendAfter
2009/7/10 Mike Solomon mike...@ufl.edu:
\relative c'' { \override Voice . BendAfter #'after-line-break = #(lambda
This override doesn't work because the property's called
after-line-breaking. You don't get any warning since LilyPond
(deliberately) does no type checks for grob properties which are set
to procedures or closures.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: minor chord names
On 7/10/09 4:17 PM, fiëé visuëlle fiee.visue...@gmx.net wrote: Am 2009-07-10 um 22:06 schrieb Carl Sorensen: Is this possible nowadays, and how? As far as I know, it is not yet possible. It is on a feature request list for Thomas's rewrite of the chord naming functions. Thank you, then I must still wait - I hope it will work in september, since I'll do a big songbook then and have to comply with the publisher's standards. Can I speed it up with some money? You might ask this question to Thomas Morgan, who is working on the ChordNames stuff. I'm copying this reply to him. Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Criminy on a crutch, wow. I'm sorry to say it but there are an awful lot of hurdles to get over in learning to use LilyPond and then even more in trying to contribute to it. I think I see why there are fewer contributor than Graham and Patrick etc. would like: being a contributor comes with a learning curve that many of us just do not have time to master. I think there'd be more contributors if contributing was a simple process (and not so Linux-centric): installing git and all its myriad dependencies, learning texinfo, etc. I simply don't have time for all that. I'm happy to write text, revise text, proof-read etc. for the Web site and the docs, but I'd submit anything in text or HTML. On Jul 10, 2009, at 4:06 PM, Graham Percival wrote: Great! Install git, and then follow the instructions here: http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00348.html More git instructions here (just follow the above email for the getting the source code) http://lilypond.org/doc/v2.13/Documentation/devel/contrib-guide/index Once you have the source, look in texinfo/*.texi and texinfo/css/lilypond-general.css Find some typo, or misspelling, or rewrite some sentence or whatever, then send me a patch. (instructions in the CG) (an absolutely trivial patch is fine; the important thing right now is just to get used to git and sending patches) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
2009/7/11 Tim McNamara tim...@bitstream.net: I think there'd be more contributors if contributing was a simple process (and not so Linux-centric): installing git and all its myriad dependencies, learning texinfo, etc. I simply don't have time for all that. I'm happy to write text, revise text, proof-read etc. for the Web site and the docs, but I'd submit anything in text or HTML. I understand your point, as I feel a lot of potential translators have been scared away because of this, but there is nothing much we can do until we manage to test, install and develop web interfaces to the version control system that offer file editing and submission facilities for people that can't or don't want to learn using command-line tools or fetch all the sources. Best, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: difficulty implementing grob-suicide! for spanned bendAfter
That does the trick - works like a charm now. Thank you!
~Mike
On 7/10/09 6:43 PM, Neil Puttock n.putt...@gmail.com wrote:
2009/7/10 Mike Solomon mike...@ufl.edu:
\relative c'' { \override Voice . BendAfter #'after-line-break = #(lambda
This override doesn't work because the property's called
after-line-breaking. You don't get any warning since LilyPond
(deliberately) does no type checks for grob properties which are set
to procedures or closures.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
Tim McNamara wrote: Criminy on a crutch, wow. I'm sorry to say it but there are an awful lot of hurdles to get over in learning to use LilyPond and then even more in trying to contribute to it. I think I see why there are fewer contributor than Graham and Patrick etc. would like: being a contributor comes with a learning curve that many of us just do not have time to master. I think there'd be more contributors if contributing was a simple process (and not so Linux-centric): installing git and all its myriad dependencies, learning texinfo, etc. I simply don't have time for all that. I'm happy to write text, revise text, proof-read etc. for the Web site and the docs, but I'd submit anything in text or HTML. I'm happy to format stuff as texinfo for you if you want to write text for the website, for example the inspirational essay why to use Lilypond that (I think) we're still looking for, or if you want to revise text in the docs, call our attention to typos and so forth. If someone comes along as says exactly where there's a problem in the docs and provides (even in an email) an exact line with which to replace it, then to me that's a significant contribution and I'm happy to integrate it to the docs. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
hurdles for contributors (was: help wanted, I mean it)
On Fri, Jul 10, 2009 at 05:50:54PM -0500, Tim McNamara wrote: I'm sorry to say it but there are an awful lot of hurdles to get over in learning to use LilyPond and then even more in trying to contribute to it. I think I see why there are fewer contributor than Graham and Patrick etc. would like: being a contributor comes with a learning curve that many of us just do not have time to master. I think there'd be more contributors if contributing was a simple process (and not so Linux-centric): installing git and all its myriad dependencies, learning texinfo, etc. I simply don't have time for all that. I'm happy to write text, revise text, proof-read etc. for the Web site and the docs, but I'd submit anything in text or HTML. I've bitterly cursed the move to git ever since it happened. :( I don't mind asking contributors to learn a bit of texinfo, since 95% of the time, they don't need to actually use any texinfo commands; they can just edit the text in the file. And, as Jonathan pointed out, the most important thing is the plain text; some people (like him) are willing to add any special texinfo formatting required. During GDP, I didn't require people to use git; I provided them with texinfo source files. They edited the files (again, mostly just the text, while ignoring the special commands), then I took care of the git side. It wasn't _too_ much work, although I wouldn't want to be doing it on a regular basis. But if there was a limited-time X-month project, I might do it again. Trevor Daniels might have an interesting opinion on this; he's another retired British windows user, who started off during GDP (and has said on multiple occasions that he would have never started contributing if he had to use git). Now he's on git (he wrote the git on windows section. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new website draft 5: help wanted, I mean it
2009/7/10 Patrick McCarty pnor...@gmail.com: If you can find better colors for the boxes and submenu that would be great. As you can tell, the idea is to link the colors of the boxes to the appropriate piece of the submenu, as well as to create *contrast* between the boxes. But the color scheme should still blend, IMO. To achieve some contrast between two colours only, it's prettier if a colour made darker is not only value- or saturation- decreased, but also hue-darkened. For example, a darker green should be also a bit more 'blue'. Otherwise it just looks 'dirty'. For three colours is better to keep the hue fixed. I'm not that sensitive to hues, but that's what I've heard. -- Francisco Vila. Badajoz (Spain) www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: hurdles for contributors (was: help wanted, I mean it)
2009/7/11 Graham Percival gra...@percival-music.ca: I've bitterly cursed the move to git ever since it happened. :( I don't mind asking contributors to learn a bit of texinfo, since 95% of the time, they don't need to actually use any texinfo commands; they can just edit the text in the file. And, as Jonathan pointed out, the most important thing is the plain text; some people (like him) are willing to add any special texinfo formatting required. During GDP, I didn't require people to use git; I provided them with texinfo source files. They edited the files (again, mostly just the text, while ignoring the special commands), then I took care of the git side. It wasn't _too_ much work, although I wouldn't want to be doing it on a regular basis. But if there was a limited-time X-month project, I might do it again. Trevor Daniels might have an interesting opinion on this; he's another retired British windows user, who started off during GDP (and has said on multiple occasions that he would have never started contributing if he had to use git). Now he's on git (he wrote the git on windows section. When I started translating, John and you made me to learn git, it was a requisite IIRC, now I can use git progressively a bit better, and I use it for my own private projects. I recommend it to all contributors; for the project it's something like those fidelity cards on the supermarkets: once you get stuck, it's difficult to move away. -- Francisco Vila. Badajoz (Spain) www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
