Re: font defects in scripts.varsegno and accordion.push
Am 24.10.2010 00:58, schrieb Carl Sorensen: [...] varsegno is now fixed, with commit bd4bb4efdb7e3a3e7ff23dbf35a33efb9b296bbc. Thanks a lot, Carl - I was just about to have a closer look at the definition of draw_bulb ... I owe you. Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/22/10 12:20 PM, Marc Hohl m...@hohlart.de wrote: Am 20.10.2010 15:30, schrieb Werner LEMBERG: The README also says that we shouldn't apply transformations to fills, but instead transform the path then fill the path. The current varsegno transforms the penstroke, which I think is contrary to this instruction. Yep. For this glyph it works accidentally. Thanks for noticing, I've missed it. Um - so what do I have to do? Rewrite the glyph completely, as Carl suggested, with a proper outline, and unfill the loops? Or is there a easier way out? varsegno is now fixed, with commit bd4bb4efdb7e3a3e7ff23dbf35a33efb9b296bbc. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Am 20.10.2010 15:30, schrieb Werner LEMBERG: The README also says that we shouldn't apply transformations to fills, but instead transform the path then fill the path. The current varsegno transforms the penstroke, which I think is contrary to this instruction. Yep. For this glyph it works accidentally. Thanks for noticing, I've missed it. Um - so what do I have to do? Rewrite the glyph completely, as Carl suggested, with a proper outline, and unfill the loops? Or is there a easier way out? Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
The README also says that we shouldn't apply transformations to fills, but instead transform the path then fill the path. The current varsegno transforms the penstroke, which I think is contrary to this instruction. Yep. For this glyph it works accidentally. Thanks for noticing, I've missed it. Um - so what do I have to do? Nothing. It accidentally works :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Here's a patch for the accordion push symbol. This looks fine. 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 mf2tp1 really doesn't like having draw instructions in the definition, so I thought it would be better to use the outline. You can draw straight lines if the pen is a square, or rectangle, or razor (this is the best of course), but not if it is polygonal $(Q#|(B actually, any polygonal pen is a no-go if conversion to an outline font is intended. Was I reading things right? Mhmm, this my paragraph is really cryptic :-) If you can reformulate it, please do so. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
This is probably overkill. FontForge is quite good in doing this for
you, provided the intersections are well defined. `fill' is necessary
because you can't exactly control the direction of the outline by
using `penstroke'.
But if I change from penstroke to fill, using zkr to go along one
side of the penstroke, then zkl to go back along the other side of
the penstroke, and controlling the directions at each of the points
on the glyph, I still get the same grazing intersections as showed
up in the glyph using penstroke.
OK. I've just played a bit, and `fill' is indeed not necessary. It's
sufficient to use `...' instead of `..', together with specifying
proper in and out directions to avoid inflections. See attached
patch. However, it doesn't fix the small grazing intersection at the
bulb.
Werner
==
--- feta-scripts.mf.old 2010-10-17 13:40:03.0 +0200
+++ feta-scripts.mf 2010-10-20 09:41:46.0 +0200
@@ -1222,15 +1222,15 @@
penstroke z1e
.. z2e
.. z3e
- .. z4e{dir (-loopangle)}
- .. z5e{dir (-loopangle)}
- .. z6e
- .. z7e
- .. z8e
- .. z9e{dir (-loopangle)}
- .. z10e{dir (-loopangle)}
- .. z11e
- .. {dir (180 - loopangle)}z12e;
+ ... {dir (-loopangle)}z4e
+ -- z5e{dir (-loopangle)}
+ ... z6e
+ ... {dir (180 - loopangle)}z7e{dir (180 - loopangle)}
+ ... z8e
+ ... {dir (-loopangle)}z9e
+ -- z10e{dir (-loopangle)}
+ ... z11e
+ ... {dir (180 - loopangle)}z12e;
addto currentpicture also currentpicture scaled -1;
penlabels (1, 1', 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Am 20.10.2010 09:50, schrieb Werner LEMBERG:
This is probably overkill. FontForge is quite good in doing this for
you, provided the intersections are well defined. `fill' is necessary
because you can't exactly control the direction of the outline by
using `penstroke'.
But if I change from penstroke to fill, using zkr to go along one
side of the penstroke, then zkl to go back along the other side of
the penstroke, and controlling the directions at each of the points
on the glyph, I still get the same grazing intersections as showed
up in the glyph using penstroke.
OK. I've just played a bit, and `fill' is indeed not necessary. It's
sufficient to use `...' instead of `..', together with specifying
proper in and out directions to avoid inflections. See attached
patch. However, it doesn't fix the small grazing intersection at the
bulb.
Hello Werner,
thanks for this information - I will use your patch and try to get the bulb
well-defined.
Marc
Werner
==
--- feta-scripts.mf.old 2010-10-17 13:40:03.0 +0200
+++ feta-scripts.mf 2010-10-20 09:41:46.0 +0200
@@ -1222,15 +1222,15 @@
penstroke z1e
.. z2e
.. z3e
- .. z4e{dir (-loopangle)}
- .. z5e{dir (-loopangle)}
- .. z6e
- .. z7e
- .. z8e
- .. z9e{dir (-loopangle)}
- .. z10e{dir (-loopangle)}
- .. z11e
- .. {dir (180 - loopangle)}z12e;
+ ... {dir (-loopangle)}z4e
+ -- z5e{dir (-loopangle)}
+ ... z6e
+ ... {dir (180 - loopangle)}z7e{dir (180 - loopangle)}
+ ... z8e
+ ... {dir (-loopangle)}z9e
+ -- z10e{dir (-loopangle)}
+ ... z11e
+ ... {dir (180 - loopangle)}z12e;
addto currentpicture also currentpicture scaled -1;
penlabels (1, 1', 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
+ ... {dir (180 - loopangle)}z7e{dir (180 - loopangle)}
This is too much :-) The following
+ ... z7e{dir (180 - loopangle)}
is sufficient. A new patch attached (to preserve tabs for dull mail
programs).
Werner
--- feta-scripts.mf.old 2010-10-17 13:40:03.0 +0200
+++ feta-scripts.mf 2010-10-20 09:54:57.0 +0200
@@ -1222,15 +1222,15 @@
penstroke z1e
.. z2e
.. z3e
- .. z4e{dir (-loopangle)}
- .. z5e{dir (-loopangle)}
- .. z6e
- .. z7e
- .. z8e
- .. z9e{dir (-loopangle)}
- .. z10e{dir (-loopangle)}
- .. z11e
- .. {dir (180 - loopangle)}z12e;
+ ... {dir (-loopangle)}z4e
+ -- z5e{dir (-loopangle)}
+ ... z6e
+ ... z7e{dir (180 - loopangle)}
+ ... z8e
+ ... {dir (-loopangle)}z9e
+ -- z10e{dir (-loopangle)}
+ ... z11e
+ ... {dir (180 - loopangle)}z12e;
addto currentpicture also currentpicture scaled -1;
penlabels (1, 1', 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/20/10 1:59 AM, Werner LEMBERG w...@gnu.org wrote:
+ ... {dir (180 - loopangle)}z7e{dir (180 - loopangle)}
This is too much :-) The following
+ ... z7e{dir (180 - loopangle)}
is sufficient. A new patch attached (to preserve tabs for dull mail
programs).
The README also says that we shouldn't apply transformations to fills, but
instead transform the path then fill the path. The current varsegno
transforms the penstroke, which I think is contrary to this instruction.
The draw_bulb macro should take care of the grazing intersection on the
bulb.
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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 run mf2pt1, this command doesn't seem to exist. How can I obtain it? Marc Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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 scripts/build: cat mf2pt1.pl | sed -e 's...@perl@!/usr/bin/perl!g' out/mf2pt1 chmod 755 out/mf2pt1 in mf: cd out \ mpost -progname=mpost -ini ../mf2pt1.mp \\dump TMP=`mktemp -d ./out/pfbtemp.X` \ ( cd $TMP \ ln -s ../mf2pt1.mem . \ MFINPUTS=..:: \ ../scripts/build/out/mf2pt1 --rounding=0.0001 \ --family=feta20 \ --fullname=feta20 \ --name=feta20 feta20.mf ) \ mv $TMP/*pfb out; \ rm -rf $TMP You should add FONTFORGE=foo to the environment variables of mf2pt1 to suppress the execution of the `fontforge' binary. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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 file during `make all' (slightly adapted): in scripts/build: cat mf2pt1.pl | sed -e 's...@perl@!/usr/bin/perl!g' out/mf2pt1 chmod 755 out/mf2pt1 in mf: cd out \ mpost -progname=mpost -ini ../mf2pt1.mp \\dump TMP=`mktemp -d ./out/pfbtemp.X` \ ( cd $TMP \ ln -s ../mf2pt1.mem . \ MFINPUTS=..:: \ ../scripts/build/out/mf2pt1 --rounding=0.0001 \ --family=feta20 \ --fullname=feta20 \ --name=feta20 feta20.mf ) \ mv $TMP/*pfb out; \ rm -rf $TMP You should add FONTFORGE=foo to the environment variables of mf2pt1 to suppress the execution of the `fontforge' binary. Ok, thank you. So the advice --- The recommended calling sequence of mf2pt1 is mf2pt1 --rounding=0.0001 other options font 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 I'll have a look to the sources of varsegno and try to correct the drawing routines as you proposed in the tracker. Thanks, Marc Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
So the advice --- The recommended calling sequence of mf2pt1 is mf2pt1 --rounding=0.0001 other options font 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 development, I simply copy all MF files and the mf2pt1 perl file (and the mf2pt1.mp) to another directory, create the mem file and run then mf2pt1 $(Q#|(B I don't like working directly within the git repository. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Am 19.10.2010 11:14, schrieb Werner LEMBERG:
So the advice
---
The recommended calling sequence of mf2pt1 is
mf2pt1 --rounding=0.0001other options font
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 development, I simply copy all MF files and the mf2pt1 perl
file (and the mf2pt1.mp) to another directory, create the mem file and
run then mf2pt1 $(Q#|(B I don't like working directly within the git
repository.
Ok. I created a new branch and tried to improve the varsegno in there.
Now my mf knowledge is cough a bit /cough rusty, so all I can come
up with
is attached in the patch.
Marc
Werner
From 1fa7fdb7d035eea56f406489a09dd496937c6474 Mon Sep 17 00:00:00 2001
From: Marc Hohl m...@hohlart.de
Date: Tue, 19 Oct 2010 11:44:07 +0200
Subject: [PATCH] Font: removing intersecting paths in varsegno
---
mf/feta-scripts.mf | 20
1 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/mf/feta-scripts.mf b/mf/feta-scripts.mf
index 8496fd7..f87f716 100644
--- a/mf/feta-scripts.mf
+++ b/mf/feta-scripts.mf
@@ -1153,7 +1153,7 @@ fet_endchar;
fet_beginchar (Varied Segno, varsegno);
- save ht, wd, loopdist, loopangle;
+ save ht, wd, loopdist, loopangle, looptension;
save thin, med, thick;
save bulbradius, center;
pair center;
@@ -1166,6 +1166,7 @@ fet_beginchar (Varied Segno, varsegno);
loopdist = 4/3 staff_space;
loopangle = 35;
+ looptension = 1.1;
thick = 1/2 staff_space;
med = 1/4 staff_space;
@@ -1212,6 +1213,10 @@ fet_beginchar (Varied Segno, varsegno);
z12 = -center;
penpos12 (thick, 270 - loopangle);
+
+ x13 = x9;
+ y13 = y9 - loopdist;
+ penpos13 (thick, 270 - loopangle);
z1' = 4/3[z1l, z1r];
bulbradius = length (z1l - z1');
@@ -1224,16 +1229,23 @@ fet_beginchar (Varied Segno, varsegno);
.. z3e
.. z4e{dir (-loopangle)}
.. z5e{dir (-loopangle)}
+ .. tension looptension
.. z6e
- .. z7e
+ .. tension looptension
+ .. z7e{dir (180 - loopangle)}
+ .. tension looptension
.. z8e
+ .. tension looptension
.. z9e{dir (-loopangle)}
.. z10e{dir (-loopangle)}
+ .. tension looptension
.. z11e
- .. {dir (180 - loopangle)}z12e;
+ .. tension looptension
+ .. {dir (180 - loopangle)}z12e
+ .. {dir (180 - loopangle)}z13e;
addto currentpicture also currentpicture scaled -1;
- penlabels (1, 1', 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
+ penlabels (1, 1', 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13);
% draw_staff (-2, 2, 0);
fet_endchar;
--
1.7.0.4
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/19/10 3:48 AM, Marc Hohl m...@hohlart.de wrote: Am 19.10.2010 11:14, schrieb Werner LEMBERG: So the advice --- The recommended calling sequence of mf2pt1 is mf2pt1 --rounding=0.0001other options font 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 development, I simply copy all MF files and the mf2pt1 perl file (and the mf2pt1.mp) to another directory, create the mem file and run then mf2pt1 $(Q#|(B I don't like working directly within the git repository. Ok. I created a new branch and tried to improve the varsegno in there. Now my mf knowledge is cough a bit /cough rusty, so all I can come up with is attached in the patch. Actually, it's a lot easier than this. See the attached patch. Thanks, Carl 0001-Font-Fix-grazing-intersection-in-scripts.varsegno.patch Description: 0001-Font-Fix-grazing-intersection-in-scripts.varsegno.patch ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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 mf2tp1 really doesn't like having draw instructions in the definition, so I thought it would be better to use the outline. Was I reading things right? Thanks, Carl 0001-Font-remove-draw-from-accordion-push.patch Description: 0001-Font-remove-draw-from-accordion-push.patch ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Am 19.10.2010 12:06, schrieb Carl Sorensen: On 10/19/10 3:48 AM, Marc Hohlm...@hohlart.de wrote: Am 19.10.2010 11:14, schrieb Werner LEMBERG: So the advice --- The recommended calling sequence of mf2pt1 is mf2pt1 --rounding=0.0001other options font 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 development, I simply copy all MF files and the mf2pt1 perl file (and the mf2pt1.mp) to another directory, create the mem file and run then mf2pt1 $(Q#|(B I don't like working directly within the git repository. Ok. I created a new branch and tried to improve the varsegno in there. Now my mf knowledge iscough a bit/cough rusty, so all I can come up with is attached in the patch. 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 visible in fontforge at 200%), so I had to introduce the tensions. Marc Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/19/10 11:19 AM, Marc Hohl m...@hohlart.de 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 visible in fontforge at 200%), so I had to introduce the tensions. Sure enough! Good job. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/19/10 11:19 AM, Marc Hohl m...@hohlart.de 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 visible in fontforge at 400%. Werner, any suggestions on how to handle this? Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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%. Werner, any suggestions on how to handle this? Don't use `penstroke' but `fill'. BTW, there's another defect: the bulb intersects slightly with the beginning of the `serpentine' stroke. You must compute the exact intersectionpoint to avoid that. Or maybe you can try the macro `draw_bulb'? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/19/10 12:52 PM, Werner LEMBERG w...@gnu.org 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 visible in fontforge at 400%. Werner, any suggestions on how to handle this? 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. Marc, are you going to take this on? Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Am 19.10.2010 21:00, schrieb Carl Sorensen: On 10/19/10 12:52 PM, Werner LEMBERGw...@gnu.org 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 visible in fontforge at 400%. Werner, any suggestions on how to handle this? 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. I was trying to simply replace the penstroke by a fill, but this didn't change the situation (which, afterwards, seems to be logical). Marc, are you going to take this on? I am not sure whether I can cope with this. If anybody else can do this in 15 minutes or so, please do not hesitate. I think I need at least two hours to get this done, should I succeed. Marc Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
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, provided the intersections are well defined. `fill' is necessary because you can't exactly control the direction of the outline by using `penstroke'. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/19/10 5:24 PM, Werner LEMBERG w...@gnu.org 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 overkill. FontForge is quite good in doing this for you, provided the intersections are well defined. `fill' is necessary because you can't exactly control the direction of the outline by using `penstroke'. But if I change from penstroke to fill, using zkr to go along one side of the penstroke, then zkl to go back along the other side of the penstroke, and controlling the directions at each of the points on the glyph, I still get the same grazing intersections as showed up in the glyph using penstroke. So I must misunderstand your comment. Any clarification you can provide would be welcome. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
I wrote: I've attached fontforge images of two broken glyphs; [...] Listmaster, please approve this mail sitting in the queue! Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
On 10/18/10 9:21 AM, Werner LEMBERG w...@gnu.org wrote: I wrote: I've attached fontforge images of two broken glyphs; [...] Werner, Can you open an issue directly on the tracker and post your attachments there? It seems that there ought to be three issues: 1) varsegno 2) accordion.push 3) Shape note heads at small font sizes. I'll take over 2 and 3. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font defects in scripts.varsegno and accordion.push
Can you open an issue directly on the tracker and post your attachments there? Done. It's issue #1335. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
