Neil Puttock wrote:
LGTM, pushed to master.
I've just made one minor change: new features go at the
top of changes.tely.
The example on the changes page is not displaying
properly.
- Mark
___
lilypond-devel mailing list
2010/1/16 Mark Polesky markpole...@yahoo.com:
The example on the changes page is not displaying
properly.
Where?
Looks fine here: http://lilypond.org/doc/v2.13/Documentation/changes/index#top
Regards,
Neil
___
lilypond-devel mailing list
Neil Puttock wrote:
The example on the changes page is not displaying
properly.
Where?
http://kainhofer.com/~lilypond/Documentation/changes/index.html
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2010/1/16 Mark Polesky markpole...@yahoo.com:
http://kainhofer.com/~lilypond/Documentation/changes/index.html
This always happens with font changes on kainhofer.com since it
doesn't do a clean docs build every day.
Cheers,
Neil
___
lilypond-devel
Perhaps I'm wrong, and the whole thing is a non-issue: ghostscript
can compute the exact bounding box of an EPS file, AFAIK, taking
care of the real dimensions of all glyphs (relying on the outlines
instead of the metrics).
I don't know what ghostscript can do, but even if it cannot compute
2010/1/10 Carsten Steger carsten.ste...@googlemail.com:
Also, from our discussion it would appear to me that the patch for the
halfopen articulation character I have designed could be pushed.
LGTM, pushed to master.
I've just made one minor change: new features go at the top of changes.tely.
This might cause problems if images are converted to, say, cropped
PNG images. You must assure somehow that the slash won't get cut
off.
[...] Furthermore, if I understand your comment correctly, even
something like the coda or snappizzicato characters could have the
semi-circles that
This might cause problems if images are converted to, say, cropped
PNG images. You must assure somehow that the slash won't get cut
off.
[...] Furthermore, if I understand your comment correctly, even
something like the coda or snappizzicato characters could have the
semi-circles that
And the cutoffs in section 1.1.3, subsection `Automatic Accidentals',
look like a real bug in lilypond since this must not happen IMHO...
I agree that these do look like a real bug. This issue, however,
seems to have nothing to to with character rendering since the beams
and stems are cut off.
Thus, the slash of the character sticks out of the bounding box by
some amount.
This might cause problems if images are converted to, say, cropped PNG
images. You must assure somehow that the slash won't get cut off.
Everything else looks fine! BTW, I don't get any warning from my
fontforge
Is there a chance that you would consider this character for
inclusion in LilyPond 2.13?
If Werner's OK with that, I'll open a feature request on the
tracker.
Please go ahead.
a patch for the half-open articulation character is attached.
The character is designed to match the open
On Fri, Jan 1, 2010 at 4:08 PM, Carsten Steger
carsten.ste...@googlemail.com wrote:
Is there a chance that you would consider this character for inclusion
in LilyPond 2.13? If so, I would start working on optimizing the
design of the character and also start working on modifying LilyPond
to
Is there a chance that you would consider this character for
inclusion in LilyPond 2.13?
If Werner's OK with that, I'll open a feature request on the
tracker.
Please go ahead.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
13 matches
Mail list logo
