Re: lilypond-book on windows
Graham Percival gra...@percival-music.ca writes: On Thu, Jan 12, 2012 at 07:00:27PM +0100, David Kastrup wrote: Reinhold Kainhofer reinh...@kainhofer.com writes: However, even for HTML we need some kind of line width so that we can line-break all lilypond snippets. That line width should be based on a pixel width (1024 is probably reasonably). It is nonsensical to have it based on a paper size. We want the line widths to look the same in the HTML as in the pdfs. Why? Also, we don't want to insist that people use a full-screen window with at least 1024 pixels -- or rather, given the left-hand navbar, that would require at least a full-screen window at 1280 pixels or so. So make a different HTML-related decision. If lilypond-book calls texi2pdf in the course of generating HTML, that is a bug. No, that is correct and working as desired. Why would that be desirable? Why should the HTML documentation be made to look different on a system with a different paper width setting for PDF? That does not make sense. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book -2
On Thu, Jan 12, 2012 at 09:02:51AM -, Trevor Daniels wrote: IOError: (0, 'Error') Lilypond-book returned code 1 Thanks, working on fixes. As a cheap experiment, could you add this: ### EXPERIMENTAL HACK: see if this makes mingw behave better? time.sleep(1) immediately between the proc = ... and (parameter_string, error_string) = proc.communicate () lines? oh, and add: import time somewhere near the top of the file. I don't expect it to work, so I'm writing a more intrusive hack to hopefully avoid this... but I'd be delighted to junk the larger hack if that can make it work. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Undefined references in translated manuals (issue 2220). (issue 5539052)
Some of these changes are already pushed. I could kiss myself.
http://codereview.appspot.com/5539052/diff/1/Documentation/es/extending/scheme-tutorial.itely
File Documentation/es/extending/scheme-tutorial.itely (right):
http://codereview.appspot.com/5539052/diff/1/Documentation/es/extending/scheme-tutorial.itely#newcode888
Documentation/es/extending/scheme-tutorial.itely:888: usaríamos
@ref{Funciones de Scheme vacías}, o lo almacenaríamos en un
This change is already pushed in the lilypond/translation branch, commit
30d5b6092
http://codereview.appspot.com/5539052/diff/1/Documentation/es/notation/rhythms.itely
File Documentation/es/notation/rhythms.itely (right):
http://codereview.appspot.com/5539052/diff/1/Documentation/es/notation/rhythms.itely#newcode3120
Documentation/es/notation/rhythms.itely:3120: ensayo, consulte
@ref{Indicaciones de texto}. Para un control más
My commit 30d5b60 includes a change here as well to fix a wrong xref
(not sure if it was a broken xref).
http://codereview.appspot.com/5539052/diff/1/Documentation/es/notation/rhythms.itely#newcode3122
Documentation/es/notation/rhythms.itely:3122: @ref{Alineación de
objetos}.
This is new, I missed it.
http://codereview.appspot.com/5539052/diff/1/Documentation/es/notation/rhythms.itely#newcode3129
Documentation/es/notation/rhythms.itely:3129: @ref{Alineación de
objetos}.
Already pushed. See 30d5b609 in lilypond/translation branch. I guess
Git will smartly merge both change sets.
http://codereview.appspot.com/5539052/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book -2
On Fri, Jan 13, 2012 at 08:41:14AM +, Graham Percival wrote: I don't expect it to work, so I'm writing a more intrusive hack to hopefully avoid this... but I'd be delighted to junk the larger hack if that can make it work. sorry, ignore that. I'm building a new binary with a better fix, and should have it uploaded in 10 minutes. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond-book 3
I believe that this should work out of the box on any windows computer which does **NOT** have texi2pdf or texi2dvi installed. http://lilypond.org/~graham/lilypond-2.15.25-3.mingw.exe Trevor, if you have latex set up, you may wish to test it with a different user account (if you didn't install latex system-wide), or otherwise temporarily rename the texi2pdf.exe executable. To see if it's doing the right thing, add a print DEBUG: , executable_found between lines 209 and 210 of the new book_texinfo.py file. On the console, you want to see DEBUG: None. If that works, then I'll merge the dev/lilypond-book-windows branch so we have a good baseline, and then I'll continue to investigate the problems in popen.communicate() - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Build: Top-level GNUmakefile (issue 5535047)
LGTM http://codereview.appspot.com/5535047/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Web: Added Concert to Introduction.itexi (issue 5543044)
LGTM, please push directly to staging. http://codereview.appspot.com/5543044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add a node prefix to snippets, preventing duplicate node errors (issue 2221). (issue 5541050)
I had tried this very approach a while ago, but there were some problems. Unfortunately, I can't remember which problems I encountered. One issue might be that all links to one particular snippet will be broken with that patch. If you don't encounter any problems with broken links etc., then I'm fine with the patch. http://codereview.appspot.com/5541050/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc search: update to version 2.15, use it in the site: part (issue 5530043)
Pavel, This patch has been approved and pushed. committer James Lowe pkx1...@gmail.com Fri, 13 Jan 2012 11:54:08 + (11:54 +) commit 427bb2b004227f3afc7de10dfd896fc375cbc320 Please can you close this Rietveld issue? Thank you for your patch. James http://codereview.appspot.com/5530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Undefined references in translated manuals (issue 2220). (issue 5539052)
On 13 January 2012 08:42, paconet@gmail.com wrote: Some of these changes are already pushed. I could kiss myself. can I kiss someone? Hey perhaps we need a Kissmeister... any takers? Janek? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book -2
Graham, you wrote Friday, January 13, 2012 8:41 AM As a cheap experiment, could you add this: ### EXPERIMENTAL HACK: see if this makes mingw behave better? time.sleep(1) immediately between the proc = ... and (parameter_string, error_string) = proc.communicate () lines? oh, and add: import time somewhere near the top of the file. Gives the same error: Traceback (most recent call last): File c:/program files/lilypond/usr/bin/lilypond-book.py, line 739, in ? main () File c:/program files/lilypond/usr/bin/lilypond-book.py, line 722, in main chunks = do_file (files[0]) File c:/program files/lilypond/usr/bin/lilypond-book.py, line 595, in do_fil e global_options.formatter.init_default_snippet_options (source) File c:\program files\lilypond\usr\share\lilypond\current\python\book_texinfo .py, line 292, in init_default_snippet_options texinfo_defaults = get_texinfo_width_indent (source, self.global_options); File c:\program files\lilypond\usr\share\lilypond\current\python\book_texinfo .py, line 226, in get_texinfo_width_indent time.sleep(1) IOError: (0, 'Error') Lilypond-book returned code 1 Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc search: update to version 2.15, use it in the site: part (issue 5530043)
I don't think I can close this. I see gray Can't Edit over Publish+Mail Comments. I tried adding my gnu.org address as an alias in gmail but it changed nothing. Sorry for not being able to participate more in the discussion! http://codereview.appspot.com/5530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc search: update to version 2.15, use it in the site: part (issue 5530043)
On 2012/01/13 16:56:54, Pavel Roskin wrote: I don't think I can close this. That is quite correct -- James Lowe owns this issue, so only he can close it. http://codereview.appspot.com/5530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Undefined references in translated manuals (issue 2220). (issue 5539052)
2012/1/13 James pkx1...@gmail.com: On 13 January 2012 08:42, paconet@gmail.com wrote: Some of these changes are already pushed. I could kiss myself. can I kiss someone? Hey perhaps we need a Kissmeister... any takers? Janek? I'm not pretty, so i guess no :P Thanks for your work, Julien! I'm inspired. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book 3
On Fri, Jan 13, 2012 at 09:02:21AM +, Graham Percival wrote: I believe that this should work out of the box on any windows computer which does **NOT** have texi2pdf or texi2dvi installed. http://lilypond.org/~graham/lilypond-2.15.25-3.mingw.exe Colin has tested this and found a problem, which I will be fixing and uploading a new version in about 12 hours. There's no point having any further tests of this until I've uploaded 2.15.25-4. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book 3
Sorry for the late response - my mail provider lost one of his RAID drives this morning, so I had no mail for some hours. Graham, you wrote Friday, January 13, 2012 9:02 AM I believe that this should work out of the box on any windows computer which does **NOT** have texi2pdf or texi2dvi installed. http://lilypond.org/~graham/lilypond-2.15.25-3.mingw.exe Correct. It outputs No executable found and says it's unable to auto-detect default settings if I rename texi2pdf.exe. Trevor, if you have latex set up, you may wish to test it with a different user account (if you didn't install latex system-wide), or otherwise temporarily rename the texi2pdf.exe executable. To see if it's doing the right thing, add a print DEBUG: , executable_found between lines 209 and 210 of the new book_texinfo.py file. On the console, you want to see DEBUG: None. Yup, I do. If texi2pdf.exe is found then we run into the usual sleep problem in threading.py, of course. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: suggestion - increase default beam thickness
On Tue, 10 Jan 2012 22:36:41 +0100 Janek Warchoł janek.lilyp...@gmail.com wrote: Good point, your concerns are valid. However, the difference between current Lily default beam thickness and average calculated from samples is so big (almost 0.1 staffspace), that i think we don't have to worry about this. Also, the change i suggest is small - only 0.03 staffspace thicker. You may want to go all the way to the measured values if your measurement are based on valid methods. Even thickness of 0.6 looks reasonable to my eyes. But what really matters is the eyes of musicians, and I'm not one (even though I'm taking voice lessons). Of course, i invite you all to print Lily-engraved scores with default settings and with beam thickness changed to 0.51. I only want to warn you that these results might be prone to similar problems: when some time ago i compared a printout of Lily-made pdf with an older printout, i was surprised to see significant difference in thickness of everything (i estimate it was something like 0.04-0.06 ss). And both copies were printed with the same printer, the only difference was the cartridge! Thicker beams look better for me, both on screen and when printed. -- Regards, Pavel Roskin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc search: update to version 2.15, use it in the site: part (issue 5530043)
On 2012/01/13 16:59:47, Graham Percival wrote: On 2012/01/13 16:56:54, Pavel Roskin wrote: I don't think I can close this. That is quite correct -- James Lowe owns this issue, so only he can close it. Sorry, I didn't realise I had the Rietveld as well. Closed. http://codereview.appspot.com/5530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
