Re: Problems with lilypond-book
Colin Cotter <[EMAIL PROTECTED]> writes: > I have reposted my question with the source attached. I hope that you can > spot what I am doing wrong! Yes, it was my first suggestion: add a \paper block. You should also put the two pieces in separate files; lilypond-book will include only the first piece of music. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: tab
[EMAIL PROTECTED] writes: > I don't believe that the mess was the result of > users trying to cut down on typing, I just don't. No, but having both a functional programming form of extending lily and a macro oriented form will lead to confusion, and there is enough of that already in Lily as we have it now. > I have a way of passing values now, fairly easily. > How are you hurt? I'm not hurt, but people keep asking me to put in parameters, macros and what have you. This gets a little tiring, so I wanted to be clear. Perhaps this is an item for the FAQ. -- Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/ ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Problems with lilypond-book
I'm a little confused - I do have a \paper command in my ly file. Can you explain what the format is? Colin > Colin Cotter <[EMAIL PROTECTED]> writes: > > > I have reposted my question with the source attached. I hope that you can > > spot what I am doing wrong! > > Yes, it was my first suggestion: add a \paper block. You should also > put the two pieces in separate files; lilypond-book will include only > the first piece of music. > > Jan. > > -- Colin Cotter ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: tab
On Mon, 09 Sep 2002 08:49:45 Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > I don't believe that the mess was the result of > > users trying to cut down on typing, I just don't. > > No, but having both a functional programming form of extending lily > and a macro oriented form will lead to confusion, and there is enough > of that already in Lily as we have it now. > > > I have a way of passing values now, fairly easily. > > How are you hurt? > > I'm not hurt, but people keep asking me to put in parameters, macros > and what have you. This gets a little tiring, so I wanted to be clear. Not quite clear yet. You allow pass through LaTeX in the \header and other places. In lilypond-book I could take advantage of \newcommand. That does not amount to a 'macro oriented form', and I don't see how it ever could. In lily-pond book I was able to use \newcommand to insert the string number *or* letter with circles around them both into the text *and* into the fingering of the lilypond blocks with almost exactly the same syntax. This was very helpful, and the opposite of confusing. The camel's nose is under the tent as long as you use LaTeX. If people want to confuse themselves, what do you care? No one is forcing you to adopt any macros which you don't want to adopt. If I find that I have to change a stem length, I define a macro *immediately*, slong = because if I use it more than once it saves me typing, and I don't know at the outset how many times I am going to need it. Having a different command for every stemlength needed is just annoying. sloong = slooong = slng = sshort = sshoort = Nobody wants to invent a 'macro oriented form'. It's just not cost effective. I do slng (well, not exactly) because I am *lazy*. If I were sufficiently confident of the result, I could type in shortcuts like $slong$ 4.0 and then use the editor when I was done to search and replace. The problem is that one usually can't do a big file with no mistakes and you are forced to check it frequently as you go. (Using a stream *editor* like sed as you go is a way out.) You see 'macro oriented form'. I see 'How am I going to be able to make this file tolerably readable?' A 'macro oriented form' in one piece of music might be a disaster in the next. Having the ability to do that sort of thing with simple substitution, I am still reluctant to do it, because IMHO .ly files are easier to understand if the user definitions are in them instead of in custom auxiliary user files. That would be true whether I used sly or indulged in 'scheme hacking'. So when doing an \override with a value by other means I will continue to define the \revert in the .ly file, and document the other means in the .ly file, because years from now I want to be able to understand what the hell I did. > Perhaps this is an item for the FAQ. It surely is. Information is not knowledge. Belief is not truth. Indoctrination is not teaching. Tradition is not evidence. David Raleigh Arnold [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: tab
I think you and I have a different idea of `macro'.
The problem with TeX, m4, YODL and metafont is that they are syntax
oriented and not function oriented. I'm too busy to formalise exactly
what I mean, but maybe this example explains what I mean
\def\foo{20}
\def\bar{20}
\def\bla{pt}
\hrule width\foo\bar\bla
TeX will do a string substitution, and instead of signaling an error
(wrong number of arguments in \HRULE), it will gladly replace \foo\bar
with 2020 and make a rule of 2020 points wide. The substitution
process has no notion of the meaning of tokens. There is no type
checking, scoping, there are no modules. In short, this will give you
a programming interface (yes, TeX also has loops, and if-then-else)
that is extremely sensitive to irrelevant naming and formatting
formatting details. It makes for hard to read and hard to debug code.
Most people will argue that they would parametrised definitions only
simple substitutions, and not get into these hairy programming
issues. I remain very skeptical: the moment there are parameters,
people will insist on having if-then. When there is if-then people
will want loops "to save repetitive entry". When we have loops and
if-then we have a turing complete language, but to make that usable,
people will demand lists and arrays. And so on, and all that time
that I spend reinventing the wheels of programming language design can
not be spent on improving the music formatter itself.
The notion of a macro language throws away 20 odd-years of research
that went into design of programming languages. I think it is a
tasteless idea, and I will not have it. There will not be a
macro-language in LilyPond as long as it has my name on it. If you
still want that, then you can fork LilyPond, or write a preprocessors
by yourself.
The whole idea of making code easier to type is based on the flawed
assumption that saving keystrokes will improve your efficiency. The
sad fact is that code is read much more often than it is written, and
therefore explicitness is good: it eases reading, and speeds up
debugging. Therefore, when in doubt, you should opt for the verbose
solution.
--
Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
forwarded message from noreply@sourceforge.net
The python bug that caused some problems when using Lilypond with
python 2.2 has been fixed.
--- Begin Message ---
Bugs item #604803, was opened at 2002-09-05 01:20
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=604803&group_id=5470
Category: Regular Expressions
Group: Python 2.2
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Han-Wen Nienhuys (hanwen)
Assigned to: Fredrik Lundh (effbot)
Summary: pre bug
Initial Comment:
Hi there,
I have an annoying bug with python 2.2 -- a workaround
is also appreciated.
Thanks.
blauw:~/usr/src/lilypond$ cat q.py
import pre
print pre.sub ('(@)', r'@\1', r"\key c \minor r8 c16 b
c8 g as c16 b c8 d | g,4 ")
blauw:~/usr/src/lilypond$ python2 q.py
Traceback (most recent call last):
File "q.py", line 4, in ?
print pre.sub ('(@)', r'@\1', r"\key c \minor r8
c16 b c8 g as c16 b c8 d | g,4 ")
File "/usr/lib/python2.2/pre.py", line 179, in sub
return pattern.sub(repl, string, count)
File "/usr/lib/python2.2/pre.py", line 344, in sub
return self.subn(repl, string, count)[0]
File "/usr/lib/python2.2/pre.py", line 366, in subn
repl = pcre_expand(_Dummy, repl)
TypeError: 'NoneType' object is not callable
blauw:~/usr/src/lilypond$ rpm -q python2
python2-2.2-16
--
>Comment By: Fredrik Lundh (effbot)
Date: 2002-09-09 16:27
Message:
Logged In: YES
user_id=38376
this has been fixed in CVS:
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/python/python/dist/src/Lib/pre.py.diff?
r1=1.10&r2=1.10.18.1
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=604803&group_id=5470
--- End Message ---
--
Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/
Re: tab
On Mon, 09 Sep 2002 13:33:41 Han-Wen Nienhuys wrote:
>
> I think you and I have a different idea of `macro'.
You must admit that it's a fairly inclusive word.
I think I should have said `identifier'.
All I mean is:
novobracket = {\property Staff.VoltaBracket = \turnOff}
If I have more than two staves, I'll do that *every
time*. I will make an identifier for anything that
has #' in it. That isn't building a new language, it it?
>
>
>
> The problem with TeX, m4, YODL and metafont is that they are syntax
> oriented and not function oriented. I'm too busy to formalise exactly
> what I mean, but maybe this example explains what I mean
>
> \def\foo{20}
> \def\bar{20}
> \def\bla{pt}
> \hrule width\foo\bar\bla
>
> TeX will do a string substitution, and instead of signaling an error
> (wrong number of arguments in \HRULE), it will gladly replace \foo\bar
> with 2020 and make a rule of 2020 points wide. The substitution
> process has no notion of the meaning of tokens. There is no type
> checking, scoping, there are no modules. In short, this will give you
> a programming interface (yes, TeX also has loops, and if-then-else)
> that is extremely sensitive to irrelevant naming and formatting
> formatting details. It makes for hard to read and hard to debug code.
\stemLength{4.5} or \\stemLength{4.5} is not going to kill
you, really, as long as it's in the .ly file.
\lilycommand{stemLength}{foofooraw #'foo = ##1}
\lilycommand{haha}[2]{foofooraw #'foo = ##1 foofoofooraw #'foo = ##2}
I've got to admit it looks nasty, but most of us would
do it in a heartbeat. The second is more trouble than
it's worth.
We just want to be able to pass a value to things already
identifiable. Of course lily would choke on a stem length
two inches long. So what? You are assuming that we are
total gluttons for punishment. 'Taint so.
Of course using the editing approach, the .ly file contains
all the long stuff and that is all lilypond sees, so debugging
is actually easier because it's easier to find the offending
line. That is the sly-ptfilter.sed approach. The disadvantage
to the user is that he has to put the value passing stuff
in ptfilter.sed.
> Most people will argue that they would parametrised definitions only
> simple substitutions, and not get into these hairy programming
> issues. I remain very skeptical: the moment there are parameters,
> people will insist on having if-then.
If they need it, they will have it. Why not try to see to it
that they don't need it instead of worrying about what they
are going to want next? And anyone with any sense at all
is going to have any if-then *write* lilypond syntax as
a product. That means having it in lilypond is
not an option.
> When there is if-then people
> will want loops "to save repetitive entry". When we have loops and
> if-then we have a turing complete language, but to make that usable,
> people will demand lists and arrays. And so on, and all that time
> that I spend reinventing the wheels of programming language design can
> not be spent on improving the music formatter itself.
This is not going to happen. I already pointed out to another
user, I thought that's who I was addressing anyway, how one
might make a tab2notation2tab program. It would make no sense
to do that with lilypond because it involves the writing of an
.ly part. It is insane to have files writing themselves.
It made no sense to have lilypond render chords either. If
it weren't so simple it would be a debugging nightmare, because
you don't have the .ly file with the written out chords in it
when you use it do you? A
separate program which took standard chord names, (which have
absolutely nothing to do with Harald Banter) and wrote guitar,
bass, midi, and lyrics parts (just pass the chord names through) for
inclusion in a .ly file would be a fun
toy, and one would not have to mess with Tex, LaTeX, C++, or
scheme to do it if he didn't want to, it could be
done with any language which could filter a textfile.
So IMHO you have already gone too far down the road of having
.ly files write themselves.
I don't set stem lengths because I *want* to, I do it because
I *must* to get acceptable output. It will be a long time
before lilypond can handle 3 parts on one staff without having
to massage the stems by hand. You force people to either have
a new identifier for each value or find other means, and other
means exist.
> The notion of a macro language throws away 20 odd-years of research
> that went into design of programming languages. I think it is a
> tasteless idea, and I will not have it. There will not be a
> macro-language in LilyPond as long as it has my name on it. If you
> still want that, then you can fork LilyPond, or write a preprocessors
> by yourself.
>
> The whole idea of making code easier to type is based on the flawed
> assumption that saving keystrokes will improve your efficiency. The
> sad fact is that code is read much more ofte
Can't achieve to compile lilypond 1.6.2 with gcc-3.2 and flex 2.5.4a
Hello,
I know it's pretty "bleeding-edge", but I have recently upgraded my
system to gcc-3.2 and encounter problems when trying to compile lilypond
1.6.2 (as expected after the reading of INSTALL.txt)...
So, I've followed the instructions given for gcc-3.1... :
I attache the log file...
Has anybody an idea (other than downgrading to gcc 2.95 ) ???
Thanks in advance,
Alex.
Script started on Mon Sep 9 18:02:31 2002
1001:root:/usr/src/lilypond-1.6.2# CONF=gcc-3.1 ./lexer-gcc-3.1.sh
Copying and fixing /usr/local/include/FlexLexer.h... done
Remove config.cache before rerunning ./configure
Reconfigure, refix, and make doing something like:
rm -f config.cache
CPPFLAGS=-I/usr/src/lilypond-1.6.2/lily/out-gcc-3.1 ./configure
--enable-config=gcc-3.1
CONF=gcc-3.1 ./lexer-gcc-3.1.sh
make conf=gcc-3.1
1002:root:/usr/src/lilypond-1.6.2# rm -f config.cache
1003:root:/usr/src/lilypond-1.6.2# CPPFLAGS=-I/usr/src/lilypond-1.6.2/lily/out-gcc-3.1
./conf<# CPPFLAGS=-I/usr/src/lilypond-1.6.2/lily/out-gcc-3.1 ./configure
--enable-config=gcc-3.1
creating cache ./config.cache
checking Package... LILYPOND
checking builddir... /usr/src/lilypond-1.6.2
checking for stepmake... ./stepmake (${prefix}/share/stepmake not found)
checking host system type... i686-pc-linux-gnu
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/sh
checking for python... python
checking for python... /usr/local/bin/python
checking for gcc... /usr/local/gcc/bin/gcc
checking whether the C compiler (/usr/local/gcc/bin/gcc -O6 -march=athlon-tbird -pipe
) works... yes
checking whether the C compiler (/usr/local/gcc/bin/gcc -O6 -march=athlon-tbird -pipe
) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether /usr/local/gcc/bin/gcc accepts -g... yes
checking for IEEE-conformance compiler flags... none
checking /usr/local/gcc/bin/gcc version... 3.2
checking for c++... /usr/local/gcc/bin/g++
checking whether the C++ compiler (/usr/local/gcc/bin/g++ -O6 -march=athlon-tbird
-pipe ) works... yes
checking whether the C++ compiler (/usr/local/gcc/bin/g++ -O6 -march=athlon-tbird
-pipe ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether /usr/local/gcc/bin/g++ accepts -g... yes
checking /usr/local/gcc/bin/g++ version... 3.2
checking whether explicit instantiation is needed... no
checking for ar... ar
checking for ranlib... ranlib
checking for bison... bison -y
checking for bison... bison
checking bison version... 1.28
checking for flex... flex
checking how to run the C++ preprocessor... /usr/local/gcc/bin/g++ -E
checking for FlexLexer.h... yes
checking language... English
checking for gettext in -lintl... yes
checking for gettext... yes
checking for msgfmt... msgfmt
checking for mf... mf
checking for inimf... inimf
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for tfm path... /usr/local/teTeX/share/texmf/fonts/tfm/public/cm
/usr/local/teTeX/share/texmf/fonts/tfm/ams/symbols
checking for guile-config... guile-config
checking guile-config version... 1.4
checking guile compile flags... -I/usr/local/include
checking guile link flags... -L/usr/local/lib -lguile -lm
checking for kpathsea/kpathsea.h... yes
checking for kpse_find_file in -lkpathsea... yes
checking for kpse_find_file... yes
checking whether to use kpathsea... yes
checking for makeinfo... makeinfo
checking whether makeinfo can split html by @node... yes
checking for python2.2/Python.h... yes
checking for python2.1/Python.h... no
checking for python2.0/Python.h... no
checking for python2/Python.h... no
checking for python/Python.h... yes
checking for python1.5/Python.h... no
checking for Python.h... no
checking for assert.h... yes
checking for sys/stat.h... yes
checking for sstream... yes
checking whether stat file-mode macros are broken... no
checking for 8-bit clean memcmp... no
checking for vprintf... yes
checking for memmem... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for gettext... (cached) yes
checking for isinf... yes
checking for guile... guile
checking for guile... /usr/local/bin/guile
checking for perl... perl
checking for perl... /usr/bin/perl
checking for pktrace... pktrace
checking pktrace version... 1.0.4
checking for makeinfo... (cached) makeinfo
checking makeinfo version... 4.2
updating cache ./config.cache
creating ./config.status
creating config-gcc-3.1.make
creating config-gcc-3.1.h
configuring in stepmake
running /bin/sh ./configure --enable-config=gcc-3.1 --cache-file=.././config.cache
--srcdir=.
loading cache .././config.cache
checking Package... Stepmake package!
checking builddir... /usr/src/lilypond-1.6.2/stepmake
checking host system type... i686-pc-linux-gnu
checking for gmake... (cached) make
checking for find... (cached) find
checking for tar... (cached) tar
checking for bash... (cached) /bin/sh
checking for python... (cached) py
Re: font (?) help request
Actually, there seem to be two workarounds: 1) use the lilypond-profile that comes with building from 1.6.2 source on Linux (this creates the TEXMF variable among other things) 2) use -P as you said, then convert separately to PDF. So, perhaps the cygwin installation needs to have those startup scripts added. I certainly didn't know about them until building from scratch. Alex Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > "Alex Langley" <[EMAIL PROTECTED]> writes: > > > I have searched in the archives and manual, I must be missing > > something when it comes to lyric and notehead fonts. Here's > > the situation: > > > > cygwin lilypond 1.6.0 ...I can get everything but the lyrics to > > show up. > > Try using ly2dvi -P (not -p), and use the postscript output, or > install tetex-base and tetex-extra too. > > > Any help will be much appreciated! > > You may also see this thread: > > http://mail.gnu.org/pipermail/lilypond-user/2002-August/002376.html > > > If it doesn't work, please post your ly2dvi --verbose output. > > Good luck, > Jan. > > -- > Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter > http://www.xs4all.nl/~jantien | http://www.lilypond.org > > > > ___ > Lilypond-user mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-user > ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
help
I would all documentation for the lilypond. I am the second director of the Conservatorio di Musica "G. Martucci" di Salerno, and I would editing the opera omnia of Martucci with lilypond, and the scores of the '700 and '800 of the composers of Neapols school's. I'm sorry for the low level of the my english... Francesco De Mattia, Vicedirettore del Conservatorio G. Martucci di Salerno ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
"Alex Langley" <[EMAIL PROTECTED]> writes: > Just want to report that using -P instead of -p solved both > the problem of no lyrics in Lilypond on Cygwin (1.6.0), and > no note heads in Lilypond (1.6.2) on Redhat. Ok. In that case you probably have an installation problem on Red Hat Linux. PDF on windows has not been tested very well. > Can -p (going all the way to PDF) be fixed by creating the > proper fonts? They should be available, ie, there should be nothing 'to fix' on Linux. Did you build LilyPond yourself? Did you build and install the pfa fonts? Maybe we need better instructions for this. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
"Alex Langley" <[EMAIL PROTECTED]> writes: > Actually, there seem to be two workarounds: > > 1) use the lilypond-profile that comes with building from 1.6.2 source > on Linux (this creates the TEXMF variable among other things) > 2) use -P as you said, then convert separately to PDF. > > So, perhaps the cygwin installation needs to have those > startup scripts added. Cygwin does have those startup scripts, in the same place as Red Hat has. Could you investigate why they don't get executed when you start your Cygwin bash shell? > I certainly didn't know about them until building from scratch. If you install the rpm you may not notice those scripts, but they do get installed. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: help
francesco de mattia <[EMAIL PROTECTED]> writes: > I would all documentation for the lilypond. You just want to read the documentation, as a user? To learn using LilyPond, the tutorial: http://lilypond.org/stable/Documentation/user/out-www/lilypond/Tutorial.html The user manual: http://lilypond.org/stable/Documentation/user/out-www/lilypond/lilypond.html And you can download both here: http://lilypond.org/stable/out/web.tar.gz > I am the second director of the Conservatorio di Musica > "G. Martucci" di Salerno, and I would editing the opera omnia of > Martucci with lilypond, and the scores of the '700 and '800 of the > composers of Neapols school's. That's quite ambitious. It will be a lot of work! > I'm sorry for the low level of the my english... No problem. If I did not understand you correctly, maybe another Italian LilyPond user can help you better. Greetings, -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > "Alex Langley" <[EMAIL PROTECTED]> writes: > > Can -p (going all the way to PDF) be fixed by creating the > > proper fonts? > > They should be available, ie, there should be nothing 'to fix' on > Linux. Did you build LilyPond yourself? Did you build and install > the pfa fonts? Maybe we need better instructions for this. Yes, I built LilyPond 1.6.2, guile, python, etc. myself. I did not create the PFA fonts. I will go back and look for the instructions for doing that as I must have missed them. I recall something appearing after the "make", which I should have copied and pasted so that the manual instructions didn't go up and off the screen as they did. Would not "make install" handle this or at least instruct the builder". Alex ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > "Alex Langley" <[EMAIL PROTECTED]> writes: > > > Actually, there seem to be two workarounds: > > > > 1) use the lilypond-profile that comes with building from 1.6.2 source > > on Linux (this creates the TEXMF variable among other things) > > 2) use -P as you said, then convert separately to PDF. > > > > So, perhaps the cygwin installation needs to have those > > startup scripts added. > > Cygwin does have those startup scripts, in the same place as Red Hat > has. Could you investigate why they don't get executed when you start > your Cygwin bash shell? I definite don't seem them in the same place as on my Red Hat box. I see only lilypond-profile.sh at /etc/profile.d/lilypond-profile.sh which is a little "diff"erent from that generated on my Red Hat box. > > > I certainly didn't know about them until building from scratch. > > If you install the rpm you may not notice those scripts, but they do > get installed. I built from source. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
I guess I still don't understanding (judging from the mktexpk commands I see from ly2dvi --verbose) why -P tells it to use a 600 dpi device ljfour, but -p tells it to use an 8000 dpi device: kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 --dpi 8000 cmbx10 mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. mktexpk: Can't guess mode for 8000 dpi devices. mktexpk: Use a config file, or update me. kpathsea: Appending font creation commands to missfont.log. dvips: Font cmbx10 not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 --dpi 8000 cmr10 mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. mktexpk: Can't guess mode for 8000 dpi devices. mktexpk: Use a config file, or update me. dvips: Font cmr10 not found, characters will be left blank. Do I really have to generate an 8000 dpi set of fonts just to get PDF files from dvips -Ppdf? If so, could you kindly point me at the exact instructions for doing that? Alex ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: font (?) help request
"Alex Langley" <[EMAIL PROTECTED]> wrote: > Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > > They should be available, ie, there should be nothing 'to fix' on > > Linux. Did you build LilyPond yourself? Did you build and install > > the pfa fonts? Maybe we need better instructions for this. > > Yes, I built LilyPond 1.6.2, guile, python, etc. myself. > > I did not create the PFA fonts. I see the problem. I did not have pktrace or mftrace installed, so make pfa-fonts didn't work. I recall during "./configure" that it was "Suggested" to have these, but not "Required". Perhaps if ./configure was a stubborn about these as python and guile? So, I think all the issues are now resolved! Off to learning more about lilypond. Thanks a lot for your patient assistance! Alex ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: tab
[EMAIL PROTECTED] writes: > We just want to be able to pass a value to things already > identifiable. Of course lily would choke on a stem length > two inches long. So what? You are assuming that we are > total gluttons for punishment. 'Taint so. You have the perspective of a well-behaved user. I have the perspective of the developer that gets to deal with the bugreports of other users, and has to watch the reputation of LilyPond in general. Since you are still arguing over this, I'll give you the quick summary: I think it is a bad idea. I'm not going to do it, and I'm not going allow it. Discussion closed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
