[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Janek Warchoł
Subject: Re: flags, beams and stem length in forced directions - output improvement
Date: Tue, 25 Jan 2011 10:12:35 +0100

2011/1/24 Werner LEMBERG <address@hidden>:
>> Calling
>>   perl scripts/build/
>> from lilypond-git directory says
>>   Can't exec @PERL@ at scripts/build/ line 1.
>> First line of that file reads
>>   address@hidden@
>> Strange...
> Well, the perl script gets `massaged', and the @PERL@ construct gets
> replaced with a real path to the perl interpreter.  I forgot that.
> In case you have a compiled lilypond, use scripts/build/out/mf2pt1
> instead.  Otherwise, copy the file and simply remove that line.

i called
  FONTFORGE=foo perl build/scripts/build/out/mf2pt1 --rounding=0.0001
from lilypond-git, but it said
  Invoking "mpost -mem=mf2pt1 -progname=mpost '\mode:=localfont;
mag:=100; bpppix 0.02; input'"...
  kpathsea: Running mktexfmt mf2pt1.mem
  Sorry, I can't find the 'mf2pt1' mem file; will try 'plain'.
  kpathsea: Running mktexfmt plain.mem
  I can't find the 'plain' mem file!
  mf2pt1: "mpost -mem=mf2pt1 -progname=mpost '\mode:=localfont;
mag:=100; bpppix 0.02; input'" failed (Bad file
So i've found mf2pt1.mem file (it was in lilypond-git/mf/build/out),
moved it to lilypond-git and called
  FONTFORGE=foo perl build/scripts/build/out/mf2pt1 --rounding=0.0001
A bit messy, but it worked - now i have feta-noteheads20.pfb. Thanks :)

2011/1/24 Werner LEMBERG <address@hidden>:
>>> 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've received an explanation: It's a feature.  In the central
> configuration file of TeXLive, `texmf.cnf', you can find this:
>  % Allow TeX \openin, \openout, or \input on filenames starting with `.'
>  % (e.g., .rhosts) or outside the current tree (e.g., /etc/passwd)?
>  % a (any)        : any file can be opened.
>  % r (restricted) : disallow opening "dotfiles".
>  % p (paranoid)   : as `r' and disallow going to parent directories, and
>  %                  restrict absolute paths to be under $TEXMFOUTPUT.
>  openout_any = p
>  openin_any = a
> This means that by default you can't access the parent directory while
> writing output files for security reasons.

Aha. Well, we can live with that :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]