Re: Please fix: japanese doc compilation
> There are many LilyPond users in Japan and they need information > about LilyPond in Japanese. I want them to join to LilyPond > community without hesitating. They are solving their problems > individually. Since there is such a great number of Japanese LilyPond users not fluent of English, it would be most important to create a `central' Japanese lilypond user forum, with one or more guys who forward more difficult questions to the English mailing lists (as it is already done for the German and French user forums) and translate the answers back into Japanese -- people like you, for example. In case people hesitate to write bad English: We don't care! lilypond code is universal :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: Lilypond on Macports
Anfang der weitergeleiteten E-Mail: Von: Josh Parmenter Datum: 25. Januar 2009 01:55:07 MEZ An: "James E. Bailey" Betreff: Re: Lilypond on Macports I had it fail here: /usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o 1/lib -L/opt/local/ lib ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../ type1/libtype1.a -L/usr/X11R6 -L/usr/X11/lib -lXaw -lXmu -lXt -lSM - lICE -lXp -lXext -lXpm -lintl -lc -lX11 -lXau -lXdmcp -liconv ../ kpathsea/.libs/libkpathsea.a -lm i686-apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory make[2]: *** [xdvi-xaw.bin] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 Error: The following dependencies failed to build: mftrace texlive texlive_base Error: Status 1 encountered during processing. Ringo:~ joshp$ intel MacBook Pro, os x 10.5.6 Best, Josh On Jan 24, 2009, at 4:08 PM, James E. Bailey wrote: Am 25.01.2009 um 00:53 schrieb Josh Parmenter: Hi David, I'm running it right now on a newer mac intel, and am noticing tons of xorg stuff... is this for the GUI? Does the regular X11 not cover these dependencies? It's for fontforge. If you look at the depencies (and the dependencies of depencies) all of the Xorg libraries are dependencies for fontforge. It's one of the downsides of macports. If you compile it yourself, you actually don't need all of those. At least, I didn't when I did. Thanks for doing this! Josh On Jan 24, 2009, at 3:27 PM, Jonathan Kulp wrote: David Baumgold wrote: I'm a big fan of Macports, and since lilypond seems to be so difficult to compile, I figured I would try to write a portfile for it, to make compiling easier for everyone. After about a week's work of research and many, many failed attempts, I finally have a portfile that seems to work. Can people test this portfile to verify that lilypond builds correctly? And if it reliably does so, can this information be put on the lilypond download page? To compile lilypond using Macports, first make sure you have XCode installed. Then just download Macports from http:// www.macports.org/ and install it, add /opt/local to your PATH, and then run "sudo port install lilypond". That's it. Macports will download, compile, and install lilypond and its dependencies. Also, I have not yet tested the GUI option in lilypond. To try building it, run "sudo port install lilypond +gui" instead of just "sudo port install lilypond". If it works, great -- if it doesn't, can people post their error messages? David, Thanks for doing this. It's a very good idea! I just tried it and it failed when building pango. It said my Xcode is too old (2.0) and that I need to update to at least 2.4.1. This is an eMac G4 that's about 4 years old. I have an Intel iMac on my desk at work, though, so I'll try it there, too. It's a much newer machine and the Xcode tools are probably up-to-date. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ** /* Joshua D. Parmenter http://www.realizedsound.net/josh/ “Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ** /* Joshua D. Parmenter http://www.realizedsound.net/josh/ “Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Directory name of aux is invalid
Hi,
On Sun, 25 Jan 2009, Paul Scott wrote:
> dem...@suffolk.lib.ny.us wrote:
>
> > On Tue, Jan 6, 2009, Trevor Daniels said:
> >
> > > The names are case-insensitive, and they cannot be used as directory
> > > names or the first part of a filename (the bit before the dot).
> >
> > please note, in DOS (and many of its contemporary file systems), what
> > users think of as the filename is not actually a ten character field
> > but in fact two seperate entitys, the name (6 characters), and a 3
> > character extension.
>
> It's actually (at least in DOS) an 8 character name and a 3 character
> extension and I'm not sure I can agree about the two separate entities
> part.
>From http://en.wikipedia.org/wiki/File_Allocation_Table#Directory_table I
see that it is indeed 8.3, and that the extension must be at a certain
offset, so in a way, name and extension _are_ separate.
Regarding the original issue ("aux" as a file/directory name) AFAIR if you
specify the absolute path, there are absolutely no problems. Which means
that you _can_ have entities with that name, you just have problems
accessing them.
Ah, the ways we have to _bend_ over for this stupid outdated operating
system!
Ciao,
Dscho
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Chord Naming
Original-Nachricht
> Datum: Sat, 24 Jan 2009 08:10:15 -0700
> Von: "Carl D. Sorensen"
>Not quite. I want to make a facility that makes it easy for everyone to
>create their favorite way, if one of the defaults isn't what is wanted. And
>dolmetsch.com just provides a list of the predefined chords. Any extra
>chords would have to be defined by the user.
Ok, now I get it.
I'd still prefer chord symbols independent from other contexts since I never use
Fretboards, but I get your point that it's probably just me and wouldn't make
sense for the majority.
Whatsoever, your proposal 'is' an improvement to the current system. :)
>This is hard for me to understand. Do you mean that in a jazz leadsheet, if
>the chord symbol says G7alt. the musician is free to choose any of the
>options you present?
Yes.
There are even more complex variations, especially in bebop.
If you transcribed the bass from a bebop recording you'd be surprised by the
amount of non-diatonic notes.
>Since all you want is text, the Lyrics method works. And you would be able
>to continue to use it under my proposal.
I was never worried it wouldn't. :)
>The same is true under my proposal. Exceptions (I don't really like the
>term; I'd prefer to just call them chord names) are stored as different
>characters, and one only had to learn to display them once. And if one has
>additional chord names that are not
Uhm, I just picked the term because I read it somewhere in the docs, I don't
like it either. Variations would be more appropriate I think.
>Thanks for the feedback, and for the offer of help,
Thanks to you for tackling this topic.
When I started using LilyPond the chord symbols were the main problem for me,
because nothing seemed logical to me. There's no standardized way of writing
chord symbols but there are some generally known variations in the jazz world.
Your proposal seems the right way to me to make this variations better
accessible. I think I'll still stick to my own way (mainly because I don't like
the chord symbols font to much) but it'll definitely make things easier for new
users.
Now I've got a question which is slightly off-topic.
This thread got me inspired to give scheme another try (everytime I tried to do
something with scheme before it'd never work).
I am trying to create a music function that makes it possible to transpose chord
symbols by my means. My initial idea was a function that takes two arguments,
ly:music and string, i.e. the transposable root and the fixed suffix, which
returns then a converted string of both arguments.
For example:
\c c1 #"m7" -> "Cm7"
\transpose c d { \c c1 #"m7" } -> "Dm7"
I am trying to go there step by step, but now I got already an error and don't
know why.
#(define (root-name music)
(let ((p (ly:music-property music 'pitch)))
(if (ly:pitch? p)
(let ((n (ly:pitch-notename p)))
if (number? n)
(number->string n)
c = #(define-music-function (parser location pitch) (ly:music?)
(let ((rn (root-name pitch)))
#{ \mark \markup { $rn } #}))
\new Staff { c'1 \c c'1 c'1 }
What I am trying so far is to convert the notename from a pitch to a string and
to display it. It won't work though and hopefully you or someone else can help
me locate the error here, so that I can continue learning scheme.
What still troubles me most is the usage of ly: -functions I guess.
The same architecure with standard scheme data-types works.
Regards,
Tao
--
Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond on Macports
Am 24.01.2009 um 23:18 schrieb David Baumgold: I'm a big fan of Macports, and since lilypond seems to be so difficult to compile, I figured I would try to write a portfile for it, to make compiling easier for everyone. After about a week's work of research and many, many failed attempts, I finally have a portfile that seems to work. Can people test this portfile to verify that lilypond builds correctly? And if it reliably does so, can this information be put on the lilypond download page? To compile lilypond using Macports, first make sure you have XCode installed. Then just download Macports from http:// www.macports.org/ and install it, add /opt/local to your PATH, and then run "sudo port install lilypond". That's it. Macports will download, compile, and install lilypond and its dependencies. Also, I have not yet tested the GUI option in lilypond. To try building it, run "sudo port install lilypond +gui" instead of just "sudo port install lilypond". If it works, great -- if it doesn't, can people post their error messages? So you can report it to the maintainer, mww, tcl fails its checksum check. ---> Verifying checksum(s) for tcl Error: No checksum set for tcl8.5.6-src.tar.gz Error: No checksum set for tcl8.5.6-src.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
