Re: anomalies with 2.1.32
[Changed to development list, since it's really a bleeding-edge issue]
On Sat, Mar 20, 2004 at 04:43:34PM +, David Bobroff wrote:
I'm still getting those same anomalies with v2.1.32; that is, dismbodied
beams, multimeasure rest numbers displaced to the right, etc. [...]
Me, too :-(
For example, both 2.1.32 and the head revision (ChangeLog 1.1917) give
me very strange results for script-abbreviations.ly (and others). See
attached files (script-abbreviations.ly and script-abbreviations.png).
There are other, even more strange errors on my chaconne example, such
as noteheads at completely wrong places, overlapping systems, randomly
misplaced accidentals, etc. Unfortunately, I didn't manage to reproduce
those effects with a small file.
Ciao,
Kili
% this chart is used in the manual too.
\version 2.1.30
\header { texidoc = @cindex Script Abbreviations
Some articulations may be entered using an abbreviation.
}
\score {
\notes \context Voice {
\override TextScript #'font-family = #'typewriter
\override TextScript #'font-shape = #'upright
c''4-._c-. s4
c''4--_c-{}-s4
c''4-+_c-+ s4
c''4-|_c-| s4
c''4-_c- s4
c''4-^_c\\^{ } s4
c''4-__c\_ s4
}
}
attachment: script-abbreviations.png___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: anomalies with 2.1.32
On Sun, 2004-03-21 at 11:42, Matthias Kilian wrote: [Changed to development list, since it's really a bleeding-edge issue] On Sat, Mar 20, 2004 at 04:43:34PM +, David Bobroff wrote: I'm still getting those same anomalies with v2.1.32; that is, dismbodied beams, multimeasure rest numbers displaced to the right, etc. [...] Me, too :-( [...] There are other, even more strange errors on my chaconne example, such as noteheads at completely wrong places, overlapping systems, randomly misplaced accidentals, etc. Unfortunately, I didn't manage to reproduce those effects with a small file. I'm having similar trouble reproducing the oddities with smaller files. Most of the really strange things I was having have disappeared as of ChangLog 1.1917; I'm not seeing the disembodied beams etc, in that file of mine. I am, however, still having some strange ties. Some are still arching quite a bit more than I think they should, and I've got one which is crashing into a stem. Also, I still shorts tie between two downstem notes which are nearly flat on top with a noticable downward bowing on the bottom. This only shows up in the multi-line score. I'd be happy to send my *.ly files and/or a page of the *.pdf file (39k). -David ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: anomalies with 2.1.32
[EMAIL PROTECTED] writes: I'm having similar trouble reproducing the oddities with smaller files. Most of the really strange things I was having have disappeared as of ChangLog 1.1917; I'm not seeing the disembodied beams etc, in that file of mine. I am, however, still having some strange ties. Some are still arching quite a bit more than I think they should, and I've got one which is crashing into a stem. Also, I still shorts tie between two Are you sure that previous versions did not have the same tie-placement problems? There haven't been any changes that affect ties specifically. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: anomalies with 2.1.32
On Sun, 2004-03-21 at 12:28, Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: I'm having similar trouble reproducing the oddities with smaller files. Most of the really strange things I was having have disappeared as of ChangLog 1.1917; I'm not seeing the disembodied beams etc, in that file of mine. I am, however, still having some strange ties. Some are still arching quite a bit more than I think they should, and I've got one which is crashing into a stem. Also, I still shorts tie between two Are you sure that previous versions did not have the same tie-placement problems? There haven't been any changes that affect ties specifically. No, I can't be 100% sure. I don't have any PS output from earlier versions, and it is possible that I did not notice this earlier as well. It is still strange, though. -David ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re : Lilypond 2.1.32 released
[EMAIL PROTECTED] writes: I saw few days ago someone else pointing this problem for lily 2.1.31 and it look like it was fixed on cvs (I don't tried it). But it's still broken for me. I'm under gentoo 1.4, python 2.3.3, guile 1.6.4. If you need other informations, tell me. makeinfo version - we require 4.6 IIRC. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
python warnings
[CVS 2004-03-20 13:43 MET] I get the following harmless warnings, using python 2.3.3: mf-to-table.py:55: FutureWarning: xy losing bits or changing sign will return a long in Python 2.4 and up cs = cs + (ord (b) shift) mf-to-table.py:280: FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up afm.write (Comment TfmCheckSum %u\n % cs) tfm.py:8: FutureWarning: xy losing bits or changing sign will return a long in Python 2.4 and up cs = cs + (ord (b) shift) Please fix -- the messages are repeated very often... Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
wrong size of time signatures
[CVS 2004-03-20 13:43 MET] Look at the attached image: The 3/4 sign is too small. It is taken from a staff reduced in size with fontSize = #-4 \override StaffSymbol #'staff-space = #(magstep -4) This is a severe bug. Werner inline: time.png___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
build warnings
Unfortunately, the lilypond build system exceeds the complexness of both groff and Freetype by some orders of magnitude -- and both are already quite complicated. Were it easier to understand I would try to fix it by myself... The very first message of the build process is repeated very often. Any chance that this is fixed? lilypond/stepmake/stepmake/generic-targets.make:142: out/dummy.dep: No such file or directory It occurs zillion times... Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
build warnings
[EMAIL PROTECTED] writes: Unfortunately, the lilypond build system exceeds the complexness of both groff and Freetype by some orders of magnitude -- and both are already quite complicated. Were it easier to understand I would try to fix it by myself... The very first message of the build process is repeated very often. Any chance that this is fixed? lilypond/stepmake/stepmake/generic-targets.make:142: out/dummy.dep: No such file or directory It occurs zillion times... fixed in CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
wrong size of time signatures
[EMAIL PROTECTED] writes: [CVS 2004-03-20 13:43 MET] Look at the attached image: The 3/4 sign is too small. It is taken from a staff reduced in size with fontSize = #-4 \override StaffSymbol #'staff-space = #(magstep -4) This is a severe bug. fixed in cvs. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
python warnings
[EMAIL PROTECTED] writes: [CVS 2004-03-20 13:43 MET] I get the following harmless warnings, using python 2.3.3: mf-to-table.py:55: FutureWarning: xy losing bits or changing sign will return a long in Python 2.4 and up cs = cs + (ord (b) shift) mf-to-table.py:280: FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up afm.write (Comment TfmCheckSum %u\n % cs) tfm.py:8: FutureWarning: xy losing bits or changing sign will return a long in Python 2.4 and up cs = cs + (ord (b) shift) Please fix -- the messages are repeated very often... fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: info problems
[lilypond CVS 2004-03-20 13:43 MET] [texinfo CVS 2004-02-28 05:36 MET] I get e.g. `Easier Music Entry: No such file or directory'. So there are many dead links. Probably a bug in `info'? Probably someone needs/needen to run texinfo-all-menu-update. Is this fixed now? No, it isn't (CVS 2004-03-19 09:10 MET). Hmm, then maybe some guru should look at this? Some facts. After a plain `make all; make install' the file `lilypond.info' says Node: Note entry0x7f66776 ... Node: Staff notation0x7f182205 ... The first entry gives a correct offset into file `lilypond.info-1', but the second entry is plain wrong. It should be 85719 instead. It appears to be a bug with the @include directive (or nested @include directives) not handled correctly by makeinfo. Karl, I'm sending you privately an archive of the input files; just say makeinfo --output lilypond.info lilypond.nexi and check the node offsets (which slightly differ from the values above for harmless reasons I think). Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
install-info problems
[texinfo CVS 2004-02-28 05:36 MET] [lilypond CVS 2004-03-20 13:43 MET] I have (among other entries) the following in my /usr/local/info/dir file: == GNU music project * GNU LilyPond: (lilypond/lilypond). The GNU music typesetter. * GNU LilyPond internals: (lilypond/lilypond-internals). LilyPond internals. * Glossary: (lilypond/music-glossary). Glossary of music terms. * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC. * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions. * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale. * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores. * midi2ly: (lilypond/lilypond)Invoking midi2ly.Importing MIDI. * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing MUP. * musedata2ly: (lilypond/lilypond)Invoking musedata2ly.Importing Musedata. * pmx2ly: (lilypond/lilypond)Invoking pmx2ly. Importing PMX. == I'm reinstalling lilypond.info, which contains the following: == INFO-DIR-SECTION GNU music project START-INFO-DIR-ENTRY * GNU LilyPond: (lilypond/lilypond). The GNU music typesetter. * Glossary: (lilypond/music-glossary). Glossary of music terms. * convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions. * midi2ly: (lilypond/lilypond)Invoking midi2ly.Importing MIDI. * etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale. * abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC. * musedata2ly: (lilypond/lilypond)Invoking musedata2ly.Importing MuseData. * mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup. END-INFO-DIR-ENTRY == The new info files have already been placed into the /usr/local/info/lilypond directory. After saying install-info --info-dir=/usr/local/info ./lilypond.info (being in the directory where the to-be-installed lilypond.info is located) I get install-info: menu item `mup2ly' already exists, for file `lilypond/lilypond' and nothing happens. This looks like a bug in install-info. It probably is confused by the reordered menu entries. Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Rectangle around the note head
On Sunday March 21 2004 10:31, Matevz Jekovec wrote: Edward Sanford Sutton, III wrote: On Friday March 19 2004 15:25, Matevz Jekovec wrote: I was searching the documentation a bit for a feature which draws a rectangle around the certain note head (or streched around 2 notes when punctuated over the bar). We use this kind of arrangement, to mark a note that is the highest in the line (the melody climax) in our contrapunkt class and I think this has become a standard for all the contrapunkt classes around. Can anyone help me out? I'm sure you're way too busy with other lilypond features, so if this marginal feature is not already possible or there is too much work to implement it, I really apologize for your time. The development version has balloon help: http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Balloon-h elp.html#Balloon% 20help which his sounds like what you wanted for a single notehead. I think that using this feature as it stands would require the two notes be marked separately if there are two of them that you want to mark. Otherwise, if using balloon help as it is, you could see if it is acceptable to just mark the first. Yes, that's exactly what I had in mind, thanks. Btw, are there any parameters to disable the line pointing out of the note at all (right now, the whole and half notes have a black dot inside them if the text is and coordinates are 0 . 0) and a way to change the rectangle size? I don't know if the balloon-padding interface changes the size of the box or tries to just shift it around on the page; I haven't played with the balloon feature myself. Perhaps some people would prefer the line connecting to the text to go away when there is no text and/or have an option for wether it is present or not. Some people might want just the box, and some people might want a line to blank space for writing on later. What does everyone else think? Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: build warnings
The very first message of the build process is repeated very often. fixed in CVS. Thanks! There is just one warning remaining which appears repeatedly during `make install', e.g. make[2]: Leaving directory `lilypond/stepmake' install-info --info-dir=/usr/local/info ./out/lilypond.info install-info: No such file or directory for ./out/lilypond.info make[1]: [install-info] Error 1 (ignored) Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
rest problem (revisited)
Since you plan to consolidate LilyPond for the next stable release, I
will check my collection of bugs, reporting problems.
The bugs below are rating very high on my wishlist.
Werner
==
%
% This file shows a problem with rests in lilypond
% CVS 2004-03-21 17:12 MET.
%
% . Vertical rest positions in a multi-voice staff should go to the default
% position of a single-voice staff if a single voice has real rests,
% and the other voices contain skip rests only.
%
% This is a severe typographical bug.
%
% . The collision algorithm for multi-voice rests still has problems.
%
% This is a severe bug.
%
\version 2.1.32
\score {
\notes \relative c' {
{ \time 4/4 a d f8 r d4 f a } \\
{ \time 4/4 s4 r8 f, a[ r a d r d f] }
}
\paper {
raggedright = ##t
}
}
% EOF
inline: rests.png___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
