On Tue, Oct 19, 2010 at 11:00:01AM +0200, Francisco Vila wrote:
> Thank you. Could you do the same with French pictures?
It's not a matter of individual files; it simply updates
everything in pictures/ and ly-examples/. Done, and should be
visible in half an hour.
Cheers,
- Graham
_
On 10/19/10 5:24 PM, "Werner LEMBERG" wrote:
>
>
>>> Don't use `penstroke' but `fill'.
>>
>> That was my thought, when looking at the glyph. Find the
>> intersections, and draw the relevant paths for the entire outline
>> and subtract the relevant paths for the holes.
>
> This is probably
Am Dienstag, 19. Oktober 2010, um 23:34:52 schrieb Keith E OHara:
> On Tue, 19 Oct 2010 13:34:05 -0700, Trevor Daniels wrote:
>
> >> 2) Two pieces of instruction were a bit vague :
> [ . . . ]
>
> >> "[...] when cue notes end, the name of the original instrument2
> >> should be printed, and any o
>> Don't use `penstroke' but `fill'.
>
> That was my thought, when looking at the glyph. Find the
> intersections, and draw the relevant paths for the entire outline
> and subtract the relevant paths for the holes.
This is probably overkill. FontForge is quite good in doing this for
you, provi
Keith E OHara wrote Tuesday, October 19, 2010 10:34 PM
On Tue, 19 Oct 2010 13:34:05 -0700, Trevor Daniels wrote:
If no one objects soon I shall push it.
James Lowe made comments that you might not have seen yet. I see
where he is coming from, but I hope my answer explained the
purpose of
Trevor Daniels wrote Tuesday, October 19, 2010 9:35 PM
Keith E OHara wrote Tuesday, October 19, 2010 12:21 AM
Suggestions attached as a diff,
I'm happy to push this as is. Many thanks Keith.
Pushed to git pretty well as you suggested, Keith, and snippet
updated
in git.
Changed version
On Tue, 19 Oct 2010 13:34:05 -0700, Trevor Daniels wrote:
If no one objects soon I shall push it.
James Lowe made comments that you might not have seen yet. I see where he is
coming from, but I hope my answer explained the purpose of the changes well
enough.
(For future reference, please
Keith E OHara wrote Tuesday, October 19, 2010 12:21 AM
One thing worth discussing is that I use the verb "to cue"
differently from the original author.
I believe that to cue is to *give* a signal for someone else to
begin action. So the instrument playing just before the singer
begins is t
Keith E OHara wrote Monday, October 18, 2010 11:40 PM
I suggest (diff attached) removing the part about
instrumentCueName in favor of a fuller example for \killCues. The
manual teaches markup elsewhere; the challenge with cue-note
labels is to let the label appear with the cue notes in parts
Am 19.10.2010 21:00, schrieb Carl Sorensen:
On 10/19/10 12:52 PM, "Werner LEMBERG" wrote:
Um, that's what I tried before, but I still got intersections
(which were smaller than before, but still visible in fontforge at
200%), so I had to introduce the tensions.
When I applied an
On 10/19/10 12:52 PM, "Werner LEMBERG" wrote:
>>> Um, that's what I tried before, but I still got intersections
>>> (which were smaller than before, but still visible in fontforge at
>>> 200%), so I had to introduce the tensions.
>>
>> When I applied and tested your patch, there were still grazi
>> Um, that's what I tried before, but I still got intersections
>> (which were smaller than before, but still visible in fontforge at
>> 200%), so I had to introduce the tensions.
>
> When I applied and tested your patch, there were still grazing
> intersections visible in fontforge at 400%.
>
>
On Tue, Oct 19, 2010 at 11:31 AM, Ian Hulin wrote:
> Hi Patrick,
>
> Patch is attached.
Thanks, I've pushed it.
Regards,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 10/19/10 11:19 AM, "Marc Hohl" wrote:
> Um, that's what I tried before, but I still got intersections (which were
> smaller than before, but still visible in fontforge at 200%), so I had to
> introduce the tensions.
When I applied and tested your patch, there were still grazing intersections
On Tue, Oct 19, 2010 at 8:02 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
>> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
>> wrote:
>> > I don't understand the issue; can't you just set PYTHON=python2 when
>> > calling configure, and in ca
On 10/19/10 11:19 AM, "Marc Hohl" wrote:
> Am 19.10.2010 12:06, schrieb Carl Sorensen:
>>
>>
>>>
>> Actually, it's a lot easier than this.
>>
>> See the attached patch.
>>
> Um, that's what I tried before, but I still got intersections (which were
> smaller than before, but still visi
Am 19.10.2010 12:06, schrieb Carl Sorensen:
On 10/19/10 3:48 AM, "Marc Hohl" wrote:
Am 19.10.2010 11:14, schrieb Werner LEMBERG:
So the advice
---
The recommended calling sequence of mf2pt1 is
mf2pt1 --rounding=0.0001
You need mf2pt1 version 2.1 or newer.
---
in
On Tue, 19 Oct 2010 00:33:25 -0700, James wrote:
Sorry for jumping in here, I have read the thread prior to this and
while I agree the Cue Notes section is sketchy, I am not sure how this
is an improvement and this seems more complicated.
What are we achieving here?
Thank you for jumping in
3 differences from .35 to .36 of note.
multiple-time-sig-settings.ly: I believe this is down to a re-write of the
test file and fixing issue 1284.
utf-8.ly: differences in the horizontal spacing. Probably not significant
but might be worth checking by someone who understands what's happening
Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
> wrote:
> > I don't understand the issue; can't you just set PYTHON=python2 when
> > calling configure, and in case you need some scripts in auxiliar call
> > them by prependi
Here's a patch for the accordion push symbol.
I went ahead and changed to a fill of the outline.
It would have been simpler if I had just drawn two straight lines:
draw z1
-- z2;
draw z3
-- z2;
This would seem to be allowed by the instructions in README, but I get the
sense that mf2
On 10/19/10 3:48 AM, "Marc Hohl" wrote:
> Am 19.10.2010 11:14, schrieb Werner LEMBERG:
>>
>>> So the advice
>>> ---
>>> The recommended calling sequence of mf2pt1 is
>>>
>>>mf2pt1 --rounding=0.0001
>>>
>>> You need mf2pt1 version 2.1 or newer.
>>> ---
>>> in README should read
>>>
Am 19.10.2010 11:14, schrieb Werner LEMBERG:
So the advice
---
The recommended calling sequence of mf2pt1 is
mf2pt1 --rounding=0.0001
You need mf2pt1 version 2.1 or newer.
---
in README should read
cd mf/
ln -s out/mf2pt1.mem .
FONTFORGE=foo ../scripts/build/out/mf2pt1 --rounding=0.00
> So the advice
> ---
> The recommended calling sequence of mf2pt1 is
>
> mf2pt1 --rounding=0.0001
>
> You need mf2pt1 version 2.1 or newer.
> ---
> in README should read
>
> cd mf/
> ln -s out/mf2pt1.mem .
> FONTFORGE=foo ../scripts/build/out/mf2pt1 --rounding=0.0001 feta13
Yes. For deve
2010/10/16 Graham Percival :
> On Sat, Oct 16, 2010 at 5:21 PM, Francisco Vila wrote:
>> Hello. Does anybody know why some German image files are in Git but
>> not in the web?
>
> Yes.
> http://lilypond.org/doc/v2.13/Documentation/contributor/uploading-and-security
>
> The relevant portion is (un
Am 19.10.2010 10:26, schrieb Werner LEMBERG:
I did the faulty varsegno sign. I read the tracker and wanted to
reproduce your observations, but I am unable to run mf2pt1, this
command doesn't seem to exist. How can I obtain it?
It's part of lilypond. Here the relevant lines from my log
> I did the faulty varsegno sign. I read the tracker and wanted to
> reproduce your observations, but I am unable to run mf2pt1, this
> command doesn't seem to exist. How can I obtain it?
It's part of lilypond. Here the relevant lines from my log file
during `make all' (slightly adapted):
in
Am 18.10.2010 22:39, schrieb Werner LEMBERG:
Can you open an issue directly on the tracker and post your
attachments there?
Done. It's issue #1335.
Hello Werner,
I did the faulty varsegno sign. I read the tracker and wanted to
reproduce your observations, but I am unable to ru
Hello,
On 18/10/2010 23:40, Keith E OHara wrote:
On mailing list lilypond-user, Trevor Daniels wrote:
Keith E OHara wrote Wednesday, October 06, 2010 9:40 AM
I no longer see any reason to use instrumentCueName for the labels
that identify the instrument playing cue notes.
OK. I'll see what
29 matches
Mail list logo
