On 5-Oct-05, at 2:09 PM, Robert J. Cristel wrote:
...
texidoc
...
the following command line gives the expected result
lilypond-book --process="lilypond --format=tex --tex \
--header=texidoc test.texinfo
note that there is only one " to open the string which is never c
On 21/11/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Sven Axelsson wrote:
> >>It's understandable that reading things takes time. The strange thing is
> >>that this should all be cached, so second runs are much quicker. Can you
> >>check whether the font directory are changed (files (dis)appe
Sven Axelsson wrote:
It's understandable that reading things takes time. The strange thing is
that this should all be cached, so second runs are much quicker. Can you
check whether the font directory are changed (files (dis)appearing,
timestamps that change?) regularly?
Also, there should be a f
On 21/11/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Sven Axelsson wrote:
> > On 21/11/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >
> >>I believe that this is related to a FontConfig problem. You can verify
> >>this, by running the console version from cmd.exe and invoking it as
> >>
>
Sven Axelsson wrote:
On 21/11/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
I believe that this is related to a FontConfig problem. You can verify
this, by running the console version from cmd.exe and invoking it as
lilypond --verbose bla.ly
Yes indeed. Lilypond sits at Initializing Fon
On 21/11/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> I believe that this is related to a FontConfig problem. You can verify
> this, by running the console version from cmd.exe and invoking it as
>
>lilypond --verbose bla.ly
Yes indeed. Lilypond sits at Initializing FontConfig... for at l
[EMAIL PROTECTED] wrote:
On Sun, 20 Nov 2005 13:42:46 +0100, [EMAIL PROTECTED] said:
Is it globally slow, or is there a specific part which is recognizably
responsible for the poor performance ? (Generating
PS/PS2PDF/generating MIDI/parsing/analysis...)
D.
I don't believe it's the compiling
