Re: Compile failure with latest CVS
Hi, This problem still remains with todays CVS version. Regarding the gcc version, the relevant information is of course that my g++4 is: gcc version 4.1.0 /Mats Mats Bengtsson wrote: When I try to build the latest CVS version, it ends with rm -f ./out/file-name.dep; DEPENDENCIES_OUTPUT=./out/file-name.dep ./out/file-name.o g++4 -c -DHAVE_CONFIG_H -DNDEBUG -I./include -I./out -I../flower/include -I../flower/./out -O2 -finline-functions -g -pipe -Werror -I/nobackup/include -pthread -I/usr/include/freetype2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-W -Wall -Wconversion -o out/file-name.o file-name.cc cc1plus: warnings being treated as errors /usr/include/c++/3.4.3/bits/basic_string.h: In static member function 'static std::basic_string_CharT, _Traits, _Alloc::_Rep std::basic_string_CharT, _Traits, _Alloc::_Rep::_S_empty_rep() [with _CharT = char, _Traits = std::char_traitschar, _Alloc = std::allocatorchar]': /usr/include/c++/3.4.3/bits/basic_string.h:215: instantiated from 'void std::basic_string_CharT, _Traits, _Alloc::_Rep::_M_dispose(const _Alloc) [with _CharT = char, _Traits = std::char_traitschar, _Alloc = std::allocatorchar]' /usr/include/c++/3.4.3/bits/basic_string.h:418: instantiated from 'std::basic_string_CharT, _Traits, _Alloc::~basic_string() [with _CharT = char, _Traits = std::char_traitschar, _Alloc = std::allocatorchar]' file-name.cc:66: instantiated from here /usr/include/c++/3.4.3/bits/basic_string.h:178: warning: dereferencing type-punned pointer will break strict-aliasing rules make[1]: *** [out/file-name.o] Error 1 make[1]: Leaving directory `/nobackup/lilypond/flower' make: *** [all] Error 2 This is using gcc version 3.4.6. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Page numbers
Han-Wen Nienhuys wrote: Han-Wen, I second the suggestion that print-page-number should be #t by default; this is causing a lot of confusion to some people. Could this be done before 2.10? Certainly. Please apply/revert this change. The last I can remember is that Mats changed the name of this property. Hmm! I changed printfirst-page-number - print-first-page-number and I only did this change in 2.9 and the problem appears also in 2.8 so I don't think that's the culprit. /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Tuesday 31 October 2006 05:37, Joe Neeman wrote: On 10/31/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote: Hi guys, a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.html please comment. On the long term - In the long term and this will enable other programss - ... programs Other than that, looks good. Also, perhaps to read LilyPond - to read LilyPond music? -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Compile failure with latest CVS
Mats Bengtsson escreveu: Hi, This problem still remains with todays CVS version. Regarding the gcc version, the relevant information is of course that my g++4 is: gcc version 4.1.0 /Mats I don't understand, your log shows /usr/include/c++/3.4.3/bits/basic_string.h:178: warning: dereferencing are you using 3.4 (unsupported) or 4.1 ? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
elegant input format and hard for other programs to parse sounds somewhat like a contradiction. Maybe sophisticated instead of elegant would be more appropriate? I am not sure about capitalization in English language, but shouldn't * all words in the headline except than start with a capital letter and * the itemized texts start with small letters (except DocBook), since they continue an incomplete sentence? Shouldn't there be a full-stop dot after the last item? Greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Hi, On Tue, 31 Oct 2006, Han-Wen Nienhuys wrote: a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.html It is a great read! You meant nested tuplets instead of nested, right? Ciao, Dscho P.S.: Congratulations on your GUB work! And sorry, I could not be of assistance with git, since I was busy writing a grant application (I just spent a week in Scotland, and was working with two other scientists). ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Mats Bengtsson escreveu: Hi, Two minor comments: For the readers that don't know LilyPond from before, it's probably not clear that the 9 months of furious programming refer to the time since version 2.8.0. (Why not call it a 10 year anniversary release?) good idea, that also gives it a new ring to the release text. The second bullet point below New Stuff ends with nested, I guess some text has disappeared. thanks -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Juergen Reuter escreveu: elegant input format and hard for other programs to parse sounds somewhat like a contradiction. Maybe sophisticated instead of elegant would be more appropriate? I am not sure about capitalization in English language, but shouldn't * all words in the headline except than start with a capital letter and It depends. This is really a bad practice that was started in the time that newspaper were still set by hand. Then, there were not enough large type letters, so mixing caps spread out the usage better. The practice is silly today. * the itemized texts start with small letters (except DocBook), since they continue an incomplete sentence? yup. Shouldn't there be a full-stop dot after the last item? Greetings, Juergen -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Johannes Schindelin escreveu: P.S.: Congratulations on your GUB work! And sorry, I could not be of assistance with git, since I was busy writing a grant application (I just spent a week in Scotland, and was working with two other scientists). Cool. We've put up a repository at repo.or.cz , but we'll probably be one of the firsts to use git at savannah. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Mats Bengtsson wrote: The second bullet point below New Stuff ends with nested, I guess some text has disappeared. I guess Han-Wen meant nested tuplets, didn't he? -- John Mandereau [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Han-Wen Nienhuys [EMAIL PROTECTED] writes: The practice is silly today. I think so too, but it is still what people expect? Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | 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: draft release announcement
Hi, On Tue, 31 Oct 2006, Juergen Reuter wrote: elegant input format and hard for other programs to parse sounds somewhat like a contradiction. Maybe sophisticated instead of elegant would be more appropriate? I think elegant is too elegant a description to be scrapped ;-) Maybe clarify: While the format is easy to write and read for humans, it is less so for programs. Therefore ... Hmmm? Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Jan Nieuwenhuizen escreveu: Han-Wen Nienhuys [EMAIL PROTECTED] writes: The practice is silly today. I think so too, but it is still what people expect? only in the US, I think. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation translation
Han-Wen Nienhuys wrote: Ludovic Sardain escreveu: Hello, As you know, we are a small team of french translators, and for some months, we're not doing anything, because none of us has understood how to compile the documentation. There's also some problem about whereas we must translate or not the nodes titles. Jan and I have been working very hard over the last days to give our build infrastructuer an update. It should be possible, in the short run, to have an almost-single-button-push method of compiling the documentation By build infrastructure, do you mean the git repository? Do you plan to replace cvs with git for the main (read/write) repository on savannah.gnu.org? Besides that, the growing number of people on [EMAIL PROTECTED] asking for a French translation of the docs, or offering to participate in doing it has (finally) urged me to have a look at the makefiles infrastructure. So, here's a [LONG] follow-up of http://lists.gnu.org/archive/html/lilypond-devel/2005-09/msg00036.html Jan Nieuwenhuizen wrote: John Mandereau writes: Does it mean that that the node names cannot be translated? (Or have I not understood well what you explained?) Yes, that's what I meant. I'm not 100% sure this is the best way, but this is what I'd like to try first. What we'd do is (excuse les mots) @node First steps @section Premier etapes and @menu * First steps:: Premiere etapes That would result in web pages: Documentation/user/out-www/lilypond/First-steps.html Documentation/user/out-www/lilypond/First-steps.fr.html Having the same html file names could be an advantage, I guess; it would be a lot easier to switch and compare different languages, and see what other languages are available for that page, just like the main web site. I'm not sure about the usability of the INFO docs, where you'd have to use English node names. It's important to have the same html filenames, but the node names should be translated, otherwise all that hard translation work is not very worthy imho. Why not gettext node names? I mean that a script could collect all node names from the .(i)tely files and write them to a po file, then (after the html docs have been generated) another script could replace the node names with regexp substitutions (like title[node name] - GNU LilyPond/title or a href=.*[node name]/a). These two scripts are fairly easy to write in Python (I've already almost written the first one). I would just like to see the effect/usability of this after having translated a few pages, and see if that's the right way to continue, or whether we have to think of something else. I have tested Jan's makefile (see patch from http://lists.gnu.org/archive/html/lilypond-devel/2005-09/msg00017.html ) against latest tutorial French translation: it works except that I had to do some minor corrections, and PNG symlinks to PNGs of English pages don't work. Before dealing with any concrete code, I would like to have the opinion of the main hackers on the goal and the main technical aspects of translating the docs. IMHO it's useful to translate the whole user manual, because: - it is the part of the documentation where there is most explanation blurb, and so it is the part of the documentation where translation is most useful and (technically speaking) doable (unlike the program reference, for example). - we are enough translators to achieve this in a reasonnable time: it took 3 translators 3 months to translate lilypond.org, and I guess there are at least as many translators ready to start working. Documentation today is available both on-line and in a tarball, and AFAIK the same files are used for both forms. If we want content negociation (i.e. automatic language selection) for the docs on lilypond.org, this will no longer be possible. I really like content negociation, mainly because it requires almost no user intervention. Regarding handling of HTML files, the most useful for both forms is certainly to hard link Documentation/user/*.LANG.html to Documentation/LANG/(user/)*.html, just like Jan's patch does. Then, for the on-line docs on lilypond.org, .html extensions should be stripped in all hrefs so that content negociation works, and a footer about automatic language selection and available languages should be added like on lilypond.org main site. For the tarball docs, I think the best solution is to generate one tarball per language: for languages other than English, *.LANG.html files should be renamed to *.html, and html pages which have no translation should be packed into the tarball too. Regarding ly snippets, there are 2 possibilities: 1) PNGs and code snippets from the English docs are used for the translated docs through symlinks. The main advantage is that translated docs don't take too much time to make and don't take too much disk space on lilypond.org. 2) ly snippets in translated docs are totally
Re: documentation translation
John Mandereau escreveu: Regarding ly snippets, there are 2 possibilities: 1) PNGs and code snippets from the English docs are used for the translated docs through symlinks. The main advantage is that translated docs don't take too much time to make and don't take too much disk space on lilypond.org. 2) ly snippets in translated docs are totally independent from ly snippets from untranslated docs. This has 2 advantages: it is easier to write the makefiles and it makes the snippets translatable, which is nicer for the end-user (texts and maybe pitch names could be translated). I prefer #2 over #1. Maybe we could ask end users on lilypond-user-fr to give their preference? Quick remark Don't agonize over this. The snippets are hashed, so duplicate snippets will be shared, if we make sure that the .ly and .png files are in the same directory. We should probably put all the snippets and images for the current doc site in one directory anyway. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation translation
John Mandereau escreveu: Jan and I have been working very hard over the last days to give our build infrastructuer an update. It should be possible, in the short run, to have an almost-single-button-push method of compiling the documentation By build infrastructure, do you mean the git repository? Do you plan No, I mean GUB the build system where we build all the binaries. The new changes (including GIT support) mean that it's possible to build and test your own versions of lilypond locally, i.e. without pushing changes through savannah.gnu.org. Also, with DVC, it should be much easier to transport changes to and from stable and devel branches of the code. to replace cvs with git for the main (read/write) repository on savannah.gnu.org? Yes, that is the plan, but it might take some weeks before that is done. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation translation
John Mandereau [EMAIL PROTECTED] writes: I have tested Jan's makefile (see patch from http://lists.gnu.org/archive/html/lilypond-devel/2005-09/msg00017.html ) against latest tutorial French translation: it works except that I had to do some minor corrections, and PNG symlinks to PNGs of English pages don't work. Ok. If it helps the translators, we can include your patch after we release 2.10. Then, for the on-line docs on lilypond.org, .html extensions should be stripped in all hrefs so that content negociation works, and a footer about automatic language selection and available languages should be added like on lilypond.org main site. For the tarball docs, I think the best solution is to generate one tarball per language: for languages other than English, *.LANG.html files should be renamed to *.html, and html pages which have no translation should be packed into the tarball too. Yes, I agree. This, and the png snippet problem, will be things that we can work out when the translation code is in place. Regarding translation maintaining, as the current maintainer of lilypond.org French translation, I'm happy with check-translation, so we could use almost the same script to maintain the user manual translation. But to avoid to maintain already translated stuff while doing the main translation work, and possibly to make translation available for 2.10 before the next stable release, I think it's better we stick with 2.10, and update to the development branch only when everything is translated. Sounds fine. I'm sure you will keep an eye on development, to see if you're not translating old stuff. I'm looking forward to your patch. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | 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: draft release announcement
On Tue, Oct 31, 2006 at 01:31:26AM +0100, Han-Wen Nienhuys wrote: Hi guys, a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.html please comment. thanks, A couple of things: Is there going to be a 2.10.0? Even if there is, it's the new series that is making the news, so I would suggest leaving the version number at 2.10. `got annoyed' is a little unprofessional. Perhaps `were disappointed' or `became disillusioned'. `computer print-out' should be `computer print-outs' or even `computer generated print outs.' `reading' should be `to read' Of course, these are just my opinions! When does the announcement look likely? -- = Cameron Horsburgh = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
