2011/1/24 Werner LEMBERG <w...@gnu.org>: >>> In one of my previous mails I gave you a recipe how to produce a >>> `proof' version of the font using `mf' and `gftodvi'. It doesn't >>> help to get the exact outline since it is always based on the >>> rasterized output of `mf', but it nicely shows the construction >>> points (if possible). >> >> I've tried making a "proof" version of the font, but my insufficient >> knowledge resulted in a failure :( > > Could you elaborate, please? Essentially, you just have to call mf, > followed by gf2dvi.
It worked now. Perhaps i called it in the wrong directory... Silly me. By the way, how to call mf with changed output directory? I tried mf '\mode:=proof; input feta-noteheads20'-output-directory=../build and mf '\mode:=proof; -output-directory="../build" input feta-noteheads20' but both failed... >>> FONTFORGE=foo mf2pt1 --rounding=0.0001 <mf-font> , >>> >>> do you see the irregularity if you open the font with fontforge? >> >> Yes, i attach a screenshot. The font file is here: >> http://www.mediafire.com/?hadr9nt5w5iqulb > > Looking at the image, I see that you haven't followed my advice since > all overlapping outlines have been removed already. Using the > `FONTFORGE=foo' environment setting while calling mf2pt1 prevents this > so that you get the direct output of mf2pt1 without postprocessing > with fontforge. Ah, i think i understand. The screenshot i provided was useless because it said us what we already knew, that there is a spike in the final font. Looking at the proof dvi, i can say that there are no spikes there. I understand that it's fontforge's fault then, am i right? > And yes, it should really be `foo', a non-existent > program name. running FONTFORGE=foo mf2pt1 --rounding=0.0001 <feta-noteheads20> in /mf or /build/mf results in this error: bash: syntax error near unexpected token `newline' I'm probably doing something stupid here... > To set up mf2pt1 so that you can call it manually in an easy way, > please execute > > mpost -progname=mpost -ini mf2pt1.mp \\dump that worked. Now i have mf2pt1.log in /mf directory. By the way, is there an easy way of avoiding cluttering my main source directory and doing all this in /build for example? > in the `mf' subdirectory (lilypond does this in the `mf/out' directory > during `make all'). > >>> You might try the recent CVS version of fontforge which has a lot >>> of fixed issues. Don't forget to pass `--enable-double' to the >>> `configure' script of fontforge. >> >> Umm.. i'm afraid i don't understand :( > > 1. Check out the CVS sources of fontforge: > > cvs -d:pserver:anonym...@fontforge.cvs.sourceforge.net:/cvsroot/fontforge > login Do i need to have an account of some kind and how can i create it? It asks me for CVS password. >From what i see i cannot proceed any further. Thanks for help! Janek > cvs -z3 > -d:pserver:anonym...@fontforge.cvs.sourceforge.net:/cvsroot/fontforge co -P > fontforge > > 2. Change to the freshly created `fontforge' directory and configure > the program with > > ./configure --enable-double > > then build the program with > > make > > If the configure script complains it is necessary to install > additional packages to fulfill all dependencies (probably missing > `*-devel' packages so that the necessary C header files are > provided for compiling). After installing a new package, simply > rerun `./configure --enable-double' until it succeeds. > > 3. Finally, install it with > > sudo make install > > Assuming that you are originally using a fontforge package from your > GNU/Linux distribution, your original binary is in /usr/bin/fontforge. > Now you have a new, additional binary in `/usr/local/bin/fontforge'. > You might add `--prefix=/your/preferred/directory/tree' to the > configure script if you want a different location than `/usr/local'. > > > Werner > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
