Re: documentation link to big page broken
This link has been broken for a few days: http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page OK I am sorry, I did not read the message of Firefox. It says there is an encoding problem: In French: Erreur d'encodage de contenu. La page que vous essayez de voir ne peut être affichée car elle utilise un type de compression invalide ou non supporté. In English: Content encoding error. The page you try to look at cannot be displayed because it uses an invalid or unsupported type of compression No problem with IE 6.0, only FireFox 3.06 refuses to show the big page. Please do not tell me I have to go back to IE! Help! Frédéric Bron ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Shouldn't the ambitus engraver prefer his key signature?
Anthony W. Youngman lilyp...@thewolery.demon.co.uk writes: In message 863aeipe74@lola.quinscape.zz, David Kastrup d...@gnu.org writes Hi, the ambitus engraver seemingly picks the first maximum/minimum in the note sequence and stays with it even when the same absolute pitch comes up later with a better match to the ambitus engraver's key signature. Here is a real world example where the ambitus engraver (which is working in C major) picks c flat rather than b as its lowest span. Ugly. Not that I use ambituses, but surely, where there multiple notes of the same pitch (I hate to say absolute pitch, because to take the above example c-flat and b-natural are NOT the same pitch except on the piano), Ambitus engravings are for expressing physical limits. I can't think of a tuning/instrument where enharmonic relations could make a difference. it makes sense to take the lowest (or highest, as appropriate) note - b over c. No. The ambitus should definitely orient itself with its key signature: it makes no sense using accidentals when a natural pitch is there. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building GUB3
On za, 2009-02-14 at 02:59 +0100, John Mandereau wrote:
Hi John,
I have a (proably simple) problem with current HEAD for building
librestrict, which may be trivial
but which I couldn't fix quickly myself:
Tried a couple of things but could not reproduce this.
What's the command you issued? Can you try removing the
root and any librestrict/make packages:
rm -rf target/tools/root
rm target/tools/packages/{make,librestrict}*
Jan.
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John, John Mandereau john.mandereau at gmail.com wrote: How did you set the execution bit? Have you used a Windows machine or some non-Unix filesystem? Yes, I mount a NTFS from Linux. I have installed both of Windows and Linux into one machine. I edit text on Windows (because my favorite text editor is available only on Windows), then reboot my machine to boot Linux and compile LilyPond documents on it (because I could not build LilyPond on cygwin. In fact, I spent a day to try building LilyPond on cygwin, but I could not do it). This way is really troublesome. I am seriously thinking to buy another machine. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
On Sat, Feb 14, 2009 at 1:24 PM, Sawada, Yoshiki sawada.yosh...@gmail.com wrote: How did you set the execution bit? Have you used a Windows machine or some non-Unix filesystem? Yes, I mount a NTFS from Linux. I have installed both of Windows and Linux into one machine. I edit text on Windows (because my favorite text editor is available only on Windows), then reboot my machine to boot Linux and compile Doesnt it run under Wine? -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John, John Mandereau john.mandereau at gmail.com wrote: 1. Release of the new patch for ja doc OK, I applied your patch, but made further fixes in the source, and made comments at the end of this email. I thank you for your work. 2. About .po file The simplest way I can see is to disable translation of variable names in Japanese documentation, which I just did in lilypond-book and langdefs. Please check if it works. It does not work. But I fixed Lilypond-book.py as following: (line 939) if not langdefs.LANGDICT[document_language].enable_ly_identifier_l10n: ^^^ I guess the property name enable_ly_identifier_l10n should be changed to disable_ly_identifier_l10n. ^^^ 3. About Building documentation without compiling LilyPond of 1.2.4 Building documentation, Application Usage nice is not needed, that's a Grahamism, but I think it's not a problem if it remains there, I'd expect people who run this command with no knoweledge of nice comand to do man nice There are other variations of this command (e.g. using -j make flag)... it's not possible to list all possibilities in the compilation documentation. I just think commands which are not needed should not be included. They may cause confusions. Now, I have another question about LilyPond documents. Thus, I will make a new thread about them. @untranslated in Documentation/ja/user/converters.itely are right, but this file shouldn't contain the English translation, so I removed it. I am sure. I have one question about this. Should I include untranslated texinfo files into patches? For example, I am translating Learning Manual, but do not start to translate rhythms.itely yet. Should I include rhythms.itely into Documentation/ja/user/ for patches? In fact, I can do make web only with lilypond.tely, notation.itely and pitches.itely. Also, the Japanese texidoc in input/lsr/piano-template-simple.ly is missing in input/texidocs, It is a my fault. I will include it into the next patch. and you may want to translate snippet titles as well, writing them in doctitleja header fields. Thank you for your advice. I add doctitleja fields to snippet files. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: What's up with the Frogs?
2009/2/13 Graham Percival gra...@percival-music.ca: Since I've been doing /such/ a good job keeping up with my lilypond duties, I figured I'd have the moral authority to bug others. Like you needed any authority to bug someone :) Valentin (since you're French and I have no shame ;) what's up with the Report? And the bug-lilypond backlog? IIRC your opera started almost two weeks ago. Aye aye, sir! Yeah, I'm slowly recovering (and I haven't had any decent connection until yesterday). The new Report site is nearly ready, and the next issue is almost complete (it has been so for 7 months). As for the bugs thing, I have finally fixed my laptop this afternoon so there's a good chance I'm not far away from being 100% functional :) Regards, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation link to big page broken
2009/2/14 Frédéric Bron frederic.b...@m4x.org: This link has been broken for a few days: http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page OK I am sorry, I did not read the message of Firefox. It says there is an encoding problem: In French: Erreur d'encodage de contenu. La page que vous essayez de voir ne peut être affichée car elle utilise un type de compression invalide ou non supporté. In English: Content encoding error. The page you try to look at cannot be displayed because it uses an invalid or unsupported type of compression No problem with IE 6.0, only FireFox 3.06 refuses to show the big page. Please do not tell me I have to go back to IE! Help! You don't, but Does Anybody Else Have This Problem? -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation link to big page broken
This link has been broken for a few days: http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page OK I am sorry, I did not read the message of Firefox. It says there is an encoding problem: In French: Erreur d'encodage de contenu. La page que vous essayez de voir ne peut être affichée car elle utilise un type de compression invalide ou non supporté. In English: Content encoding error. The page you try to look at cannot be displayed because it uses an invalid or unsupported type of compression No problem with IE 6.0, only FireFox 3.06 refuses to show the big page. Please do not tell me I have to go back to IE! Help! You don't, but Does Anybody Else Have This Problem? I have googled a bit and found other people having the same problem with FireFox 3. Often many people have no problems and some have problems. There is an easy workaround: Ctrl+F5! It worked for me. Thanks, Frédéric Bron ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building GUB3
Hi Jan, On Fri, Feb 13, 2009 at 11:06:28PM +0100, Jan Nieuwenhuizen wrote: I finally cooked-up a patch for that, it took a bit more work than I imagined. With latest GUB3 you can do LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond This will disallow libtool to read from or stat in /, so this should (from target/mingw/log/build.log) give us a clue why libtool reads from /usr/lib on your machine. Oh, this will trigger a full rebuild ;-) I decided to start completely from scratch with `make lilypond' to see if I could reproduce the current libtool issue, but I ran into some other problems. I will revisit this issue soon. The problem I am having is that fontconfig, ghostscript, guile, and lilypond are not downloaded! Directories such as downloads/fontconfig, downloads/lilypond, etc. are not even created at the start of the build process. This is resulting is all sorts of ugly errors like the following: /bin/sh: line 0: cd: /home/pnorcks/git/gub/downloads/lilypond: No such file or directory read_pipe failed: cd /home/pnorcks/git/gub/downloads/lilypond git show git.sv.gnu.org/lilypond.git/master:VERSION Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation link to big page broken
Frédéric Bron wrote: Ctrl+F5! this just means Reload (override cache) and it is important - if the previous load was broken - to make a real reload, not only from cache [simply F5] (which is a locally stored copy of a website). -- View this message in context: http://www.nabble.com/documentation-link-to-big-page-broken-tp21970706p22017317.html Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building GUB3
On Sat, Feb 14, 2009 at 1:42 PM, Patrick McCarty pnor...@gmail.com wrote: Hi Jan, On Fri, Feb 13, 2009 at 11:06:28PM +0100, Jan Nieuwenhuizen wrote: I finally cooked-up a patch for that, it took a bit more work than I imagined. With latest GUB3 you can do LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond This will disallow libtool to read from or stat in /, so this should (from target/mingw/log/build.log) give us a clue why libtool reads from /usr/lib on your machine. Oh, this will trigger a full rebuild ;-) I decided to start completely from scratch with `make lilypond' to see if I could reproduce the current libtool issue, but I ran into some other problems. I will revisit this issue soon. The problem I am having is that fontconfig, ghostscript, guile, and lilypond are not downloaded! Directories such as downloads/fontconfig, downloads/lilypond, etc. are not even created at the start of the build process. This is resulting is all sorts of ugly errors like the following: /bin/sh: line 0: cd: /home/pnorcks/git/gub/downloads/lilypond: No such file or directory read_pipe failed: cd /home/pnorcks/git/gub/downloads/lilypond git show git.sv.gnu.org/lilypond.git/master:VERSION Just to follow up, there are *many* errors in build.log. Most of them occur during the configure stage of tools::make. They all look like this: ERROR: ld.so: object '/home/pnorcks/git/gub/target/tools/root/usr/lib/librestrict.so' from LD_PRELOAD cannot be preloaded: ignored. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building GUB3
Jan Nieuwenhuizen a écrit : Tried a couple of things but could not reproduce this. What's the command you issued? Can you try removing the root and any librestrict/make packages: I get the error I reported when running rm -rf target make -f lilypond.make bootstrap Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
links in LSR snippets
LSR files sometimes refer to the manual. Example:
makam-example.ly:
(see the `Learning Manual @version{}, 4.6.3 Other sources of
information' for the location of this file)
Such references to absolute section numbers are error-prone;
additionally, there is no proper hyperlink. Any idea how to do
better?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
