> 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
>>> 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-c
Reviewers: joeneeman,
Message:
On 2010/01/10 05:03:30, joeneeman wrote:
http://codereview.appspot.com/186054/diff/1/2
File lily/pango-font.cc (right):
http://codereview.appspot.com/186054/diff/1/2#newcode384
lily/pango-font.cc:384: bool to_paths = get_program_option
("music-strings-to-paths")
http://codereview.appspot.com/186054/diff/1/2
File lily/pango-font.cc (right):
http://codereview.appspot.com/186054/diff/1/2#newcode384
lily/pango-font.cc:384: bool to_paths = get_program_option
("music-strings-to-paths");
It would be more consistent, I think, to use a global variable here.
htt
Hello,
This patch addresses the generalization of the "utf-8-string" check in
lily/pango-font.cc. Please review it here:
http://codereview.appspot.com/186054/show
Thanks,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gn
On 2010-01-09, Graham Percival wrote:
> On Sat, Jan 09, 2010 at 01:51:26AM -0200, Han-Wen Nienhuys wrote:
> >
> > What was the reasoning for removing everything?
>
> http://lists.gnu.org/archive/html/lilypond-devel/2009-10/msg00101.html
> as well as 2 or 3 earlier messages to -devel (between 1 an
On 2010-01-09, Graham Percival wrote:
> Patrick, IIRC you recently changed the CSS to have bigger margins.
> This wastes a lot (relatively speaking) of horizontal space on
> small screens+windows. Could you keep the smaller margins (more
> text space) for small screens? I don't mind if you do som
Sure, go ahead.
Cheers,
- Graham
On Sat, Jan 09, 2010 at 11:08:01AM -0800, Mark Polesky wrote:
> All the doc files' header comments contain
>
> coding: utf-8
>
> except macros.itexi and most of the contributor/ folder,
> which have
>
> coding: us-ascii
>
> instead. I assume that's an ove
All the doc files' header comments contain
coding: utf-8
except macros.itexi and most of the contributor/ folder,
which have
coding: us-ascii
instead. I assume that's an oversight, and it's okay to
push the attached patch?
Thanks.
- Mark
From 0e19bee899ef2390a186bd678df9c2196897e2
>> 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
Graham Percival wrote:
> 1 Introduction
> [...]
> 1.4 lily-git
> (maybe -- have you decided one way or the other?)
Yes. lily-git instructions will go into chapter 2 (I'm
still working on this).
- Mark
___
lilypond-devel mailing list
lilypond-
Patrick, IIRC you recently changed the CSS to have bigger margins.
This wastes a lot (relatively speaking) of horizontal space on
small screens+windows. Could you keep the smaller margins (more
text space) for small screens? I don't mind if you do something
fancy and increase the margins for larg
Le 6 janv. 2010 à 13:35, Reinhold Kainhofer a écrit :
>
>> If so it is a pity because it would be quite nice to be able
>> to write things like:
>>
>> \tocItem \markup { \fromproperty #'header:title }
>
> I had the same problem a while ago, and there is a workaround to make header
> fields avai
Han-Wen Nienhuys writes:
> All done and submitted.
Thanks. I needed that.
Now I'll have a go at figuring out just what to do with it for my
personal task list.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.
In the past few months, we've had a number of developers being
surprised at some of the build system changes. The changes (not
just the input/ deletions) *were* announced in advance, but it's
easy to miss emails on a large list like -devel. When a proposal
goes out and nobody answers, it's diffic
15 matches
Mail list logo