Re: flags,beams and stem length in forced directions - output improvement

[Werner LEMBERG]

> 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...

It fails for me too...  I've just reported this to the TeXLive people.

I suggest that you copy the whole `mf' directory to another place.

> 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?

I think so.

> 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...

It's my fault, sorry.  I've used `<' and `>' as meta-markers which
shouldn't be used for invocation.  Try this:

  FONTFORGE=foo mf2pt1 --rounding=0.0001 feta-noteheads20.mf

> By the way, is there an easy way of avoiding cluttering my main source
> directory and doing all this in /build for example?

You might write a script to do that, something like

  cd build
  mf '\mode:=proof; input ../feta-noteheads20'
  cd ..

>>     cvs -d:pserver:address@hidden:/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.

No password required.  Simply press enter.


    Werner