Hi,
Has anybody here tried to output to ASCII art in Windows? I can
successfully create the *.as file but following that I type
$ as2text as-email.as 2>/dev/null
and the prompt doesn't do anything. If I just type
$ as2text as-email.as
then it says
bash: /usr/lilypond-1.4.12-1/bin/as2text:
On 2002.04.15 17:59 Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > > > ...
> > > > File not found `feta16list.ly'
> > >
> > > Strange, this file should have been generated in
> > > the directory mf/out/ earlier during the build
> > > process, together with the files, feta16.afm, feta16.de
[EMAIL PROTECTED] writes:
> > > ...
> > > File not found `feta16list.ly'
> >
> > Strange, this file should have been generated in
> > the directory mf/out/ earlier during the build
> > process, together with the files, feta16.afm, feta16.dep,
> > feta16.enc, feta16.log, feta16.tex and feta16.tfm,
On 2002.04.15 11:25 Mats Bengtsson wrote:
> Congratulations, you have successfully built Lilypond.
> When you have come this far in the building process, it
> just works on producing Info versions of the documentation.
>
> > /usr/local/bin/python ../.././scripts/lilypond-book.py -I
> > /tmp/lilyp
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Han-Wen> We see this question very often. We should probably put a multi-voice
Han-Wen> multi-stanza choral example in the manual.
Whatever happened to the idea of having some templates for things like
this? I've done eno
[EMAIL PROTECTED] writes:
> > It worked for me, but was the result of "try'n'error".
>
> Yes, that's the way to do it. If you needed trial and error to
> find this out, we have failed with the documentation.
> If you have several contexts of the same type that should be
> handled as separate uni
> On Sun, Apr 14, 2002 at 11:34:30PM -0300, marcelo martin wrote:
> > The problem is that the lyrics for
> > alto, tenor and bass end up being displayed under the
> > soprano staff, together with the soprano lyrics. I get
> > this warning from "ly2dvi":
>
> > \addlyrics
> > \context
Congratulations, you have successfully built Lilypond.
When you have come this far in the building process, it
just works on producing Info versions of the documentation.
> /usr/local/bin/python ../.././scripts/lilypond-book.py -I
> /tmp/lilypond-1.5.52/Documentation/user -I ./out-gcc-3.0
> -I.
