Re: Is Anthony Fok <[EMAIL PROTECTED]> MIA?
Pedro Kröger wrote: Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: Ok, adoption in progress. that's very good to hear! it's nice to know that debian will have up-to-date lilypond versions again. Yes!! Please consider my request to rename the existing lilypond-snapshot packages to plain lilypond so 2.4.2 will be available for production work until 2.5.whatever is fully ready. As far as I am concerned your current lilypond-snapshot could be Debian's sid version replacing whatever Anthony's last version was. If I can help please let me know. I have considered becoming a DD. Maybe I could do the renaming I was requesting. Thanks again for all your work on the Debian packages, Paul Scott ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is Anthony Fok <[EMAIL PROTECTED]> MIA?
[sorry If I took too long to answer this, it's the beginning of the semester over here (I'm a teacher) and I've been preparing classes and expending more time in the classroom than in front of the computer. plus, I'm finishing a big concerto for percussion and orchestra that is taking lots of my time!] Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > Ok, adoption in progress. Would the lilypond people please point me > to the official web pages and subscription information for the > relevant mailing lists I should be on? that's very good to hear! it's nice to know that debian will have up-to-date lilypond versions again. Cheers, Pedro ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is Anthony Fok <[EMAIL PROTECTED]> MIA?
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: >>> We are a bit concerned with old LilyPond packages, and a potential >>> new maintainer (Pedro Kroger) with his sponsor going mia. >> >> Who was going to sponsor him? > > I don't think Pedro told me that. Pedro? actually he was going to sponsor another lilypond-unrelated package, but was willing to sponsor another packages (like lilypond-snapshot) as well. Pedro ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog mf/feta-klef.mf mf/feta-ma...
> The downstroke of change clef becomes thinner between the top loop > and the downstroke. I've moved some points slightly; it should be better now. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Point-and-click data and backend futures
Hi all, As some of you might have seen on the lilypond-user list, I'm working on a Mac OS X integrated text editor/previewer for LilyPond. Several users have asked for point-and-click support, and I'd like it too. So, a couple clusters of questions on this topic: (1) As I understand it, the data mapping between layout coordinates and line/column numbers in the source code is already embedded in the DVI output. I know nothing about DVI--can anyone point me to a reference for getting at this data? Is this the best way to get the data? And since I'm actually displaying PDF in the app, not DVI, will these coordinates match the coordinates in the PDF output exactly? (2) I've seen things here and there in the archives about the various backends--PS, TeX, GNOME, etc.--and wanted to know how the future of these backends might affect point-and-click in my previewer, or, to be more open-ended, how it might affect the design of the previewer in any way. Will the DVI point-and-click data continue to be available? Should I be designing my previewer to display something other than PDF? Etc. Lastly: any objections around here to me calling the app LilyPad? Thanks much, Ed ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Speed Test Results of Lilypond on Windows (Cygwin and coLinux)
Hi, I setup a simple test to see how to lilypond takes to complete operating on a file, on cygwin compared to on colinux. Platform this test is ran on is on a PIII 800MHz, 359MB ram, running Windows 2k. Cygwin is installed selecting the Lilypond 2.4.2-1 package. coLinux (0.6.2) runs the Debian-3.0r2.ext3-mit-backports.1gb image, and installed a stable Lilypond 2.4.2. Lilypond is ran using the coLinux shell, not under X. The following tests files were taken from mutopiaproject intermezzo.ly - http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=535 bwv851a.ly - http://www.mutopiaproject.org/ftp/BachJS/BWV851/bwv851a/bwv851a.ly enchanted-island.ly - http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=536 op149-19.ly -http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=533 A script was use to run the test. # script start (run.sh) date > log.txt lilypond file.ly date >> log.txt # script end Time when lilypond starts and ends is recorded in the log file. Here are the results. 1. intermezzo.ly cygwin: start: Tue Mar 15 16:33:45 MPST 2005 end: Tue Mar 15 16:36:43 MPST 2005 elapse: 2:58 colinux: start: Tue Mar 15 16:41:41 HKT 2005 end: Tue Mar 15 16:42:49 HKT 2005 elapse: 1:07 2. bwv851a.ly cygwin: start: Tue Mar 15 16:46:41 MPST 2005 end: Tue Mar 15 16:47:43 MPST 2005 elapse: 1:02 colinux: start: Tue Mar 15 16:51:56 HKT 2005 end: Tue Mar 15 16:52:18 HKT 2005 elapse: 0:22 3. enchanted-island.ly cygwin: start: Tue Mar 15 17:07:10 MPST 2005 end: Tue Mar 15 17:07:34 MPST 2005 elapse: 0:24 colinux: start: Tue Mar 15 17:10:05 HKT 2005 end: Tue Mar 15 17:10:35 HKT 2005 elapse: 0:30 4. op149-19.ly cygwin: start: Tue Mar 15 17:14:50 MPST 2005 end: Tue Mar 15 17:15:44 MPST 2005 elapse: 0:54 colinux: start: Tue Mar 15 16:41:41 HKT 2005 end: Tue Mar 15 16:42:49 HKT 2005 elapse: 1:08 cygwin total: 5:18 colinux total: 3:07 Conclusion and Comments. Lilypond in Colinux does seems to run faster than in Cygwin. Statistically, lilypond in colinux runs 42% faster than cygwin (although some runs are faster in cygwin). Of course, the sample data is too little, and my test could be inaccurate in many ways. Another interesting factor is the time to get into the shell. for cygwin bash shell, i took about 4s to load. for colinux, i took about 12s (plus u need to login with your username and password). An werid observation I saw, lilypond in cygwin will take about 20+Mb of ram. In colinux, it seems to use only about 5Mb of ram, although I allocated 192MB of memory to the guest machine. To the end of this test, I have no preferences to promote cygwin over colinux or vice-versa. coLinux have the flexiblity to run more like a linux os, but cygwin is much simpler to configure and install. Both have their pros and cons, so I leave it to the reader to try both and decide. I'm open to any comments, or any test results you might come up with. Joshua Koo ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: mensural notation: patch, question, plan
Hi Jürgen, Currently, the thickness property of the flexa shape aplies to all segments of the outline. IIUC, you are suggesting to apply the thickness property only to the left and right outline segment of the flexa shape, while hard-wiring the upper and lower segment wrt to the proportions in the .mf code for the brevis note head. I think this is somewhat inconsistent. If we really need different thicknesses for the vertical and horizontal segments, we may want to control this behavior with a separate property. That's fine with me. However, I just looked at a few facsimiles as well as contemporary educational works on mensural ligatures, and my impression is that all line segments roughly have the same thickness (unless the steepness is extremely high, in which case we may want to apply some thickness correction factor to the horizontal segments in order to compensate for optical illusion effects). Do you really think that the horizontal and vertical segments need to be controlled separately? Yes! Do you have facsimiles or contemporary works with noticeable difference between the thickness of the horizontal and vertical outline segments? Yes: I have facsimiles of about twenty masses from Petrucci prints and different codices (e.g. the Chigi codex; I don't know where the other facsimiles come from). There are at least three different scribes (i.e. script styles) I can distinguish. The horizontal lines of flexae are always like that of breves and not like the vertical ones (i.e. distinctly heavier). If you are interested, I'll try to make some scans. Pal Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol. Probald ki most! http://www.freestart.hu ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Followup on solved bug reports. Was: lilypond ./ChangeLog lily/new-fingering-engrave... [lilypond_2_4]
Han-Wen,
Another of all these quick bug fixes! Thanks for your hard work!
It would be great if you (and others who fix bugs in CVS) could also
send a reply to the original bug report that the problem has been fixed.
I seem to recall that you sent the same request to me and others some
years ago and that you also followed it yourself. I'm not sure if it's
time limitations or that you expect Erik to handle the official
responses to all bug reports that has changed these good habits.
This information is useful both for the user who wrote the bug report,
for people who search for information on the mailing list archives and
just see a large number of unanswered bug reports and for me and others
who try to provide relevant answers on the lists and documentation
updates, for example.
/Mats
Han-Wen Nienhuys wrote:
CVSROOT:/cvsroot/lilypond
Module name:lilypond
Branch: lilypond_2_4
Changes by: Han-Wen Nienhuys <[EMAIL PROTECTED]> 05/03/15 10:45:54
Modified files:
. : ChangeLog
lily : new-fingering-engraver.cc
stepmake/bin : add-html-footer.py
Log message:
(position_scripts): take priority
from head position. Backport.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?only_with_tag=lilypond_2_4&tr1=1.2780.2.32&tr2=1.2780.2.33&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/lily/new-fingering-engraver.cc.diff?only_with_tag=lilypond_2_4&tr1=1.42&tr2=1.42.2.1&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/stepmake/bin/add-html-footer.py.diff?only_with_tag=lilypond_2_4&tr1=1.28&tr2=1.28.2.1&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.2780.2.32 lilypond/ChangeLog:1.2780.2.33
--- lilypond/ChangeLog:1.2780.2.32 Mon Mar 14 21:05:32 2005
+++ lilypond/ChangeLog Tue Mar 15 10:45:53 2005
@@ -1,3 +1,8 @@
+2005-03-15 Han-Wen Nienhuys <[EMAIL PROTECTED]>
+
+ * lily/new-fingering-engraver.cc (position_scripts): take priority
+ from head position. Backport.
+
2005-03-14 Jan Nieuwenhuizen <[EMAIL PROTECTED]>
* make/ly-rules.make ($(outdir)/%.nexi): Remove old makeinfo
Index: lilypond/lily/new-fingering-engraver.cc
diff -u /dev/null lilypond/lily/new-fingering-engraver.cc:1.42.2.1
--- /dev/null Tue Mar 15 10:45:54 2005
+++ lilypond/lily/new-fingering-engraver.cc Tue Mar 15 10:45:54 2005
@@ -0,0 +1,336 @@
+/*
+ fingering-engraver.cc -- implement New_fingering_engraver
+
+ source file of the GNU LilyPond music typesetter
+
+ (c) 1998--2004 Han-Wen Nienhuys <[EMAIL PROTECTED]>
+
+ */
+
+#include "warn.hh"
+#include "engraver.hh"
+#include "side-position-interface.hh"
+#include "item.hh"
+#include "event.hh"
+#include "stem.hh"
+#include "rhythmic-head.hh"
+#include "self-alignment-interface.hh"
+#include "script-interface.hh"
+#include "stem.hh"
+
+struct Finger_tuple
+{
+ Grob *head_;
+ Grob *script_;
+ Music *note_event_;
+ Music *finger_event_;
+ bool follow_into_staff_;
+ int position_;
+
+ Finger_tuple ()
+ {
+position_ = 0;
+head_ = script_ = 0;
+note_event_ = finger_event_ = 0;
+follow_into_staff_ = false;
+ }
+ static int compare (Finger_tuple const & c1, Finger_tuple const & c2)
+ {
+return c1.position_- c2.position_;
+ }
+
+};
+
+class New_fingering_engraver : public Engraver
+{
+ Array fingerings_;
+ Array articulations_;
+ Link_array heads_;
+ Grob *stem_;
+
+public:
+ TRANSLATOR_DECLARATIONS (New_fingering_engraver);
+protected:
+ virtual void stop_translation_timestep ();
+ virtual void acknowledge_grob (Grob_info);
+ void add_fingering (Grob*, Music*,Music*);
+ void add_script (Grob*, Music*,Music*);
+ void position_scripts ();
+};
+
+void
+New_fingering_engraver::acknowledge_grob (Grob_info inf)
+{
+ if (Rhythmic_head::has_interface (inf.grob_))
+{
+ Music * note_ev =inf.music_cause ();
+ if (!note_ev)
+ return;
+
+ SCM arts = note_ev->get_property ("articulations");
+
+ for (SCM s = arts; scm_is_pair (s); s = scm_cdr (s))
+ {
+ Music * m = unsmob_music (scm_car (s));
+
+ if (!m)
+ continue;
+
+
+ if (m->is_mus_type ("fingering-event"))
+ {
+ add_fingering (inf.grob_ , m, note_ev);
+ }
+ else if (m->is_mus_type ("text-script-event"))
+ {
+ m->origin ()->warning ("Can not add text scripts to individual note heads");
+ }
+ else if (m->is_mus_type ("script-event"))
+ {
+ add_script (inf.grob_, m, note_ev);
+ }
+ else if (m->is_mus_type ("harmonic-event"))
+ {
+ inf.grob_->set_property ("style", ly_symbol2scm ("harmonic"));
+ Grob * d = unsmob_grob (inf.grob_->get_property ("dot"));
+ if (d)
+ d->suicide ();
+ }
+ }
+
+ heads_.push (inf.grob_);
+}
+ else if (Stem::has_interface (inf.grob_))
+{
+ stem_ = inf.grob_;
+}
+}
+
+void
+New_fingering_engraver::add_script (Grob * head,
+Music * event,
+
Re: comments on fixcc.py
Werner LEMBERG writes: > Uh, oh, I'm neither an expert in python programming nor a regexp guru, > sorry. Ok. No problem. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog mf/feta-klef.mf mf/feta-ma...
[EMAIL PROTECTED] writes: > > > * mf/feta-klef.mf (draw_gclef): Replace `simple_serif' for > > > top of the glyph with smooth curve. > > > > while you're at it, can you have a look at the G clef in feta-11? > > The upper loop has an odd bulge at the left. > > I don't see a problem. Please provide an image. The downstroke of change clef becomes thinner between the top loop and the downstroke. <> > > > Werner -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: comments on fixcc.py
> > Here some comments on parts where its formatting is not optimal. > > I agree with your suggestions, but most seem non-trivial. I would > be delighted if you could fix some of them, otherwise they'll > probably have to wait a bit. Uh, oh, I'm neither an expert in python programming nor a regexp guru, sorry. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog mf/feta-klef.mf mf/feta-ma...
> > * mf/feta-klef.mf (draw_gclef): Replace `simple_serif' for > > top of the glyph with smooth curve. > > while you're at it, can you have a look at the G clef in feta-11? > The upper loop has an odd bulge at the left. I don't see a problem. Please provide an image. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
