Hello,
now we have a conventional (out/*, image alt only) and www
(out-www/*, image src present) Info documentation. Should
the files of the latter override those of the former when
installed? Analogously, we also have *.pfa fonts in mf/out
and mf/out-www, which are mostly the sam
[EMAIL PROTECTED] writes:
> When running lilypond (I'm using 2.1.27), if you have 2 voices with
> different note head styles (fonts), the program will merge colliding
> notes, losing one of the fonts. The problem is shown in this example:
>
> \score { \notes { << { d'4 c'4 }
> \\ \overr
[EMAIL PROTECTED] writes:
> > some other version of LilyPond, but I can think of several
> > occasions where an update involved changes to both the
> > program and the fonts so both had to be updated together.
>
> Yes, recently I've started to have the impression that the
> fonts are less frequent
[EMAIL PROTECTED] writes:
> Thanks a lot for fixing the positioning of accidentals! It greatly
> improves the optical appearance. IMHO there is still a problem with
> naturals and sharps occurring in a chord at the same time (see
> attached image): They don't appear vertically aligned; the natura
[EMAIL PROTECTED] writes:
>
> [CVS 2004-03-10 9:50 MET]
>
> With the current vertical size of flats I think it is not appropriate
> to allow the same horizontal position if the interval is a sixth --
> they almost do touch (see image). If you insist on that, how can I
> configure this?
I've add
Werner LEMBERG writes:
> With the current vertical size of flats
Do you implicitely suggest to prefer another size of flats instead of
an adapte algorithm?
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilyp
Another resending.
Werner
==
[CVS 2004-03-07 15:58 MET]
Compare /prallmordent with /upmordent: The vertical slash is
too short in the latter glyph.
Werner
___
Lilypond-
[EMAIL PROTECTED] writes:
> Saw the changes from 'central C' to 'middle C' and I have just one more
> nit to pick about this. I saw in introduction.itely on line 513:
>
> Are a quarter note C (the middle C) and eighth note D1 (the D above...
>
> When referring to the pitch C in this particular o
Pedro Kroger wrote:
* Paul Scott ([EMAIL PROTECTED]) wrote:
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_
Ferenc Wagner writes:
>>> 4. Can you think of any related issues?
>>
>> Yes: it will cause dependency problems and spurious
>> bugreports. I think it's a bad idea.
>
> You don't think too high about apt-get, do you? Or about
> the packager? :)
Your idea is not new, we have thought about this bef
* Paul Scott ([EMAIL PROTECTED]) wrote:
> 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
Han-Wen Nienhuys writes:
> Can you provide install instructions?
> I only have ilisp in xemacs.
Bug report to Red Hat?
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
[EMAIL PROTECTED] writes:
>
> Mon, 01 Mar 2004 20:43:55 +0100, Nicolas a dit :
>
> >> try #(top-repl)
>
> > there is a place for an emacs command that would launch that, with I/Os in a
> > buffer with ilisp-mode or so, which would enable symbol completion...
>
>
> The following command def
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> 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 sp
The down-bow symbol is positioned too near to the note head. The
problem might be related to the smaller staff size...
Werner
<>___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>>
>> 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 faster than autotrace.
Thanks, will try that.
> If you
[EMAIL PROTECTED] writes:
> Since Braille is read as "prose" and is not formatted as per the
> characteristics of printed "conventional" music, I am looking at
> generating the text for a staff and planting it as a prose section above
> as discussed previously. However, it *might* be long and I wou
> > 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.
Correct, but I think this can't be automated anyway. For the
beginning only accid
> > 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 comprehensive solutio
[EMAIL PROTECTED] writes:
>
> [CVS 2004-03-13 06:24 MET]
>
> > > % 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?
>
> No,
> > % . The algorithm for computing position of rhythmic dots
> > % sometimes produces wrong results.
>
> I can't duplicate this. Can you investigate?
I suspect a rounding problem somewhere -- perhaps a similar fix to the
one you've applied a few weeks ago would do the trick. As you know, I
st
[CVS 2004-03-13 06:24 MET]
> > % 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?
No, it hasn't. In the example code I've sent to you t
> > With the current vertical size of flats
>
> Do you implicitely suggest to prefer another size of flats instead of
> an adapte algorithm?
No. I like lilypond's vertical size of flats. But I've seen scores
where flats are smaller so that they can be positionad at the same
horizontal position
23 matches
Mail list logo
