On Tue, 2009-08-11 at 02:09 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 11. August 2009 01:52:36 schrieb Joe Neeman:
> > > The notes collide with the author tag, and the tempo mark and the lyrics
> > > above the staff are even above the instr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 11. August 2009 01:52:36 schrieb Joe Neeman:
> > The notes collide with the author tag, and the tempo mark and the lyrics
> > above the staff are even above the instrument name from the header.
>
> This might be because I left a bunch of v
On Mon, 2009-08-10 at 21:00 +0200, Reinhold Kainhofer wrote:
> Am Montag, 10. August 2009 14:35:22 schrieb Joe Neeman:
> > On Sat, 2009-08-01 at 12:37 +0200, Reinhold Kainhofer wrote:
> > > Am Samstag, 1. August 2009 11:44:42 schrieb Francisco Vila:
> > > > Hello. The new vertical algorythm is near
Comment #5 on issue 786 by csny...@mvpsoft.com: Extenders in lyrics stop
prematurely if a single underscore is found
http://code.google.com/p/lilypond/issues/detail?id=786
I've done some looking into this, and am not sure of the best way to fix
this. My
original patch (the one that caused t
On Sat, 2009-08-01 at 12:37 +0200, Reinhold Kainhofer wrote:
> Am Samstag, 1. August 2009 11:44:42 schrieb Francisco Vila:
> > Hello. The new vertical algorythm is nearly perfect. Here is another
> > problem, though.
>
> And another problem: There are collisions with the header. In particular,
>
2009/8/9 Werner LEMBERG :
>
>>> The attached image is taken from notation.pdf, subsection `Multiple
>>> notes to one syllable'; the bug IMHO is that the extender line is
>>> too short. Similar to `-- _ _' (with respect to the length), `__ _
>>> _ _' should construct an extender line up to the `e'.
> 1. The time signature is written immediately before the |: separating
> the bars of :||: if necessary, unless a repeat alternative ends in a
> different meter than the repeat section begins with, in which case the
> time signature is moved after the |:.
> 2. The time signature is always written
On 10 Aug 2009, at 00:51, David Kastrup wrote:
I figure LilyPond might support what people want to typeset.
Yes, if I tell it explicitly. Short of that, Lilypond should pick the
way that best reflects the art of typesetting, as recognized by the
developers. It is ok if there are manual overr
Status:
Owner: lemzwerg
Labels: Type-Enhancement
New issue 829 by lemzwerg: split Metafont output into smaller units
http://code.google.com/p/lilypond/issues/detail?id=829
Currently, we get warnings like this while Metafont processes the feta and
parmesan fonts:
some charht values had to
