Re: Good luck, Valentin
> The name is "Affaire étrangère"; how would you translate it, Valentin? :-) "Foreign affair" surely sounds odd :-) Arthur ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Invalid overrides in ly/gregorian.ly?
Patrick McCarty wrote Sunday, February 01, 2009 11:27 PM On Sat, Jan 31, 2009 at 1:11 PM, Trevor Daniels wrote: It looks like extra-X-extent and extra-Y-extent were removed from the calculation of a grob extent in lily/grob.cc by committish c9b87b059ea73d9adb2b416e30c78e9340af8af2. This is dated 21 Oct 2005, so these properties have been ineffective for quite a while! I can't find them used anywhere else. These two properties definitely do not work anymore, and removing the overrides in ly/gregorian.ly don't affect any of the examples in NR 2.8 The extra-spacing-width/height properties seem to do much the same as extra-X/Y-extent used to do. This *seems* to be true, but since extra-spacing-width/height belong to the item-interface, and extra-X/Y-extent belong to the grob-interface, I'm a little skeptical that the two sets of properties are related. The difference between the item-interface and grob-interface is that the item-interface is used only by grobs with a definite shape, so it's not used, for example, by spacing or alignment grobs. But it does need to be checked and documented properly. At this stage I agree we can't simply convert one to the other. I think we should just remove the properties and add a convert-ly rule, but I'm not sure how to write this sort of rule. Not often are grob properties *removed* from LilyPond without being replaced by another property. :-) Agreed. We can't code a rule to fix extra-X/Y-extent automatically, so the rule should just issue a warning message which simply says this property is no longer in use and suggests extra-spacing-width/height might be an alternative. -Patrick Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: phrasing slur continued through a repeat?
This reminds me, I still haven't heard anything from my feature request on -devel on this topic. Anyone? http://lists.gnu.org/archive/html/lilypond-devel/2008-12/msg00403.html http://lists.gnu.org/archive/html/lilypond-devel/2008-12/msg00404.html - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Japanese translations
Hello Carl, Carl D. Sorensen byu.edu> wrote: > I found a place in ja/user/fundamentals.itely where a line ended in @c c, > which caused make web to fail. I fixed it and pushed a patch to git, so > it's taken care of now. Thank you for your pointing my mistake. Thanks to you, I got the opportunity to check all of my TexInfo files. > But I was curious that you ended each line of the japanese translation with > @c, presumably so that you would prevent your editor from joining the line > with the next line. > > Is this necessary in Japanese? It's not done in any other language, and if > it's possible to avoid it, I think it would be better practice. Havina an > @c at the end of each line makes it harder to edit, in general. > > I'm only a tiny bit literate in Japanese, so maybe there's something that I > don't know about that requires @c at the end of each line. The reason to put @c at the end of each line is because a line break in a TexInfo file produces a white space in its document and Japanese texts usually do not use any white space. @c at the end of line prevents texi2html from converting it's line break to a white space. I think Japanese text with needless white spaces looks ugly and is hard to read. But other Japanese may not pay any attention for it. In fact, the previous Japanese translator for LilyPond (Ishizaki-san) put line breaks into HTML files without any care. Before, I entered a paragraph into a line of a TexInfo file not to produce needless white spaces. But, because the patch generated from it is hard to read, I now often put line breaks with "@c"s. I think there are three choices which we should select to treat Japanese text. 1. Put line breaks with "@c"s into TexInfo files. The advantage of this method is generated documents look good and their TexInfo sources do not look so bad. The disadvantage is they make their TexInfo codes harder to edit as you said. 2. Put a paragraph into a line of TexInfo file. Documents generated by this method look good, but their TexInfo sources are hard to read. 3. Put line breaks without any "@c" into TexInfo files. TexInfo files are easy to read and edit, but documents generated from them look a little bad. Of course, I think choice 1 is best. But if I should take choice 3, it is better to put line breaks immediately after commas or periods when I can. (They are "、" and "。" respectively in Japanese.) Thanks, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: OT: Some git statistics
Fred is what Jan used to call himself on his home machine. On Mon, Feb 2, 2009 at 4:17 AM, Francisco Vila wrote: > Warning: offtopic. Do not waste your time if it doesn't worth it. > > I've put a set of lilypond git statistics at > http://paconet.org/lilypond-statistics/index.html have a look at https://www.ohloh.net/p/lilypond too -- 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: OT: Some git statistics
2009/2/2 Han-Wen Nienhuys : > Fred is what Jan used to call himself on his home machine. Impossible. Was he the one and only committer for 6+ years? > have a look at > > https://www.ohloh.net/p/lilypond This does not say anything new and it is based on the git repo, anyway. - History stops on 2008/04 - If you are a contributor, you aren't another contributor, so no mailmaps here. - ... -- 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: OT: Some git statistics
Op maandag 02-02-2009 om 19:39 uur [tijdzone +0100], schreef Francisco Vila: > 2009/2/2 Han-Wen Nienhuys : > > Fred is what Jan used to call himself on his home machine. > > Impossible. Was he the one and only committer for 6+ years? Fred was me when I populated the history of our CVS using tarball releases and patches, using a cheesy script. The first six years we used tarball releases and mailing patches. We usually had a pattern like [hanwen]: lilypond-0.0.60.tar.gz [jan]:lilypond-0.0.60.jcn.diff.gz -> mail to hanwen [hanwen]: lilypond-0.0.60.hwn1.diff.gz -> hanwen's hacks + jcn1 -> mail to jan OR [hanwen]: lilypond.0.0.60.hwn1.diff.gz -> mail to jan [jan]:lilypond-0.0.60.jcn2.diff.gz -> includes .hwn1 -> mail to hanwen until we got to .jcn/.hwn 3/4/5 and Han-Wen made a new release. This then included patches sent to the list by Mats [.mb], Werner [.wl] and others. See also http://repo.or.cz/w/lilypond.git?a=blob;f=Documentation/misc/CHANGES-0.0;h=f936254a1f7a92f043954bae0689c52375b3b2f1;hb=HEAD It would be nice but hardly doable to make a much better history, as most of the intermediate releases and patches have been lost [I think]. Not all intermediate patches had good changelog entries. Jan. -- Jan Nieuwenhuizen | 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: OT: Some git statistics
Hi, On Mon, 2 Feb 2009, Francisco Vila wrote: > - How could differently-written names for a given author to be joined on > one? I guess you could write a .mailmap: http://www.kernel.org/pub/software/scm/git/docs/git-shortlog.html (section "FILES"). Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Sponsoring a full support for footnotes in Lilypond
I stopped doing sponsored work on LilyPond. I'm forwarding your message to the lilypond-devel forum. Maybe you can someone there can help you. ** Dear Sir, I would like to start negotiating with you about me sponsoring the feature in Lilypond which would add the full support of footnotes, i.e. markup which would at certain place make a sign (a number, for example) and at the footer (alternatively in the margin of the page) of the page there would be the sentence of small paragraph with the text of the footnote. The numbers/symbols to use should be customizable to certain extent - for example numbering each page separately, or numbering each piece separately, or numbering whole book in a series. The Lilypond should automatically keep the footnotes on the same page where they occur and automatically calculate the space needed in the footer for the footenote text to occupy. This function is called for by many users already for several years as I read in the lilypond forum, and I think it is still not there. For musicologists this is the main feature - I am now setting up means in Lilypond for my work which should span over 3 years, editing about 800 pages of mediaeval Czech chant - the critical edition - and footnote would be very requirement for this work to be easy. So, please, if you are willing to do this, please estimate the expenses and perhaps I will pay it myself, or alternatively I will try to find more people supporting the feature with the help of your internet webpage - as you state on your internet pages. Sincerely, Jiri Zurek -- 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: Good luck, Valentin
Arthur Reutenauer wrote: The name is "Affaire étrangère"; how would you translate it, Valentin? :-) "Foreign affair" surely sounds odd :-) Arthur "Business Abroad"? Break a leg for the rest of the run, Valentin. Cheers, Ian ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Japanese translations
> The reason to put @c at the end of each line is because a line break > in a TexInfo file produces a white space in its document and > Japanese texts usually do not use any white space. @c at the end of > line prevents texi2html from converting it's line break to a white > space. This is a suboptimal solution. texinfo (and texi2html) should have an option to control that, similar to my CJK package for LaTeX. > Of course, I think choice 1 is best. But if I should take choice 3, > it is better to put line breaks immediately after commas or periods > when I can. (They are "、" and "。" respectively in Japanese.) Similarly, kinsoku shori should be controlled by texi2html. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
OT: Some git statistics
Warning: offtopic. Do not waste your time if it doesn't worth it. I've put a set of lilypond git statistics at http://paconet.org/lilypond-statistics/index.html Still trying to understand certain anomalies here... To help on this, is anybody able to answer - who is fred? I assume it's a dummy name for an old VCS that didn't support author names. - How could differently-written names for a given author to be joined on one? - what a cataclysm happened between 2002-03-24 and 2002-03-27? -- 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: Sponsoring a full support for footnotes in Lilypond
On Mon, Feb 2, 2009, Han-Wen Nienhuys said: > I stopped doing sponsored work on LilyPond. I'm forwarding your > message to the lilypond-devel forum. Maybe you can someone there can > help you. MS Word, and might even be supported in more robust desktop publishing software such as Quarkexpress, Pagemaker, or Framemaker. Footnotes are not always small citations, sometimes they are many paragraphs long and need to be flowed across several pages in competition with the main flow of prose and ilustrations (music in our case). This might not be a quickie which would be available for this user in a reasonable timeframe, even if someone here cared to work on it at all. Endnotes would be easier to implement, but for generality and our other users we should do both if either, as many journals and some publishers prefer endnotes. Perhaps the user could be content to make illustrations in LP to adorn the pages of the book typeset in MS Word? -- Dana Emery ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Good luck, Valentin
2009/2/1 John Mandereau : > IIRC it should have started at 15.00 CET, so the premiere is most probably > finished. I hope this was a great success and the two other will go well > too. Greetings everybody, the past couple of weeks has been exhausting and has almost been preventing me from following our mailing lists, but at least it's done now. As John said, there are still two performances on tommorrow and Thursday evening, but at least my work is done. I think it has been quite a success indeed. It's funny and straightforward, and both the audience and the perfomers seem to find it amusing. We had a pretty decent media coverage, and not one single interview has been published without mentioning LilyPond and the special terms of the opera's license. As soon as I have more time (any day now), I'll tell you more about that (this very evening, I'm even advertising LilyPond on TV!). One other thing worth mentioning is that this project has allowed me to demonstrate LilyPond power and beauty. Some musicians have asked me to reprint their parts with a different layout, bigger staves, thicker barlines, more time to turn their pages, etc; all of which I've been able to do impressively quickly and perfectly; not to mention more complicated stuff such as clean transpositions, clefs fine-tuning etc. Several musicians have made nice compliments about the quality of their printed parts. As this opera is adapted from a comic book, I have included some graphics into the score, and it has been quite pleasant to see the musicians smile while playing, and to hear the conductor say "let's start back from... hem.. well, from the little drawing that looks like a castle". I had originally created a font that looked like the hand-written texts in the comic book, and all the lyrics were printed using that font. However, since the comic book's author didn't want this font to be free, I eventually had to remove it. Finally, the table of contents was nice, and quite helpful for the singers. The license I have chosen wraps together the GPL for the source code (this way you may use any function, macro, PostScript or even chunks of music), and a CC by-nc-sa for the "narrative work" (characters, story, etc.), which has allowed us to "sell" our stuff to the opera house. Since this license is copyleft, it will also cover any derivative work such as the video recording that has been made, which I plan to offer on the Internet, with convenient subtitles. This also means that the recorded music may be remixed, and redistributed in a non-commercial approach. (We'll wait for several months, and then see if we can remove the -nc- term from the license.) In the meantime, you can have a look at http://valentin.villenave.info/opera/download.html (in French) and at the source code: http://repo.or.cz/w/opera_libre.git As for the title, I think that would be "The Foreign Affair"...; by the way, I'm looking for a skilled translator to translate the subtitles. (and/or translate the libretto into English or other languages.) Whether you want to read it, translate it, reproduce it, rewrite it accordingly to your tastes or needs, be my guest: this work is meant for everyone, and I'd be really happy if it could have a life of its own after my work is done. Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Sponsoring a full support for footnotes in Lilypond
2009/2/2 Han-Wen Nienhuys : > I stopped doing sponsored work on LilyPond. I'm forwarding your > message to the lilypond-devel forum. Maybe you can someone there can > help you. I'm not sure anybody will be able to implement that anytime soon, but it's indeed a mandatory feature for lots of people (myself included). I've added it to our tracker to make sure it won't go forgotten: http://code.google.com/p/lilypond/issues/detail?id=737 Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
