Re: How to do this correctly?
Carl Sorensen c_soren...@byu.edu writes: On 1/28/10 12:49 PM, David Kastrup d...@gnu.org wrote: Carl Sorensen c_soren...@byu.edu writes: On 1/28/10 7:25 AM, David Kastrup d...@gnu.org wrote: Anyway, I think that likely the ambitus engraver would be a good candidate for reimplementing as a Scheme engraver. It would appear reasonably straightforward but not trivially so, and it is one of those things where augmenting the _code_ and behavior is likely to be better extensible in Scheme. I think it would be difficult to implement as a Scheme engraver, because there need to be variables stored as part of the context that are modified by different event handlers. But I could be wrong. It wouldn't be the first time and is not likely to be the last. If you aren't wrong know, I hope you'll become so in future. I think that all the interactions of a standard engraver doing nothing out of the ordinary should be describable in terms of Scheme, even if the actual implementation might be C++ for performance reasons. Well, the ambitus engraver does do something out of the ordinary. It watches for all the notes, but doesn't create grobs for any of them. That's not unusual. Everything that needs to comprehend some passage of music (for example, chord namers) does that, and might create grobs in a different context. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH]: New G clef
Mats Bengtsson schrieb: Marc Hohl wrote: Is it ok to do just cd mf/ make clean cd .. make all since this is faster? Sure! You may save some typing by doing make -C mf clean make Cool, didn't know about this. Thanks Marc /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Scheme Engraver - Removing Engravers
On Thursday, January 28, 2010, Carl Sorensen c_soren...@byu.edu wrote: Two points. First, policy is that we don't top post on this list. You'll be received better if you avoid top posting. I hope you view this as a gentle reminder; it's intended to be that. Thanks for understanding. Thanks for letting me know about this. I used be strongly against top posting and was quite vocal about it. I found that I was just alienating myself from newer Internet users who didn't know what I was talking about. It appears that this list is populated by a lot of long term Internet users and I'll happily stop top posting! Second, you don't need to write new contexts. You just need to define your contexts in a layout block. (See Notation Reference, 4.2.2). Then you'll define your StaffTab as a template, where your Staffs (by default) will include the new Scheme engravers that you've written, and remove the New_fingering_engraver. I'll check this out this morning, thanks. -Eric ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Thanks for letting me know about this. I used be strongly against top posting and was quite vocal about it. I found that I was just alienating myself from newer Internet users who didn't know what I was talking about. It appears that this list is populated by a lot of long term Internet users and I'll happily stop top posting! I usually read my email on a mobile connection using a 120x176 px mobile phone, and bottom posting means extra traffic and extra scrolling. For a longer discussion I usually don't care about history, only the latest events and thoughts, so for me please do top post. ;) Thanks, Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Am Freitag, 29. Januar 2010 15:27:55 schrieb Bertalan Fodor (LilyPondTool): I usually read my email on a mobile connection using a 120x176 px mobile phone, and bottom posting means extra traffic and extra scrolling. For a longer discussion I usually don't care about history, only the latest events and thoughts, so for me please do top post. ;) I think you don't understand what top posting means: It means that you quote the whole message (and all messages that it quoted) and simply add your reply at the top. This way, each mail contains the whole history! What you are asking for is to delete all irrelvant parts of the message you answer to and leave only the relevant parts in it. That's not top-posting, though. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
I think you don't understand what top posting means: It means that you quote the whole message (and all messages that it quoted) and simply add your reply at the top. This way, each mail contains the whole history! I wanted to say that I prefer that to quote the whole message and simply add your reply at the bottom. What you are asking for is to delete all irrelvant parts of the message you answer to and leave only the relevant parts in it. That's not top-posting, though. No, I'm asking that the relevant parts be at the top of the message as much as possible, to prevent unnecessary network traffic and scrolling. But honestly, my ultimate idea is freedom (that's why I'm here): everyone do what she feels effective. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Bertalan Fodor (LilyPondTool) lilypondt...@organum.hu writes: Thanks for letting me know about this. I used be strongly against top posting and was quite vocal about it. I usually read my email on a mobile connection using a 120x176 px mobile phone, and bottom posting means extra traffic and extra scrolling. Wrong. It means that only if people don't reduce the quoted context to the parts required for establishing the context. But we are not talking about what kind of inappropriate behavior we like better. The question is what _appropriate_ behavior we want. Unabridged posts remain available separately courtesy to your newsreading software and cross-reference headers. There is no need to quote unabridged either top or bottom. For a longer discussion I usually don't care about history, Nobody cares about that. Instead, context is what is required. As a rule of thumb, write the majority of your postings yourself, and don't let them consist primarily of stale and irrelevant history. only the latest events and thoughts, so for me please do top post. ;) I have seen people top posting above daily digests. Of course, if that happens every day, not even a broadband connection will be able to keep up after a few weeks. The main rule is: don't post irrelevant quoted garbage. Not at top, not at bottom. And if what you post is not garbage but judiciously picked context, the logical reading order for a developing thought in context is top to bottom. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Bertalan Fodor (LilyPondTool) lilypondt...@organum.hu writes: But honestly, my ultimate idea is freedom (that's why I'm here): everyone do what she feels effective. That's not freedom but chaos. There is nothing wrong with conventions and agreements as long as they don't take on a life of their own and become more important than their purpose. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Hi, On Fri, 29 Jan 2010, Bertalan Fodor (LilyPondTool) wrote: [do not know who said that, Bertalan removed that information] I think you don't understand what top posting means: It means that you quote the whole message (and all messages that it quoted) and simply add your reply at the top. This way, each mail contains the whole history! I wanted to say that I prefer that to quote the whole message and simply add your reply at the bottom. That is not top-posting. But frankly, please do not discourage anyone from top-posting. This would deprive me of a valuable indicator to sort my emails. I get 200+ emails a day, some of which do not even land in my inbox (some people are culled by my killfile, I think there is even one on this list), and I have to have a way to sort out those who are clueful enough that I should spend (the time I have to answer mails) on them. Top-posting is a _perfect_ way to lable those who are not in that group. I just cannot read every mail I get. Please, do not deprive me of that indicator. Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: top posting
Op vrijdag 29-01-2010 om 20:55 uur [tijdzone +0100], schreef Johannes Schindelin: I wanted to say that I prefer that to quote the whole message and simply add your reply at the bottom. That is not top-posting. Right, but just as clueless and just as valid as an indicator of the usefulness of the content. But, indeed, don't tell anyone we're not reading those messages. Greetings, Jan. -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
[patch] doc cleanup that touches translations
Does anybody know if I can push this patch? It removes
Documentation/included/divisiones.ly and puts that info in the
main .itely files.
I started going in circles and getting lost while trying to figure
out if I was supposed to use git pull or change the comment at the
top or whatever.
Cheers,
- Graham
From b51656614f8e76da5912ffd6ce1377f7a95f1fb4 Mon Sep 17 00:00:00 2001
From: Graham Percival gra...@percival-music.ca
Date: Sat, 30 Jan 2010 00:02:46 +
Subject: [PATCH] Doc: move divisiones.ly into Ancient.
Translations: I did the same thing here to retain compiling;
hopefully this doesn't break anything. AFAIK nobody has touched
the translations of Ancient in years.
---
Documentation/de/notation/ancient.itely | 31 ++-
Documentation/es/notation/ancient.itely | 31 ++-
Documentation/fr/notation/ancient.itely | 32 ++-
Documentation/included/divisiones.ly| 42 ---
Documentation/notation/ancient.itely| 31 ++-
5 files changed, 121 insertions(+), 46 deletions(-)
delete mode 100644 Documentation/included/divisiones.ly
diff --git a/Documentation/de/notation/ancient.itely b/Documentation/de/notation/ancient.itely
index 4999627..b2ac2d9 100644
--- a/Documentation/de/notation/ancient.itely
+++ b/Documentation/de/notation/ancient.itely
@@ -1247,7 +1247,36 @@ entsprechenden Stellen zu schreiben. Einige Editionen verwenden eine
sich in der Datei @file{gregorian@/-init@/.ly} auch eine Definition für
@code{\virgula} und @code{\caesura}.
-...@lilypondfile[quote,ragged-right]{divisiones.ly}
+...@lilypond[quote,ragged-right]
+\include gregorian.ly
+\score {
+
+\context VaticanaVoice {
+ \override TextScript #'padding = #3
+ g a g
+ s^\markup { divisio minima }
+ \divisioMinima
+ g a g
+ s^\markup { divisio maior }
+ \divisioMaior
+ g a g
+ s^\markup { divisio maxima }
+ \divisioMaxima
+ \break
+ g a g
+ s^\markup { finalis }
+ \finalis
+ g a g
+ s^\markup { virgula }
+ \virgula
+ g a g
+ s^\markup { caesura }
+ \caesura
+ g a g
+}
+
+}
+...@end lilypond
@funindex \virgula
@funindex \caesura
diff --git a/Documentation/es/notation/ancient.itely b/Documentation/es/notation/ancient.itely
index 357aa6a..da40193 100644
--- a/Documentation/es/notation/ancient.itely
+++ b/Documentation/es/notation/ancient.itely
@@ -1257,7 +1257,36 @@ ediciones usan @emph{virgula} o @emph{caesura} en vez de divisio
minima. Por ello, @file{gregorian@/.ly} define también las
instrucciones @code{\virgula} y @code{\caesura}.
-...@lilypondfile[quote,ragged-right]{divisiones.ly}
+...@lilypond[quote,ragged-right]
+\include gregorian.ly
+\score {
+
+\context VaticanaVoice {
+ \override TextScript #'padding = #3
+ g a g
+ s^\markup { divisio minima }
+ \divisioMinima
+ g a g
+ s^\markup { divisio maior }
+ \divisioMaior
+ g a g
+ s^\markup { divisio maxima }
+ \divisioMaxima
+ \break
+ g a g
+ s^\markup { finalis }
+ \finalis
+ g a g
+ s^\markup { virgula }
+ \virgula
+ g a g
+ s^\markup { caesura }
+ \caesura
+ g a g
+}
+
+}
+...@end lilypond
@predefined
diff --git a/Documentation/fr/notation/ancient.itely b/Documentation/fr/notation/ancient.itely
index cce6eb3..ef51166 100644
--- a/Documentation/fr/notation/ancient.itely
+++ b/Documentation/fr/notation/ancient.itely
@@ -847,7 +847,37 @@ Les divisions sont disponibles après inclusion du fichier
pourquoi @file{gregorian@/-init@/.ly} définit aussi @code{\virgula} et
@code{\caesura}.
-...@lilypondfile[quote,ragged-right]{divisiones.ly}
+...@lilypond[quote,ragged-right]
+\include gregorian.ly
+\score {
+
+\context VaticanaVoice {
+ \override TextScript #'padding = #3
+ g a g
+ s^\markup { divisio minima }
+ \divisioMinima
+ g a g
+ s^\markup { divisio maior }
+ \divisioMaior
+ g a g
+ s^\markup { divisio maxima }
+ \divisioMaxima
+ \break
+ g a g
+ s^\markup { finalis }
+ \finalis
+ g a g
+ s^\markup { virgula }
+ \virgula
+ g a g
+ s^\markup { caesura }
+ \caesura
+ g a g
+}
+
+}
+...@end lilypond
+
@predefined
diff --git a/Documentation/included/divisiones.ly b/Documentation/included/divisiones.ly
deleted file mode 100644
index 6307c9a..000
--- a/Documentation/included/divisiones.ly
+++ /dev/null
@@ -1,42 +0,0 @@
-% possible rename to ancient- or gregorian- ?
-\header {
-texidoc = @cindex Divisiones
-
-Divisiones are ancient variants of breathing signs.
-Choices are @code{divisioMinima}, @code{divisioMaior},
-...@code{divisiomaxima} and @code{finalis}, @code{virgula} and
-...@code{caesura}.
-
- }
-
-\version 2.12.0
-
-\include gregorian.ly
-
-\score {
-
-\context VaticanaVoice {
-
Re: [patch] doc cleanup that touches translations
On Fri, Jan 29, 2010 at 05:47:03PM -0700, Carl Sorensen wrote: On 1/29/10 5:15 PM, Graham Percival gra...@percival-music.ca wrote: Does anybody know if I can push this patch? It removes Documentation/included/divisiones.ly and puts that info in the main .itely files. Looks good to me. Thanks, pushed. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
