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
___
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
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
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,
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
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
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
+ ... {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
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
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
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 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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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)
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
27 matches
Mail list logo
