[CVS 2004-03-13 6:24 MET]
> > Since installation of info files into a separate directory
> > (/usr/local/info/lilypond/), calling
> >
> > info lilypond
> >
> > no longer works. This is *very* bad. I use texinfo CVS version
> > 2004-02-28.
>
> Thanks. Fixed in CVS.
Hmm. If I now say `info
[EMAIL PROTECTED] writes:
>
> This really hurts:
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
[EMAIL PROTECTED] writes:
> I think better separating the font stuff from the main
> distribution would have the following advantages:
>
> 1. Tracking LilyPond development would be easier for the
>non-uber-hackers due to
> a) shorter build times and
Are you using potrace? It is a lot fast
On Monday March 8 2004 04:26, Mats Bengtsson wrote:
> I actually find that the depencies are well documented in INSTALL.txt,
> what information did you miss?
> Of course, it may sometimes be tricky to find out what RPM/.dpkg
> contains the necessary programs and files but that's hardly a
> LilyPond
[EMAIL PROTECTED] writes:
> %
> % This file shows problems with staves having different sizes in lilypond
> % CVS 2004-03-12 07:17 MET.
> %
> % . The algorithm for computing position of rhythmic dots sometimes
> % produces wrong results.
> %
I can't duplicate this. Can you investigate?
--
Ha
[EMAIL PROTECTED] writes:
> Implementing this in the metafont sources should be straightforward.
except that MetaFont doesn't have facilities for computing the kerning
regions, so the distances would have to be entered by hand.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4al
[EMAIL PROTECTED] writes:
>
> %
> % This file shows a problem with stem lengths in lilypond
> % CVS 2004-03-12 07:17 MET.
> %
> % . Stems for chords are too long sometimes.
> %
Can you check if current CVS has the correct behavior? A test is in
input/regression/stem-shorten.ly
--
Han-Wen Nienh
[EMAIL PROTECTED] writes:
>
> The down-bow symbol is positioned too near to the note head. The
> problem might be related to the smaller staff size...
all symbols share the same settings, and I've just tuned down the
padding to accomodate your staccato-position bugreport. Evidently, a
more comp
[EMAIL PROTECTED] writes:
>
> Staccato dots are too far away from note heads. Looking into various
> vocal scores from Peters and Breitkopf confirms this.
fixed in CVS, hopefully.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_
Paul Scott <[EMAIL PROTECTED]> writes:
> There may be a small problem with the Debian packages for 2.1.29.
Seems like you aren't using my packages, which I know to
have this problem. Unfortunately it didn't disappear with
.30, so I will have to investigate. Until a solution is
found simply remo
[EMAIL PROTECTED] writes:
>
> Another resending.
>
>
> Werner
fixed.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lily
Hi,
There may be a small problem with the Debian packages for 2.1.29.
Trying to install either I get:
Unpacking lilypond-doc (from .../lilypond-doc_2.1.29-1_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/lilypond-doc_2.1.29-1_all.deb (--unpack):
trying to overwrite `/usr/share/inf
Ferenc Wagner wrote:
Paul Scott <[EMAIL PROTECTED]> writes:
There may be a small problem with the Debian packages for 2.1.29.
Seems like you aren't using my packages, which I know to
have this problem. Unfortunately it didn't disappear with
.30, so I will have to investigate. Until a so
One issue that comes to my mind is how to make the fonts and TeX
header files available to teTeX. So far, we have done it by setting
up a separate texmf/ tree with all these files and adding it to the
teTeX search tree by setting TEXMF. If we split into separate
distributions, we would have to take
Werner LEMBERG writes:
> Since installation of info files into a separate directory
> (/usr/local/info/lilypond/), calling
>
> info lilypond
>
> no longer works. This is *very* bad. I use texinfo CVS version
> 2004-02-28.
Thanks. Fixed in CVS.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU
I agree, when notes exit form penthagram staccato should be nearer (beware
when stem direction is forced outside)
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
%
% This file shows a problem with stem lengths in lilypond
% CVS 2004-03-12 07:17 MET.
%
% . Stems for chords are too long sometimes.
%
\version "2.1.30"
\score {
\notes \relative c''{
2
}
\paper {
raggedright = ##t
}
}
% EOF
<>___
> > IMHO there is still a problem with naturals and sharps occurring
> > in a chord at the same time: They don't appear vertically aligned;
> > [...]
>
> That's because they are positioned independently. I don't consider
> this a high priority bug.
>
> (I remember that you contributed a better
Dear Gurus,
I think better separating the font stuff from the main
distribution would have the following advantages:
1. Tracking LilyPond development would be easier for the
non-uber-hackers due to
a) shorter build times and
b) less build dependencies.
2. Creating and di
%
% This file shows problems with staves having different sizes in lilypond
% CVS 2004-03-12 07:17 MET.
%
% . The algorithm for computing position of rhythmic dots sometimes
% produces wrong results.
%
% This is a severe bug.
%
% . There should be a mechanism to give the staff size in a \with {
Staccato dots are too far away from note heads. Looking into various
vocal scores from Peters and Breitkopf confirms this.
Werner
<>___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
21 matches
Mail list logo
