Re: lilypad is localized?
https://code.google.com/p/lilypond/issues/detail?id=3586 2013/9/29 Phil Holmes m...@philholmes.net ** These both need a bit of study to work out how to fix them. Can you raise an issue for them, please? -- Phil Holmes - Original Message - *From:* Federico Bruni fedel...@gmail.com *To:* Phil Holmes m...@philholmes.net *Cc:* Graham Percival gra...@percival-music.ca ; David Kastrupd...@gnu.org; lilypond-devel lilypond-devel@gnu.org *Sent:* Sunday, September 29, 2013 10:57 AM *Subject:* Re: lilypad is localized? 2013/9/29 Federico Bruni fedel...@gmail.com 2013/9/28 Federico Bruni fedel...@gmail.com 2013/9/28 Phil Holmes m...@philholmes.net I believe lilypad for Windows is localised - see https://github.com/gperciva/**lilypad/tree/master/windowshttps://github.com/gperciva/lilypad/tree/master/windows All those .rc files are Windows resource files in different languages. I've no idea how it works, though. I think I can test it later I've just remembered that I have a virtualbox file with Windows inside I confirm that LilyPad is localized: let me know if you need screenshots for italian website.. Two issues to fix IMO: 1. Welcome_to_Lilypond should be translated 2. The installation wizard was in english, even if my locale in Windows is italian Generate PDF and Edit source (right-click menu) are not translated. So only the menu items are translated. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
verification and bulk edit [Re: Unverified issues?]
2013/9/29 Eluze elu...@gmail.com Traditionally Eluze works through these on a Monday. Let's check the situation on Tuesday. Ah, ok. I will treat what's left tomorrow (I'm not the only bug squad member allowed to do it!) I've cleared some of them, you won't have to work too much tomorrow :-) This is a boring task and it should be shared as possible between all bug squad members. Also, I'm thinking about a way of making it easier. Most of the times we have only to check if the committish pasted by the developer is really in master. If we add a field Committish (where the developer should paste the committish), then the bug squad can show the column Committish and work on the list page instead of having to open each issue. Then we copypaste each committish in gitk and when we have verified all of them we can use the bulk edit to mark all the issues as Verified in one shot (never tried but I hope it works). What do you think about it? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: verification and bulk edit [Re: Unverified issues?]
2013/9/29 David Kastrup d...@gnu.org It matches the theory. In practice, I've been startled quite a few times when bug squad members not just verified the commit to be present but also reported back when it turned out that the claimed functionality did not actually accompany the commit. The verification you spell out here could be done by a web crawler and would be done in seconds. The verification from the bug squad appears to do a more thorough job on average. This makes sense for issues marked as defects.. Well, some of them: for example, issue 3553 doesn't have a minimal example (I guess it cannot be produced) and I have no idea about how to verify it in depth. In such cases I'll follow the CG: Quite a few of these will be issues tracking patches. You do not have to prove these patches work - simply that they have been pushed into the code base. BTW, what are tracking patches? On the other hand, all the doc issues don't require other than checking that the committish is in master. When changing the issue tracker, you get a field for specifying what the tracker should do next after changing the current issue. If you use go to next issue, it will move to the next issue matching the search. That seems rather efficient, and it would appear that the bug squad reading the issue description and possibly more leads to an improvement of the results. The question is whether we can significantly improve the efficiency without sacrificing more quality than desirable. Because of the release delay, the issues to verify for 2.17.27 were way over the average, which is around 15 issues per release AFAICS. So probably my proposal is not needed. I'm curious to hear the opinion of Eluze ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypad is localized?
I can't remember if LilyPad for Windows is localized and I don't have Windows machines to test it myself. Just to know if I should translate the lilypad menus in the Documentation or not. Thanks Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypad is localized?
2013/9/28 Phil Holmes m...@philholmes.net I believe lilypad for Windows is localised - see https://github.com/gperciva/**lilypad/tree/master/windowshttps://github.com/gperciva/lilypad/tree/master/windows All those .rc files are Windows resource files in different languages. I've no idea how it works, though. I think I can test it later I've just remembered that I have a virtualbox file with Windows inside ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
no critical: 2.18 is close?
I see there's no critical issue in the tracker. I remember that you used to publish release candidates of next stable when we have no critical issues. So I wonder if the releae of 2.18 is close or there's something that it's blocking it.. Just curious.. and also I want to organize my translation work. Thanks Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: we now have lilypond organization on GitHub
2013/9/18 David Kastrup d...@gnu.org Translation workflows don't use our review system or issue trackers. And I don't even think they would benefit from it. If we take a look at the few reasonably tightly tracked translations (French and Spanish, I think), I very much doubt that you'd improve the quality of the work of the respective translators by forcing a web frontend on them. And I doubt that a crowd-sourced German (say) translation would lead to a consistent quality _unless_ several people get fully immersed into it and again work at a level of thoroughness where web/crowdsourced interfaces get more in the way than anything else. Program documentation is not a Wikipedia-like task. LilyPond documentation is so huge that sometimes I wish that more people could be involved.On the other hand, keeping the documentation consistent in the use of words is harder when several persons are working on it. I think that I like working in a team of two persons, even if this means that translation is proceeding slowly. Anyway, I don't know if a web interface would help much (at least for italian translation, as I don't see many users). The problem is translating.. and the quantity of lines to be translated: this is what may scare away potential contributors. I think also that the average LilyPond user can deal fairly well with unfriendly interfaces :-) For example, I recently asked the reviewer of my translation to use git[1] to send his corrections to me. He did it right since the beginning, even if he had no experience in commits and patches. [1] right after receiving 50 .diff files for each file in his previous review :) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ERROR: Please install required programs: International New Century Schoolbook fonts
2013/8/3 Federico Bruni fedel...@gmail.com I'm getting this error if I run ./autogen.sh in git master: ERROR: Please install required programs: International New Century Schoolbook fonts International New Century Schoolbook fonts I can't find the missing package, I have all the ones listes in the CG. What I'm missing? In the same directory, now it works if I checkout master branch and I still get this error if I checkout translation branch. Probably issue 3526 fixed by Julien? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ERROR: Please install required programs: International New Century Schoolbook fonts
2013/8/3 James pkx1...@gmail.com Well when I run configure in an out of tree build I get the line --snip-- checking New Century Schoolbook PFB files... /usr/share/fonts/type1/gsfonts/c059013l.pfb /usr/share/fonts/type1/gsfonts/c059033l.pfb /usr/share/fonts/type1/gsfonts/c059036l.pfb /usr/share/fonts/type1/gsfonts/c059016l.pfb --snip-- So I assume this is where it is checking. I can only assume you have updated or removed some other package that has broken this dependency? I have those files: $ ls /usr/share/fonts/type1/gsfonts/c059*.pfb /usr/share/fonts/type1/gsfonts/c059013l.pfb /usr/share/fonts/type1/gsfonts/c059016l.pfb /usr/share/fonts/type1/gsfonts/c059033l.pfb /usr/share/fonts/type1/gsfonts/c059036l.pfb ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ERROR: Please install required programs: International NewCentury Schoolbook fonts
2013/8/9 Phil Holmes m...@philholmes.net Is http://code.google.com/p/lilypond/issues/detail?id=2742 of relevance? maybe... but I have texlive-lang-cyrillic installed this is the relevant part of the configure error: checking New Century Schoolbook PFB files... configure: WARNING: /usr/share/texlive/texmf-dist/fonts/type1/urw/ncntrsbk/uncbi8a.pfb does not have Cyrillic characters. configure: WARNING: /usr/share/texlive/texmf-dist/fonts/type1/urw/ncntrsbk/uncri8a.pfb does not have Cyrillic characters. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Suggestion: spacing for swing music?
2013/7/13 Steve Burgondy steve.burgo...@gmail.com Hello, Proportional spacing can be of great help to understand music and to associate visual space to time space. It can be useful for beginners, but also in general. It is very important in tablatures, especially when full tab notation is not used. Currently in Lilypond, if we want to have an accurate visual space representation in the specific case of swing music, it is required to enter music in 12/8 mode (this implies dotted notes and so on). Has anyone thought of implementing swing spacing with a 4/4 mode notation? Would this be hard to achieve? Hi Steve AFAICS nobody replied to your questions. I'm not a developer so I cannot say if this can be achieved or not (but I have a feeling that it's not easy for sure). I'm putting the bug-lilypond list in CC. There's an analog issue with sound (MIDI): https://code.google.com/p/lilypond/issues/detail?id=687 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
ERROR: Please install required programs: International New Century Schoolbook fonts
I'm getting this error if I run ./autogen.sh in git master: ERROR: Please install required programs: International New Century Schoolbook fonts International New Century Schoolbook fonts I can't find the missing package, I have all the ones listes in the CG. What I'm missing? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ERROR: Please install required programs: International New Century Schoolbook fonts
2013/8/3 David Kastrup d...@gnu.org James pkx1...@gmail.com writes: On 03/08/13 18:53, Federico Bruni wrote: I'm getting this error if I run ./autogen.sh in git master: ERROR: Please install required programs: International New Century Schoolbook fonts International New Century Schoolbook fonts I can't find the missing package, I have all the ones listes in the CG. What I'm missing? Hello, Well when I run configure in an out of tree build I get the line --snip-- checking New Century Schoolbook PFB files... /usr/share/fonts/type1/gsfonts/c059013l.pfb /usr/share/fonts/type1/gsfonts/c059033l.pfb /usr/share/fonts/type1/gsfonts/c059036l.pfb /usr/share/fonts/type1/gsfonts/c059016l.pfb --snip-- So I assume this is where it is checking. I can only assume you have updated or removed some other package that has broken this dependency? gsfonts probably? gsfonts is installed I've just spot a warning in the middle of the terminal output: checking New Century Schoolbook PFB files... configure: WARNING: /usr/share/texlive/texmf-dist/fonts/type1/urw/ncntrsbk/uncbi8a.pfb does not have Cyrillic characters. configure: WARNING: /usr/share/texlive/texmf-dist/fonts/type1/urw/ncntrsbk/uncri8a.pfb does not have Cyrillic characters. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: References to publications in the docs
2013/7/13 Phil Holmes em...@philholmes.net We currently refer to Gardner Read and others in the NR under the very sparsely populated Contemporary Music section of the NR: http://www.lilypond.org/doc/**v2.17/Documentation/notation/** further-reading-and-scores-of-**interesthttp://www.lilypond.org/doc/v2.17/Documentation/notation/further-reading-and-scores-of-interest It strikes me that this would be better at the end of section 1 of the LM: http://www.lilypond.org/doc/**v2.17/Documentation/learning/** overview-of-manualshttp://www.lilypond.org/doc/v2.17/Documentation/learning/overview-of-manuals Further reading, plus adding at the very least Elaine Gould's book. Does anyone disagree? BTW, shouldn't the node title be included inside the @ignore? @node Scores and musical examples @unnumberedsubsubsec Scores and musical examples @ignore Rough list of composers whose work could be included (in alphabetical order, perhaps with suggested work): Pierre Boulez (Le Marteau Sans Maître?) John Cage (Freeman Etudes?) George Crumb (Black Angels?) Brian Ferneyhough (Transit? Time Motion Studies?) Ben Johnston (extended just intonation example) György Ligeti (several, including Hamburg Concerto) Krzysztof Penderecki (Threnody to the Victims of Hiroshima?) Karlheinz Stockhausen (Gruppen?) @end ignore It was ignored from the very beginning (perhaps a kind of todo list): commit 7df6ed01116dac2a8ea1babfb3f7184859ebf6c7 Author: Joseph Wakeling joseph.wakel...@webdrake.net Date: Sat Sep 5 22:30:58 2009 +0200 Doc: Further Reading for contemporary music. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Busy Developers' Summary 10: we have a blog!
2013/6/10 Jacques Menu jacques.m...@tvtmail.ch A suggestion : it might be nice to use: target=_blank in the links on the blog, thus switching to a new window or tab. I'm against the use of this. It should be up to the user choosing to open whatever link in a new tab/window or not. Opening a new tab is quite easy: right click or hold Ctrl and left click. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: the future of LilyPond blog
2013/6/3 Janek Warchoł janek.lilyp...@gmail.com Hi, in general: good points, but i have valid arguments as well ;) 2013/6/3 Jan Nieuwenhuizen jann...@gnu.org: Janek Warchoł writes: because i have 0 experience with blogging and webhosting and i didn't want to spend a lot of time setting things up :) What I also mean is, is it wise to have yet another site/platform? What is wordpress.com doing for us, that cannot be done just as well (or better?) on G+ -- http://google.com/+lilypond [...] 2) We won't have complete control over the content (that's why i want to move the blog to our website eventually). I think that we should be as independent as possible. As far as i know, Wordpress is open source so we can take it with us, there shouldn't be (m)any proprietary software dependencies. Another option could be Mezzanine, a CMS based on Django which has many built-in features (including blogging). Considering that many lilypond developers know python, it could be a wise choice in case we need to hack on it. Mezzanine has some scripts to import from other CMS (Wordpress included): http://mezzanine.jupo.org/docs/blog-importing.html The initiative is great ...but we now have groups on FB and G+ and all kinds of alternative/language fora all over the place. I agree that it's bad to spread all over the internet too much. However, from what i see on G+ it's growing to become more something like a mailing list: people post links to LilyPond-related articles (i.e. Liedboek announcement), ask about LilyPond. It seems to me to be more like a news aggregator - it collects content from other places. I don't imagine anyone posting an article like this http://news.lilynet.net/?The-LilyPond-Report-26#lilypond_output_analysis on G+ - it seems too long (maybe my gut feeling is wrong, though), while it's acceptable for a blog post. Yes, I agree with you. The blog you are setting up is something totally different and you are missing an important gap. This may actually need to be stated more clearly: i want this blog to become a source of information, not just a news feed. Something that people read even 5 years after it was posted, because it gives them valuable knowledge. can I suggest putting keywords in the titles of posts? I think that it would improve the search: for example wikipond is funny but lilypond-scores-in-wikipedia work better also, there should be some SEO plugin for Wordpress I apologize that i didn't ask for opinions first, but i have an impression that we (LilyPond community) sometimes go on and talk forever and not have anything done. I appreciate your approach! :-) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: do we have @lilypond.org email addresses?
2013/6/1 Janek Warchoł janek.lilyp...@gmail.com Hi, as mentioned in this post, i'd like to contact WordPress about a lilypond blog name that is taken, but inactive. I think it would be good to contact them using some @lilypond.org address, to be more credible. Do we have such addresses? maybe you can just give them a link to a commit in gitweb where your email address is recorded ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: OT: Struggling with time
2013/5/29 Francisco Vila paconet@gmail.com Dear LilyPond community, my apologies for having disappeared these days. I have important issues at end of every semester, along with taxes, family, and own studies. Especially Federico, please forgive me for ignoring your request of more information on a lilypond-book-related matter. I will return to life ASAP. Thank you -- no problem, we are all struggling with time ;-) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
make error: please check usage.makeinfo.log for errors
I'm having trouble with make, I've never had this kind of problem. Maybe some system update broke something? $ make [...] /home/fede/lilypond-git/scripts/build/out/run-and-check LANG= makeinfo --enable-encoding --error-limit=0 -I /home/fede/lilypond-git/Documentation -I. -I./out --output=out/lilypond-usage.info out/usage.texi usage.makeinfo.log Please check the logfile usage.makeinfo.log for errors make[1]: *** [out/lilypond-usage.info] Error 1 make[1]: Leaving directory `/home/fede/lilypond-git/Documentation' make: *** [all] Error 2 Find attached the log file. I've already tried running 'make distclean' and start from scratch, but I get the same error. I'm on debian sid texinfo v5.1 Thanks Federico usage.makeinfo.log Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ugly left-side cropping in documentation
2013/5/28 Werner LEMBERG w...@gnu.org Have a look at the image in this section: http://www.lilypond.org/doc/v2.17/Documentation/notation/displaying-staves#nested-staff-groups Whatever the snippet tries to show, it is cut off. it was correct in v2.16: http://www.lilypond.org/doc/v2.16/Documentation/notation/displaying-staves#nested-staff-groups ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make error: please check usage.makeinfo.log for errors
2013/5/28 Werner LEMBERG w...@gnu.org As distributions move on to Texinfo 5, we are going to get a rather awkward transitioning problem. I fear so. On the other hand, the warning messages are reasonable (at least most of the time :-), and fixing them should be straightforward. A completely different issue is our hand-crafted `lilypond-texi2html.init' file. No idea whether this is compatible with texinfo 5. maybe ./configure should check the installed version of texinfo and print a warning if it's 4.13? tonight I'll downgrade texinfo and try again thanks Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make error: please check usage.makeinfo.log for errors
2013/5/28 Werner LEMBERG w...@gnu.org A completely different issue is our hand-crafted `lilypond-texi2html.init' file. No idea whether this is compatible with texinfo 5. http://lists.gnu.org/archive/html/help-texinfo/2011-02/msg00013.html http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#texi2html ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make error: please check usage.makeinfo.log for errors
2013/5/28 Werner LEMBERG w...@gnu.org maybe ./configure should check the installed version of texinfo and print a warning if it's 4.13? Until errors and bad output are fixed, I would even suggest to abort for a version larger than 4.13. added to the tracker: https://code.google.com/p/lilypond/issues/detail?id=3382 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make error: please check usage.makeinfo.log for errors
2013/5/28 Federico Bruni fedel...@gmail.com maybe ./configure should check the installed version of texinfo and print a warning if it's 4.13? tonight I'll downgrade texinfo and try again ok, I've downgraded to v4.13 in debian stable and pinned the package I also had to (re?)install libtext-unidecode-perl now I can compile the doc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Final double bar that ends written music.
2013/5/27 Ted kielh...@amerimailbox.com I am new to Lilypond and one frustration was to find out how to write the final double bar. Some simple examples should include this early in the introductory tutorials. I searched the web to find \bar |. but I did not see it in the manuals. Did you use the index of the Notation Reference? If you search bar lines you get to: http://lilypond.org/doc/v2.17/Documentation/notation/bars#bar-lines and \bar |. is the first example. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
patch: add some italian words in the Music Glossary
This is a trivial patch: may I just push it? To staging or master? 0001-Doc-add-some-missing-italian-translations-in-Music-G.patch Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: patch: add some italian words in the Music Glossary
2013/4/14 David Kastrup d...@gnu.org Never push anything to master: that breaks our system. Push to staging, and it will arrive in due time in master. Or not, depending on whether it actually passes all tests. ok, done ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
few questions on minor errors in LM and website
1) A small error in Documentationo/learning/tweaks.itely:
@node The force-hshift property
@unnumberedsubsubsec The @code{force-hshift property}
It should be:
The @code{force-hshift} property
2) http://www.lilypond.org/productions.html
A critical edition of Tommaso Traetta’s *Enea nel Lazio (1760)*, opera
series with libretto by Vittorio Amedeo Cigna-Santi, in four parts:
Part
Onehttp://www.academia.edu/1987651/Enea_nel_Lazio_opera_riformata_prima_lazione_poi_le_parole_-_Partitura_1_4_Part
Twohttp://www.academia.edu/1994533/Enea_nel_Lazio_opera_riformata_prima_lazione_poi_le_parole_-_Partitura_2_4_
Part
Threehttp://www.academia.edu/1994558/Enea_nel_Lazio_opera_riformata_prima_lazione_poi_le_parole_-_Partitura_3_4_
Part
Fourhttp://www.academia.edu/1996242/Enea_nel_Lazio_opera_riformata_prima_lazione_poi_le_parole_-_Partitura_4_4_
Created
by Luca Rossetto Casel http://unito.academia.edu/LucaRossettoCasel for
his Ph.D. Thesis.
Opera series? Or opera seria?
I'm very ignorant in classical music, but series doesn't make sense to me
and I found this:
http://en.wikipedia.org/wiki/Opera_seria
Thanks
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: point-and-click in SVG
2013/4/3 Graham Percival gra...@percival-music.ca The archives show a few half-hearted attempts to get this working, but no actual patches other than Mike's lily dances patch from Dec 2010 which wasn't merged. I've got a patch which adds point-and-click, https://codereview.appspot.com/8273045 Hi Graham really interesting patch! You created a new issue (3293) in the tracker but there was an old issue for point-and-click in SVG: https://code.google.com/p/lilypond/issues/detail?id=1372 Please merge the two issues and remember to add the issue number in your commit message. Thanks Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Snippet broken in 2.17.14
2013/4/5 Phil Holmes em...@philholmes.net The snippet http://lilypond.org/doc/v2.17/**Documentation/snippets/** contexts-and-engravers#**contexts-and-engravers-** engravers-one_002dby_002donehttp://lilypond.org/doc/v2.17/Documentation/snippets/contexts-and-engravers#contexts-and-engravers-engravers-one_002dby_002doneno longer produces sensible output. It was broken by http://code.google.com/p/**lilypond/issues/detail?id=3225http://code.google.com/p/lilypond/issues/detail?id=3225 See attached images from current unstable docs and stable docs. I'm not sure whether this a bug in the snippet or the enhancement. Maybe this is related: http://code.google.com/p/lilypond/issues/detail?id=3290 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond.org down
it's up now 2013/3/11 Phil Holmes em...@philholmes.net For me, and for http://www.**downforeveryoneorjustme.com/http://www.downforeveryoneorjustme.com/. Guess we wait a while and then try to contact the admin. -- Phil Holmes __**_ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/**listinfo/lilypond-develhttps://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: build: missing explicit dependency?
Il 10/03/2013 01:44, Julien Rioux ha scritto: Yes, CG does lists metapost. But this peckage was not auto-installed as a dependency from other previous packages. I agree that this looks like something that the configure script should have caught. Thanks for reporting it, we should open an issue for it. added to the tracker: http://code.google.com/p/lilypond/issues/detail?id=3233 -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: texinfo_document.po files encoding
2013/2/28 Jean-Charles Malahieude lily...@orange.fr It is because the files are in US-ASCII and not in UTF-8. I have to admit it has been a pain for me having to type @'a instead of just à or @ for a non breakable space like in the old times of LaTeX (or even lyrics in LilyPond 1.3.84). Do you mean they _have to_ be ASCII? It looks weird... why not using UTF-8? The italian file is UTF-8, for example. Why french and german are ASCII? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
texinfo_document.po files encoding
I've received the texinfo_document.po file from the Translation Project. While looking at other languages po files to understand what to translate and what to leave untraslated, I've noticed some strange characters. Probably because these files are saved as ASCII instead of UTF-8? $ file texinfo_document-5.0.fr.po texinfo_document-5.0.fr.po: GNU gettext message catalogue, ASCII text For example: Forme Sp@'eciale http://translationproject.org/domain/texinfo_document.html -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: opening bar check crashes the compiler
Il 25/02/2013 03:33, Steve Yegge ha scritto:
Hi Thomas, thanks for the reply.
I think there are two issues at play here. One issue is that user input
should never crash the program. It took nontrivial effort to track down
why my scores were crashing after upgrading Lilypond (since in some
distant past version, it didn't crash.) Even if the input is invalid, a
compiler error with line number information is greatly preferable to
seeing bus error with no diagnostics.
The second issue is that disallowing bar checks at the beginning of a
section hampers composability. It turns out that my bar check is, in
fact, positioned at a place where a bar line is expected. Here is a
slightly larger input file that demonstrates the problem:
\version 2.16.0
introRest = {
\set Score.skipBars = ##t
R2.*11
\unset Score.skipBars
}
orch = {
\key g \minor
\time 3/4
\tempo Andante 4 = 84
\override TupletBracket #'stencil = ##f
\introRest
}
intro = \relative c {
| r4 r d
}
music = {
\intro
}
\score {
\new Staff { \orch \music }
}
\score {
\unfoldRepeats
\music
\midi {
\context {
\Score
}
\context {
\Voice
\remove Dynamic_performer
}
}
}
My bar check that's crashing the program is not at the beginning of the
music. It does fall on a bar line, which is consistent with the docs.
The problem is in the \midi block, which in your example indeed starts
with a bar check.
It improves composability of sections -- copying them, commenting them
out, moving them around -- if you don't have to special-case bar checks
happening at the beginning of a section.
If we agree that this is a bug then I'll go ahead and report it.
no need to report it on bug-lilypond, I've already added the issue here:
http://code.google.com/p/lilypond/issues/detail?id=3205
you can add any comment there
thanks for the report
--
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: opening bar check crashes the compiler
Il 24/02/2013 06:46, Steve Yegge ha scritto:
Here's a small input file which for me produces a bus error when
compiled with version 2.16.2 on OS X 10.7.5 (intel):
\version 2.16.2
music = {
| d
}
\score {
\new Staff { \music }
}
\score {
\music
\midi {
\context {
\Score
midiInstrument = #acoustic guitar (steel)
}
}
}
If you remove the | bar-check, it no longer crashes.
This was happening in 2.14.x as well.
Regards,
-steve
It's not just the bar check.
The following snippet (one score block) compiles fine:
\version 2.16.2
music = {
| d
}
\score {
\new Staff { \music }
\layout{}
\midi {}
}
while this (two score blocks) fails:
music = {
| d
}
\score {
\new Staff { \music }
\layout{}
}
\score {
\music
\midi {}
}
The right mailing list to report bugs is bug-lilyp...@gnu.org
However, I'm not sure this is a bug, as there's no point in starting a
music with a bar check. On the other hand I think that we should expect
lilypond to print a warning in this case.
Comments from developer appreciated.
Thanks
--
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bug in articulate.ly
Il 24/02/2013 16:02, David Kastrup ha scritto: Can the bug team register a bug for it? If we don't get a response in about two days from the original author, I'd suggest reverting it. added as: http://code.google.com/p/lilypond/issues/detail?id=3204 -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: opening bar check crashes the compiler
Il 24/02/2013 17:54, Thomas Morley ha scritto:
Some more investigation:
The problem seems to be related to \midi
\score {
{ | d }
\midi { }
}
returns a segfault with 2.16.1 and 2.17.12
I can confirm it on 2.16.2 and 2.17.3
Thanks for the investigation and the minimal example.
Added here:
http://code.google.com/p/lilypond/issues/detail?id=3205
--
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make website' error: makeFooter function of website_post.py
Il 13/01/2013 13:26, Phil Holmes ha scritto: Aha. It's because you're missing a bugfix that's in master. Have a look at f1e9b96641440bf81e701f01dbad61ed2ca6a83e - you should be able to edit website_post.py manually to apply that fix. yes, it works fine on master thanks -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Re: How to extract PDF of translated documentation?
2013/1/14 Harmath Dénes harmathde...@gmail.com As responsible for the Hungarian translation, what are the exact steps I should perform in order to solve this? Hi Darmath I don't think it's your duty, the problem is in the build system. Honestly, I don't know why the links change depending on the language. The first step is waiting for some developer to fix this bug: http://code.google.com/p/lilypond/issues/detail?id=3107 Then we'll see if there's any error in any language ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Re: How to extract PDF of translated documentation?
2013/1/14 David Kastrup d...@gnu.org The only translations that appear to be thoroughly maintained are the Spanish and French translation, with the German translation following close behind. Well, the italian translation is far to be completed but it _is_ maintained. It would a lamentable state of affairs if we had translations that are not maintained because of a lack of translators and manpower. But this and some other mailings on the translator list rather suggest to me that we _might_ have manpower and persons feeling responsible, but that the information what they could be doing for the project does not even arrive at their doorstep. And that would not be lamentable, but stupid. If we have people enlisted and willing to do a job, we should not let their availability go to waste. Are there people willing to do translations, particularly those who actually _are_ already subscribed to the translator list, that are waiting for instructions or whatever else before they know how to get to work on making their language better supported with LilyPond? If so, we need to organize this effort better and more transparently. Probably the CG should be updated, improved and simplified. I think that at the moment it would be a bit hard for a new translator to get in. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Re: How to extract PDF of translated documentation?
2013/1/14 Werner LEMBERG w...@gnu.org I wonder what's the best way to update outdated documentation. Reading the whole documentation and checking the translation is probably quite hard and needs a lot of time. Would it be better instead to use a git repository viewer, walking over the English documentation commits and translating them commit by commit? Or do you recommend to check the differences between development releases? Hi Werner the maintenance is described here: http://lilypond.org/doc/v2.17/Documentation/contributor/documentation-translation-maintenance I use only check-translation. If you have questions let us know. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Re: How to extract PDF of translated documentation?
2013/1/14 Werner LEMBERG w...@gnu.org So how can we improve the efficiency of our current translation work force, and how can we make it easier for people to help in a way that does not step on anybody's toes and actually leads to better results? Yeah. Let's assume that I would like to quickly improve various places of the German translation (for example, just fixing a typo). What should I do? Directly committing to `staging' doesn't seem appropriate... Werner All the translation work should be made in the translation branch. git checkout -b translation origin/translation and push changes to translation. If you just fix a typo and don't update anything, _don't_ change the committish in the document. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Re: How to extract PDF of translated documentation?
Il 14/01/2013 20:32, David Kastrup ha scritto: Redundancy of contributors, or redundancy in CG to make things much easier to find? Redundancy of contributions. We currently have one person does the translation once and nobody including himself looks at it ever after. I've had a look here: http://lilypond.org/translated.html and it seems that this is true for any language except french and italian. As you aptly observed, that's the best you yourself can barely manage for Spanish. But I can't believe you to be the only LilyPond user natively speaking Spanish. The main qualification we should be requiring from translators and translation revisors is good command of language. Not ability to juggle with git and other technical stuff. My proofreader, Luca, is a huge help for the quality of italian words and also the choice of musical terms (he studied music, while I'm just self-taught and very ignorant in notation theory). He's scared away by the technical stuff (which I'm happy to handle) and I remember that he offered to help me provided that he didn't have to learn git, texinfo and the build system. So technical stuff can be handled by just one person per language. Editing the italian words of a text file, ignoring any strange texinfo command, and producing a diff file, is not an hard task... especially for a LilyPond user :-) So how can we move in a direction where translation work is less technically challenging? I believe that with regard to the program string translation (gettext, po, pot files or whatever), there is some sort of process that detaches the language teams from the technical details. Maybe we can move more in that direction for the manual texts as well? I don't have good suggestions here at the moment, but I should think that there is potential for getting more people involved for making their own language look better-suited for reading about and working with LilyPond. I've never worked at the translation of a manual which uses gettext. The Debian Handbook can be a source of inspiration: http://debian-handbook.info/contribute/ http://anonscm.debian.org/gitweb/?p=debian-handbook/debian-handbook.git;a=blob;f=README.translators;hb=master https://fedorahosted.org/publican/ http://debian.weblate.org/projects/debian-handbook/ Did you know Weblate (it's GPL)? http://weblate.org/en/ -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to extract PDF of translated documentation?
Il 13/01/2013 11:24, David Kastrup ha scritto: which is quite nice as an introduction. make doc apparently also builds a PDF version of it which is fine for that purpose. However, it apparently does not build a PDF of the German (or any) translation. HTML, no? There is web-big-page.de.html -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to extract PDF of translated documentation?
Il 13/01/2013 11:45, Francisco Vila ha scritto: Oh sorry! you mean PDF of the translation of the web document. http://www.lilypond.org/development.de.html links to web.de.pdf but you are right, this is a dead link. the dead links to web.xx.pdf occur only on certain languages: fr, de, cs, hu I'm CCing translation. Can anyone have a look at that? -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make website' error: makeFooter function of website_post.py
Il 13/01/2013 11:50, Phil Holmes ha scritto: Pretty certain this is likely to be a bug in the implementation of http://code.google.com/p/lilypond/issues/detail?id=847 However, I don't see this error. Could you confirm the exact command you issue in order to generate the problem, please? A simple 'make website', after a successful 'make doc'. Please note that I'm on the translation branch and I'm currently at this commit (because I'm waiting for the proofreader to send comments to my latest translations): commit 52f4f425dcae9ba597eba8c50ac207b14f70dcc5 Author: Jean-Charles Malahieude lily...@orange.fr Date: Sun Dec 23 20:20:44 2012 +0100 -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
'make doc' should generate translated PDF files of website [WAS: Re: How to extract PDF of translated documentation?]
Il 13/01/2013 11:58, Francisco Vila ha scritto: 2013/1/13 Federico Bruni fedel...@gmail.com: Il 13/01/2013 11:45, Francisco Vila ha scritto: Oh sorry! you mean PDF of the translation of the web document. http://www.lilypond.org/development.de.html links to web.de.pdf but you are right, this is a dead link. the dead links to web.xx.pdf occur only on certain languages: fr, de, cs, hu for 'es' the link is alive but points to untranslated web.pdf Same for italian and nederlands. Curiously, spanish doc v2.15 links to web.es.pdf (therefore it's broken): http://lilypond.org/doc/v2.15/Documentation/web/development.es.html Anyway, translated versions of PDF files were never generated (going back up to 2.13): http://lilypond.org/doc/v2.15/Documentation/ We would expect to have the translated PDF, as in any other manual. I've opened an issue in the tracker: http://code.google.com/p/lilypond/issues/detail?id=3107 I've CCed also lilypond-bug (sorry for the big cross-posting). -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
'make website' error: makeFooter function of website_post.py
Hi I can't compile the website. Actually, everything is compiled except the manuals: out-website/website/doc/ is missing. Here's the error: ls out-website/cs/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/cs/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.cs hard out-website/cs/ out-website/website/; ls out-website/de/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/de/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.de hard out-website/de/ out-website/website/; ls out-website/es/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/es/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.es hard out-website/es/ out-website/website/; ls out-website/fr/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/fr/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.fr hard out-website/fr/ out-website/website/; ls out-website/hu/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/hu/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.hu hard out-website/hu/ out-website/website/; ls out-website/it/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/it/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.it hard out-website/it/ out-website/website/; ls out-website/ja/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/ja/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.ja hard out-website/ja/ out-website/website/; ls out-website/nl/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/nl/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.nl hard out-website/nl/ out-website/website/; ls out-website/zh/*.html | xargs grep -L 'UNTRANSLATED NODE: IGNORE ME' | sed 's!out-website/zh/!!g' | xargs python /home/fede/lilypond-git/scripts/build/mass-link.py --prepend-suffix=.zh hard out-website/zh/ out-website/website/; python /home/fede/lilypond-git/scripts/build/website_post.py out-website/website Traceback (most recent call last): File /home/fede/lilypond-git/scripts/build/website_post.py, line 179, in module lang_footer = makeFooter (file_base, lang) File /home/fede/lilypond-git/scripts/build/website_post.py, line 132, in makeFooter return footer % locals () KeyError: 'me' make[1]: *** [out-website/website/index.html] Error 1 make[1]: Leaving directory `/home/fede/lilypond-git' make: *** [website] Error 2 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug Squad Rota
Il 07/01/2013 02:04, Colin Hall ha scritto: I would prefer Sunday, but Saturday can be ok. I was thinking that Marek should get some relief as he has been doing two days for a long time. If you took Sunday, Federico, I could take one of Marek's slots. ok for me ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug Squad Rota
Il 06/01/2013 14:35, Ralph Palmer ha scritto: I have a request to make. I live in the eastern U.S., and at least some of the Bug Squaders appear to live in Europe. My usual (most reliable) time on the computer on the weekend is in the morning. As a result, I frequently don't have any bugs to evaluate when I get up on Saturday morning, and I frequently don't get back to the Bug List until Sunday morning. By that time, someone in Europe has usually snagged my Saturday bugs. In the interest of equity of labor, I'm requesting that someone who has one of the weekdays (where I'm more often at the computer later in the day) switch with me. If no one wishes to switch, I can stay on Saturday, but I probably won't catch as many bugs as I ought. Hi Ralph I was discussing privately with Colin the idea of joining the Bug Squad. I'm still waiting for the confirmation that reading lilypond-auto is not a requisite (my email capacity is saturated), but if that's the case I'd like to choose one of the weekend days. Colin has Sunday and Monday currently. I would prefer Sunday, but Saturday can be ok. Let me know -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc: cannot import name TexModule (but dblatex is now arequireddependency)
Il 30/12/2012 09:06, Federico Bruni ha scritto: I can't find any information about dblatex developers. I'll send a bug report to Debian bug tracking system. Ok, problem solved thanks to the Debian maintainer: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696976 The problem was the python package merengue (installed in /usr/local with pip), which contains a file called plugins/TexModule.py After running 'pip uninstall merengue' dblatex works fine again. The following command helped to understand what was happening under the hood: strace -e open dblatex example.xml Cheers -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc: cannot import name TexModule (but dblatex is now arequireddependency)
Il 29/12/2012 17:05, Federico Bruni ha scritto: Il 29/12/2012 16:51, David Kastrup ha scritto: I have no idea, but an incomplete installation of dblatex or one that is unable to find its own parts seems plausible. The file which contains TexModule is plugins.py I have that file both under python2.6 and python2.7 Now I've tried removing the debian package and installing the package from PyPI: pip install dblatex But I get the same error. Can you try the attached file (taken from dblatex documentation)? Does it work for you? $ dblatex example.xml Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3.4) === Warning: the root element is not an article nor a book Warning: example wrapped with article Build example.pdf Unexpected error occured Error: cannot import name TexModule I can't find any information about dblatex developers. I'll send a bug report to Debian bug tracking system. -- Federico !DOCTYPE example PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; exampletitleA DSSSL Function/title programlisting (define (node-list-filter-by-gi nodelist gilist) ;; Returns the node-list that contains every element of the original ;; nodelist whose gi is in gilist (let loop ((result (empty-node-list)) (nl nodelist)) (if (node-list-empty? nl) result (if (member (gi (node-list-first nl)) gilist) (loop (node-list result (node-list-first nl)) (node-list-rest nl)) (loop result (node-list-rest nl)) /programlisting /example ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
make doc: cannot import name TexModule (but dblatex is now a required dependency)
This is a followup to this thread: http://lists.gnu.org/archive/html/lilypond-devel/2012-08/msg00716.html I used to work around the problem by removing dblatex. But dblatex is now a required dependency (see issue 2529) and configure won't create the Makefile if dblatex is not installed. Can you help me finding what's the problem? John suggested that it could be a compatibility issue with some xml-related dependency of dblatex on my system. I've had a look to my /usr/local/lib/python* packages but I can't find any package which may be related. I've already run 'make distclean' and tried from scratch, but I cannot compile anymore. Find attached the log. Here's the output: cd ./out-www /home/fede/lilypond-git/scripts/build/out/run-and-check pdflatex -halt-on-error suffix-lytex.tex suffix-lytex.pdflatex.log LILYPOND_VERSION=2.17.10 /usr/bin/python -tt ../../../scripts/lilypond-book.py -I ./ -I ./out-www -I ../../../input -I /home/fede/lilypond-git/Documentation -I /home/fede/lilypond-git/Documentation/snippets/out -I ../../../input/regression/ -I /home/fede/lilypond-git/Documentation/included/ -I /home/fede/lilypond-git/mf/out/ -I /home/fede/lilypond-git/mf/out/ -I /home/fede/lilypond-git/Documentation/pictures -I /home/fede/lilypond-git/Documentation/pictures/./out-www --process='/home/fede/lilypond-git/out/bin/lilypond -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out-www --redirect-lilypond-output --loglevel=WARN --lily-output-dir /home/fede/lilypond-git/out/lybook-db --pdf -o ./out-www suffix-lyxml.lyxml cd ./out-www /home/fede/lilypond-git/scripts/build/out/run-and-check dblatex suffix-lyxml.xml suffix-lyxml.dblatex.log Please check the logfile suffix-lyxml.dblatex.log for errors make[4]: *** [out-www/suffix-lyxml.pdf] Error 1 make[4]: Leaving directory `/home/fede/lilypond-git/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/fede/lilypond-git/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/fede/lilypond-git/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/fede/lilypond-git' make: *** [doc-stage-1] Error 2 Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3.4-2) === Build suffix-lyxml.pdf A possible reason for transformation failure is invalid DocBook (as reported by xmllint) Error: cannot import name TexModule ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc: cannot import name TexModule (but dblatex is now arequireddependency)
Il 29/12/2012 16:51, David Kastrup ha scritto: I have no idea, but an incomplete installation of dblatex or one that is unable to find its own parts seems plausible. The file which contains TexModule is plugins.py I have that file both under python2.6 and python2.7 This is what I get: # grep TexModule `dpkg -L dblatex` 2/dev/null /usr/share/pyshared/dbtexmf/dblatex/grubber/bibtex.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/bibtex.py:class BibTex(TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/bibtopic.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/bibtopic.py:class Bibtopic(TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/dvips.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/dvips.py:class Module (TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/index.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/index.py:class Index(TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/index.py:class Module (TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/pdftex.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/pdftex.py:class Module (TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/plugins.py:All the modules must be derived from the TexModule class. /usr/share/pyshared/dbtexmf/dblatex/grubber/plugins.py:class TexModule (object): /usr/share/pyshared/dbtexmf/dblatex/grubber/ps2pdf.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/ps2pdf.py:class Module (TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/xetex.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/xetex.py:class Module (TexModule): /usr/share/pyshared/dbtexmf/dblatex/grubber/xr-hyper.py:from plugins import TexModule /usr/share/pyshared/dbtexmf/dblatex/grubber/xr-hyper.py:class Module(TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/xr-hyper.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/xr-hyper.py:class Module(TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/xetex.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/xetex.py:class Module (TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/ps2pdf.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/ps2pdf.py:class Module (TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/plugins.py:All the modules must be derived from the TexModule class. /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/plugins.py:class TexModule (object): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/pdftex.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/pdftex.py:class Module (TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/index.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/index.py:class Index(TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/index.py:class Module (TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/dvips.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/dvips.py:class Module (TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/bibtopic.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/bibtopic.py:class Bibtopic(TexModule): /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/bibtex.py:from plugins import TexModule /usr/lib/python2.6/dist-packages/dbtexmf/dblatex/grubber/bibtex.py:class BibTex(TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/bibtex.py:from plugins import TexModule /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/bibtex.py:class BibTex(TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/bibtopic.py:from plugins import TexModule /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/bibtopic.py:class Bibtopic(TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/dvips.py:from plugins import TexModule /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/dvips.py:class Module (TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/index.py:from plugins import TexModule /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/index.py:class Index(TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/index.py:class Module (TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/pdftex.py:from plugins import TexModule /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/pdftex.py:class Module (TexModule): /usr/lib/python2.7/dist-packages/dbtexmf/dblatex/grubber/plugins.py:All the modules must be derived from the TexModule class.
Re: New Catalan PO file for 'lilypond' (version 2.15.95)
Il 25/12/2012 19:23, David Kastrup ha scritto: What actually worries me is: All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ And this shows: The current template for this domain is lilypond-2.15.95.pot which sounds seriously outdated. I think that it's ok. We usually update this file just before the release of a new stable. As you can see here: http://translationproject.org/domain/lilypond.html translated files are always some development version and the minor number is quite high (just before the release of stable). I think that it's up to Jean-Charles uploading the new pot file. Then we translators get the notification and update the file for the coming release. -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Missing issue tracker
Il 10/12/2012 22:22, Thomas Morley ha scritto: You can see the patch at http://codereview.appspot.com/6923043/ but no issue on the tracker was generated. Colin, I'm sorry about that. AFAIK, you should first create the issue and then upload the patch. git-cl is able to recognize which issue is related to your patch (can't remember how, I did it just once.. have you checked the CG?). The last time this happened, Colin created an issue for me. Am I allowed to do it myself? Is there something special to observe? I think that you can create it yourself, as you are a committer in this list: http://code.google.com/p/lilypond/people/list Anyway, wait for a reply from some developer -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Your Patches
Il 25/11/2012 17:41, Francisco Vila ha scritto: This message belongs to a private thread I can not see. Would you mind sending the actual patches so that I can know what are we talking about? I think that it's about this patch: https://codereview.appspot.com/6852077 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [talk] suggestion: redesign sponsoring page.
Il 09/11/2012 18:55, Janek Warchoł ha scritto: - split the remainder of the page between features for hire (one-time bounties) and continuous support (giving money to an individual without setting what exactly he has to do, just to enable him to continue his work - what we do with David now). I suggest putting a link to the list of bounties: http://code.google.com/p/lilypond/issues/list?can=2q=label%3ABounty ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [talk] suggestion: redesign sponsoring page.
Il 10/11/2012 11:04, David Kastrup ha scritto: Federico Brunifedel...@gmail.com writes: I suggest putting a link to the list of bounties: http://code.google.com/p/lilypond/issues/list?can=2q=label%3ABounty I think the idea of Bounty was pretty much retired. I don't think any have been proposed in the last year, and it is very much questionable that any remaining listed bounties will be easily collectable. Collecting money is an issue, I understand. Maybe a developer who decides to work on a bounty feature could contact people who offered money and set some conditions before the work starts. For example, I know that two developers (that I respect and trust) will probably work, in the coming months, on a feature really important for me. I'd be happy to pay in advance and whatever the final results will be. Which means: even if they won't be able to cover all the possible situations, I'd still be happy to see implemented all the basic features related to that area. I tried collecting on a number of low-hanging or not so low-hanging bounties probably a year ago or so, and it has been my experience that the process of trying to collect the bounties (even though I eventually managed to get about 75%) amounted to a disproportionate effort and, quite worse, was a major turnoff. It turns out that even a bounty of €25 or similar throws many people into bill-paying mode where they question every achievement by default, delay payment until they have have found time and leisure to corroborate that the stuff does what they think they wanted to have (partly different from what they specified they wanted to have) when they were still using LilyPond etc etc. That's sad.. Well, keeping this experience in mind, you might consider trying to work again on a bounty and ask people to accept your conditions before starting to work on it. If they accept it, fine; otherwise, it's ok anyway, at least you've tried. So it has been at least my experience that with regard to the balance of motivating and demotivating experiences, the bounty system was not working out. I'd recommend against linking to the remaining bounties. I think that any user will be happier to invest some money on a specific feature he/she really wants rather than on general development. Why wasting this opportunity? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.pot polluted
Il 03/11/2012 19:04, Jean-Charles Malahieude ha scritto: Hi John and all, I just noticed that, because the out of tree build, lilypond.pot gets polluted by personal path, what does not happen with an in tree build. e.g. we get, when out of tree : #: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174 #: /home/jcharles/GIT/Mentor/lily/parser.yy:188 msgid Too much lookahead msgstr #: parser.yy:466 parser.yy:736 parser.yy:803 #: /home/jcharles/GIT/Mentor/lily/parser.yy:466 #: /home/jcharles/GIT/Mentor/lily/parser.yy:736 #: /home/jcharles/GIT/Mentor/lily/parser.yy:803 msgid bad expression type msgstr instead of just : #: parser.yy:174 parser.yy:188 msgid Too much lookahead msgstr #: parser.yy:466 parser.yy:736 parser.yy:803 msgid bad expression type msgstr The full paths are obviously wrong, but relative paths (either to po/ or root tree) would be a benefit for translators, because po editors provide buttons which open the source file:line for each string. Now the paths are missing and the editor can't find the file. Translators are not developers, but sometimes looking at the context can help. When I submitted my translation to the italian proofreader list, I received complaints about that. Other projects I've contributed to use relative paths, so this should be possible. -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG: fixed wrong link to Contact
2012/10/24 James pkx1...@gmail.com: This passes a make doc - I checked just in case - I see no reason why you cannot just push this one char change directly to staging. I can't because I'm not on my laptop (until Saturday). Could you push it for me? Thanks ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: svg output
2012/10/23 Joram Berger joram.no...@gmx.de: Even though things are perhaps a little bit different, I would suggest to include svg (or the whole backend-options) into formats, if possible. Because thats essentially what the user wants: get the output in the format svg. there's an old issue still open for this: http://code.google.com/p/lilypond/issues/detail?id=967 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: svg output
2012/10/23 Joram Berger joram.no...@gmx.de: Ok, I've overlooked that. Btw: SVG output is really nice! I agree. Personally, I'd love to see it used in the documentation. I wonder if it's possible to build the documentation using SVGs instead of PNGs.. The documentation would be lighter, faster when browsed online and it would be possible to immagine advanced features (e.g. point-and-click from image to source through some javascript). Possible cons: - browser compatibility (sensible persons care for it, but I'm not sensible... especially when it's about _that_ browser) - output bugs in SVG? I have no idea if here's any, but this would be the most serious drawback I can think of ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: svg output
2012/10/23 David Kastrup d...@gnu.org:
Texinfo does not support SVG as far as I know. And neither do typical
info readers like Emacs if I remember correctly.
This page seems to confirm your statement:
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Image-Syntax.html#Image-Syntax
But then what about this?
BTW, as for the HTML, if you want to use your .svg's, add one more optional
argument:
@image{foo.svg}
http://lists.gnu.org/archive/html/help-texinfo/2011-10/msg7.html
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: svg output
2012/10/23 James pkx1...@gmail.com: Do all browsers accept output in SVG what about PDF readers? I think that it should be limited to html. The main problem is IE, because the basic support was added only in version 9: http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Support_for_SVG_in_web_browsers But there are some turnarounds. I'm rather sceptical about SVG output only that we do get occasionally gripes about LilyPond SVG output and Inkscape (for example), implying that our SVG backend (or whatever it is) is not 100% perfect, at least PNGs are 'just' images. My suggestion was just about having an option to compile images in the doc as SVG. Just to see what can happen.. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy report
2012/10/22 Phil Holmes m...@philholmes.net: WARNING: Unable to find node 'Alturas' in book snippets. WARNING: Unable to find node 'Alturas' in book snippets. [snip] WARNING: Unable to find node 'Anotaciones editoriales' in book snippets. That's issue 2266. I added some comments in August with some hints about the problems.. It would be nice to fix it, but I think it's a build bug... muddy waters... *** Undefined node `Títulos y cabeceras' in @ref (in out-www/notation/editorial.texi l. 1293 in @funindex) Max error number exceeded this should be the error which makes the build fail ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.16.1
2012/10/21 David Kastrup d...@gnu.org: I hope translati...@lilynet.net is not a dead list (or did its list server die, or is it moderated with no moderator ever approving posts?). At any rate, I sent several messages. The first I can only find in my mailing logs (Friday), but not in my mailing list archives. Too bad. Probably sitting in the translator list moderation queue. I append the second one which presumably got a reply from Francisco only because I replied to an old thread, thus directing a direct copy to him as well. Yes, you are not allowed to post on translators mailing list, in fact your email is missing from the archives. It's just because you are not subscribed, I don't think there's any moderation. We can see only the reply from Francisco: http://lilypond-translations.3384276.n2.nabble.com/Git-translation-branch-policy-change-merge-with-and-from-stable-2-16-td7572469i20.html A bit confusing, since it is an old thread and I didn't receive your email before Francisco's reply. Maybe next time write to Francisco and he will forward your message to translators list, keeping you in CC. Or ask Valentine to be subscribed (it's a low volume list). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
make scripts on Windows (cygwin)
I'd like to update the italian translation before 2.16.1 release. I have a problem: I'm abroad until Friday and I only have a Windows laptop. I guess that you will recommend LilyDev. Not tried yet, as I'm not really interested in compiling Lilypond. I just need to be able to run some make commands for the translation maintenance. I've installed Cygwin and the packages needed for compiling (well, I hope so). But I get an error when I run configure: $ ./configure configure: error: cannot run /bin/sh stepmake/bin/config.sub $ sh sh.exe shasum shimeng.dll shrpubw.exe sha1sum.exe shdocvw.dll shimgvw.dll shsetup.dll sha224sum.exe shell32.dll shlwapi.dll shsvcs.dll sha256sum.exe shellstyle.dll shmtool.exe shuf.exe sha384sum.exe shfolder.dllshopt shunimpl.dll sha512sum.exe shgina.dll shpafact.dllshutdown.exe shacct.dll shift shred.exe shwebsvc.dll $ sh configure configure: error: cannot run /bin/sh stepmake/bin/config.sub Can any Windows user help me? Thanks, Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [translations] Git translation branch policy change: merge with and from stable/2.16
2012/10/21 Jean-Charles Malahieude lily...@orange.fr: So I really think we should move translations over, and live with the documentation of 2.16 being the best we could make it for 2.16. Do we translators first update what you just merged from stable? I'm on it at the present (my wife is conducting a choir rehearsal of King Arthur this afternoon). Yes, please wait for the update (at least from me). Then we can move to 2.17, I agree. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make scripts on Windows (cygwin)
2012/10/21 David Kastrup d...@gnu.org: Federico Bruni fedel...@gmail.com writes: [..] I've installed Cygwin and the packages needed for compiling (well, I hope so). If you are not interested in wasting the rest of your week (and probably the next month) throwing good time after bad time fighting things that almost, but not quite work, you should seriously give LilyDev a try. Its main motivation is not having gcc available (that one is perfectly available standalone on Windows) but rather all the little things when you just need to be able to run some make commands. I've installed LilyDev: very easy and fast (except for 1 GB download). Disclaimer: I have not touched either Windows, Cygwin, or virtual environments for years. But I still habe the scars to show. :-) But I get an error when I run configure: $ ./configure configure: error: cannot run /bin/sh stepmake/bin/config.sub $ sh sh.exe shasum shimeng.dll shrpubw.exe sha1sum.exe shdocvw.dll shimgvw.dll shsetup.dll sha224sum.exe shell32.dll shlwapi.dll shsvcs.dll sha256sum.exe shellstyle.dll shmtool.exe shuf.exe sha384sum.exe shfolder.dllshopt shunimpl.dll sha512sum.exe shgina.dll shpafact.dllshutdown.exe shacct.dll shift shred.exe shwebsvc.dll $ sh configure configure: error: cannot run /bin/sh stepmake/bin/config.sub Can any Windows user help me? Well, Cygwin has an idea of where /bin is situated. ls /bin might tell you that. Or maybe not. yes, he knows it and sh is there: $ ls /bin | grep ^sh sh.exe sha1sum.exe sha224sum.exe sha256sum.exe sha384sum.exe sha512sum.exe shasum shmtool.exe shred.exe shuf.exe No idea why it can't run that command. Nevermind, I'll use LilyDev. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.16.1
Il giorno 21/ott/2012 05:17, David Kastrup d...@gnu.org ha scritto: Phil Holmes em...@philholmes.net writes: David, I see you've done a lot of moving updates into 2.16.1. When do you expect to want a release for this? I've asked on the translator list whether they want to get something translated from all the cherry-picking, and feedback is incomplete yet. Hi David, When did you ask? I may have missed your email.. I think that all translators should update the inaccuracies in LM. I'll try to do it today, even if I'm abroad and with a Windows laptop. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [GLISS] basics
Il 23/09/2012 15:08, Thomas Morley ha scritto: So I thought it might be an idea to start threads on national lists/forums about it and after same time (a week?) collect and list the complains, ideas, proposals. The advantage would be to reach a larger amount of users. And, not the least advantage, not to annoy David with any half-baked user-thought during that week.:) I started with the german LilyPond-Forum: http://www.lilypondforum.de/index.php?topic=1213.0 What do you think about getting more basic informations this way? Eluze, Federico, Francisco would you like to join this and post sth similar on your national lists? Hi Harm there's not a lilypond-it list yet, because italian users seem to be few at the moment. I've counted about 10 italians subscribed to lilypond-user so far and I think that most of them would subscribe to the lilypond-language list if really interested in joining the discussion. -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
2.16 backports [WAS: LSR-image cropped]
Il 18/09/2012 11:59, David Kastrup ha scritto: Of course,_planning_ the next round of LSR updates is fine. It is not like there will be functional changes in 2.16 any more (check URL:code.google.com/p/lilypond/issues/list?can=1q=Label%3DBackport for more info, disregarding the 2.15 or earlier labels), so if you get a file ported over, you should not need to revisit it again except in very, very limited circumstances. You may want to add the label Backport to issue 2791 (inaccuracies in LM). I want to include those fixes in my translation patch, that I'd like to be backported to 2.16.1 I'm still waiting for the proofreader's review... Hopefully within end of September I'll push it to translation branch and let you know the commit id. -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
release 2.16.1
Can you announce here the release of 2.16.1 at least a week before the actual release? So translators will have time to complete their works. I have a patch which will be ready next week and I hope it won't miss next stable release. Thanks -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: slides-in-tablature.ly snippets: string numbers of hided notes arevisible
Il 02/09/2012 12:13, Phil Holmes ha scritto: Well - I've done that, but it appears that the snippet actually only works properly on 2.16. Using the LSR and on my own machine with 2.14 I get no numerals over the normal staff, and little zeros on the tabstaff. If you know how to fix that, please let me know. Yes, it works properly only in 2.16. Little zeros on tabstaff is because \hideNote didn't include TabNoteHead, see issue 2480 (fixed 2.15.38). The strange signs on tabstaff (in 2.14.2) are related to issue 1459. About no numerals over normal staff in 2.14.2, see previous messages from Patrick and David. In 2.14.2 I used the following snippet to get this kind of grace slides: http://lsr.dsi.unimi.it/LSR/Snippet?id=633 I think it can be removed once LSR upgrades to 2.16. Or maybe you can leave it but you'd better add a comment saying that it's just an hack for versions below 2.16 Thanks -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
slides-in-tablature.ly snippets: string numbers of hided notes are visible
I've just realized that in this snippet the hidden notes, used to make
the grace slides, have a string number which is printed (and it shouldn't).
I think that we should just remove /3 from the notes in the grace blocks
(see file attached).
All the examples in the doc using Staff + TabStaff show the string
numbers. I don't know if it's desirable, but removing all the string
numbers in this example putting this in a \layout block wouldn't be
consistent with the rest of the doc:
\context {
\Staff
\override StringNumber #'stencil = ##f
}
Can a LSR editor fix it?
Thanks
--
Federico
%% DO NOT EDIT this file manually; it is automatically
%% generated from LSR http://lsr.dsi.unimi.it
%% Make any changes in LSR itself, or in Documentation/snippets/new/ ,
%% and then run scripts/auxiliar/makelsr.py
%%
%% This file is in the public domain.
\version 2.16.0
\header {
lsrtags = fretted-strings
texidoc =
Slides can be typeset in both @code{Staff} and @code{TabStaff}
contexts:
doctitle = Slides in tablature
} % begin verbatim
slides = {
c'8\3(\glissando d'8\3)
c'8\3\glissando d'8\3
\hideNotes
\grace { g16\glissando }
\unHideNotes
c'4\3
\afterGrace d'4\3\glissando {
\stemDown \hideNotes
g16 }
\unHideNotes
}
\score {
\new Staff { \clef treble_8 \slides }
\new TabStaff { \slides }
\layout {
\context {
\Score
\override Glissando #'minimum-length = #4
\override Glissando #'springs-and-rods =
#ly:spanner::set-spacing-rods
\override Glissando #'thickness = #2
}
}
}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dblatex and Error: cannot import name TexModule
Il 28/08/2012 16:41, John Mandereau ha scritto: 2012/8/27 Federico Brunifedel...@gmail.com: I've stumbled again on this error while running make doc: http://lilypond-translations.3384276.n2.nabble.com/make-doc-error-cannot-import-name-TexModule-td7467314.html Here's the output: cd ./out-www dblatex suffix-lyxml.xml Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3.4-1) === Build suffix-lyxml.pdf A possible reason for transformation failure is invalid DocBook (as reported by xmllint) Which program or input does the invalid DocBook come from? lilypond-book, I think. I made a new try and the output seems more detailed: cd ./out-www /home/fede/lilypond-git-test/scripts/build/out/run-and-check dblatex suffix-lyxml.xml suffix-lyxml.dblatex.log Please check the logfile suffix-lyxml.dblatex.log for errors make[4]: *** [out-www/suffix-lyxml.pdf] Error 1 make[4]: Leaving directory `/home/fede/lilypond-git-test/input/regression/lilypond-book' The log file is just a copy of the output. Error: cannot import name TexModule make[4]: *** [out-www/suffix-lyxml.pdf] Error 1 make[4]: Leaving directory `/home/fede/lilypond-git/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/fede/lilypond-git/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/fede/lilypond-git/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/fede/lilypond-git' make: *** [doc-stage-1] Error 2 I have dblatex-0.3-4.fc17 installed on my regular laptop, and 0.3.4-1 (same version as yours) on Grenouille with Debian unstable, and I didn't ever hit such build error. On Grenouille with Debian unstable, dblatex 0.3.4-1 package explicitly requires Python 2.6 or 2.7, are you sure there isn't a mismatch on your system with Python, or a compatibility issue some other xml-related dependency of dblatex? My default python is 2.7.3 libxml2-utils is installed. These are the docbook packages I have installed: $ aptitude search ~idocbook i A docbook-dsssl i A docbook-utils i A docbook-xml i A docbook-xsl i A docbook-xsl-doc-html -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make website and environments variables [WAS: Web glitch]
Il 29/08/2012 14:21, Graham Percival ha scritto: On Tue, Aug 28, 2012 at 07:11:10PM +0200, Federico Bruni wrote: I can launch 'make website' now, but the css stylesheet is not loaded. Because there's no css/ directory in out-website/ Yes, because out-website/index.html is not the real website. Intead, look at out-website/website/index.html ok, I missed that thanks ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
Il 28/08/2012 12:06, Phil Holmes ha scritto: It's always been like that on Internet Explorer. On Firefox 3.6.8 on Windows, they're round. So I believe it's browser dependent, rather than a change we've made. They are round also in Chromium 20 and Firefox 10 and 12. It seems that in FF14 the radius is applied inside when hovering over the anchor (see attached image). -- Federico attachment: firefox14.png___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dblatex and Error: cannot import name TexModule
Il 27/08/2012 13:51, Federico Bruni ha scritto: The quick solution was removing dblatex. But it looks like now dblatex is a required dependency. I think that it is required if ./configure finds it installed. I haven't tried to make a clean build (which maybe could solve the problem?), because I don't have a superfast laptop and the hot temperature may force my laptop to suspend. I removed dblatex and made a distclean + clean build. Now it compiles fine. I'll try to remember to never ever install dblatex. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
Il 28/08/2012 14:51, Francisco Vila ha scritto: I think hovering is not the key. When I look carefully, I see the round corner inside also if not hovering over. The colors are very similar. Yes, I made the screenshot just to make it evident. Anyway, these examples work fine in FF14: http://www.css3.info/preview/rounded-border/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
I think I'm getting closer..
It's probably an issue with the name of css properties and the order of
them, as explained here:
http://css-tricks.com/ordering-css3-properties/
I think that FF14 needs the right property name, without -moz.
In lilypond-website.css add it here:
#tocframe ul:first-child li:first-child a {
text-indent: -999em;
background: #6aec7c url(../pictures/lily-home-nav-bg.png) no-repeat
50% 50%;
width: 9%;
/* css3 no go yet? */
-moz-border-radius-bottomleft: 7px;
-webkit-border-bottom-left-radius: 7px;
border-bottom-left-radius: 30px;
}
And you'll see the rounded corner coming back.
BTW, 'make website' doesn't exist anymore?
--
Federico
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
Il 28/08/2012 16:27, Francisco Vila ha scritto: 2012/8/28 Federico Brunifedel...@gmail.com: BTW, 'make website' doesn't exist anymore? Yes it does, but to trigger it you need a value for the LILYPOND_WEB_MEDIA_GIT environment variable. Ok, found it: http://lilypond.org/doc/v2.17/Documentation/contributor-big-page.html#environment-variables ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make website and environments variables [WAS: Web glitch]
Il 28/08/2012 16:43, Federico Bruni ha scritto: Il 28/08/2012 16:27, Francisco Vila ha scritto: 2012/8/28 Federico Brunifedel...@gmail.com: BTW, 'make website' doesn't exist anymore? Yes it does, but to trigger it you need a value for the LILYPOND_WEB_MEDIA_GIT environment variable. Ok, found it: http://lilypond.org/doc/v2.17/Documentation/contributor-big-page.html#environment-variables I can launch 'make website' now, but the css stylesheet is not loaded. Because there's no css/ directory in out-website/ This is the link (relative to out-website): link rel=stylesheet type=text/css title=Default style href=css/lilypond-website.css Any hint? My ~/.bashrc contains the following variables: LILYPOND_WEB_MEDIA_GIT=/home/fede/lilypond-extra export LILYPOND_WEB_MEDIA_GIT LILYPOND_GIT=~/lilypond-git export LILYPOND_GIT LILYPOND_BUILD_DIR=~/lilypond-git/ export LILYPOND_BUILD_DIR I added the last two variables because I hoped to fix the problem but nothing changed. Note: I do not compile in build/, just like any translator, AFAIK ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
Il 28/08/2012 18:24, Francisco Vila ha scritto: -moz-border-radius-bottomleft: 7px; -webkit-border-bottom-left-radius: 7px; border-bottom-left-radius: 30px; } Why a different radius for -moz-border-radius-bottomleft and border-bottom-left-radius? I don't know: it was already there, I just moved it down. I'll prepare a patch so you can test it yourself. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web glitch
Il 28/08/2012 19:27, Federico Bruni ha scritto: Il 28/08/2012 18:24, Francisco Vila ha scritto: -moz-border-radius-bottomleft: 7px; -webkit-border-bottom-left-radius: 7px; border-bottom-left-radius: 30px; } Why a different radius for -moz-border-radius-bottomleft and border-bottom-left-radius? I don't know: it was already there, I just moved it down. I'll prepare a patch so you can test it yourself. I have a patch already working but I'll follow the standard procedure. Here's the issue: http://code.google.com/p/lilypond/issues/detail?id=2784 I'll send the patch to Rietveld soon -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
dblatex and Error: cannot import name TexModule
I've stumbled again on this error while running make doc: http://lilypond-translations.3384276.n2.nabble.com/make-doc-error-cannot-import-name-TexModule-td7467314.html Here's the output: cd ./out-www dblatex suffix-lyxml.xml Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3.4-1) === Build suffix-lyxml.pdf A possible reason for transformation failure is invalid DocBook (as reported by xmllint) Error: cannot import name TexModule make[4]: *** [out-www/suffix-lyxml.pdf] Error 1 make[4]: Leaving directory `/home/fede/lilypond-git/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/fede/lilypond-git/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/fede/lilypond-git/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/fede/lilypond-git' make: *** [doc-stage-1] Error 2 The quick solution was removing dblatex. But it looks like now dblatex is a required dependency. I haven't tried to make a clean build (which maybe could solve the problem?), because I don't have a superfast laptop and the hot temperature may force my laptop to suspend. I hope you have some suggestions. Thanks -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dblatex and Error: cannot import name TexModule
Il 27/08/2012 13:51, Federico Bruni ha scritto: Error: cannot import name TexModule This error reminds me python errors.. I have no clue of what's happening but I tried to set the PYTHONPATH, as suggested here: http://lilypond.org/doc/v2.15/Documentation/contributor/problems export PYTHONPATH=/home/fede/lilypond-git/python/out As you can see, I'm building in the git root directory and not in build/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
metapost error
Hi, I'm trying to compile the current translation branch, in order to test 'make doc' before submitting my patch. But I'm getting the following error when I run make: # make[1]: Entering directory `/home/fede/lilypond-git/mf' /home/fede/lilypond-git/scripts/build/out/gen-emmentaler-scripts --dir=./out cd ./out \ touch mf2pt1.mem \ mpost -progname=mpost -ini /home/fede/lilypond-git/mf/mf2pt1.mp \\dump /home/fede/lilypond-git/scripts/build/out/gen-emmentaler-scripts --dir=./out /home/fede/lilypond-git/scripts/build/out/gen-emmentaler-scripts --dir=./out This is MetaPost, version 1.504 (kpathsea version 6.1.0) (/home/fede/lilypond-git/mf/mf2pt1.mp ! I can't open file `mfplain'. l.27 input mfplain ; Please type another input file name: ! Emergency stop. l.27 input mfplain ; Transcript written on mf2pt1.log. make[1]: *** [out/mf2pt1.mem] Error 3 make[1]: Leaving directory `/home/fede/lilypond-git/mf' make: *** [all] Error 2 ## Can you help me? I'll try a fresh build and see if the problem disappears. I'm compiling in the git root directory, not in build/, because otherwise I may get conflicts, see these discussions: http://lilypond-translations.3384276.n2.nabble.com/again-trouble-with-scripts-td6596436.html#a6599176 http://lilypond-translations.3384276.n2.nabble.com/compiling-error-quot-make-Entering-an-unknown-directory-quot-td7147600.html Thanks -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: metapost error
On 21/07/2012 12:46, Federico Bruni wrote: This is MetaPost, version 1.504 (kpathsea version 6.1.0) (/home/fede/lilypond-git/mf/mf2pt1.mp ! I can't open file `mfplain'. l.27 input mfplain sorry for the noise: texlive-metapost was not installed now it works My current internet connection is damned slow, so is my ability to search and try solutions. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 2-1: LilyPond is part of GNU
2012/7/16 Francisco Vila paconet@gmail.com: I will try. Just to be sure: googling for site:lilypond.org/doc/v2.15 open source which is what our search box produces, gives some other results. I'm assuming that is just the first result what bothers us, namely the German main entry web page. I'll fix the italian pages tonight. BTW, as we have one critical bug, no release will happen on Wednesday? Or it's up to David? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 2-1: LilyPond is part of GNU
2012/7/16 David Kastrup d...@gnu.org: Mark Knoop m...@opus11.net writes: At 11:55 on 16 Jul 2012, Mark Knoop wrote: This used to work... but has recently broken. See: https://bugzilla.gnome.org/show_bug.cgi?id=568209 or maybe: https://bugzilla.gnome.org/show_bug.cgi?id=660092 Neither, actually. Those are described to display broken images. But for me, Yelp just locks up and never delivers anything, churning away at 100% CPU power. It works quite fine for me (Debian testing, yelp 3.4.2-1). yelp starts at 100% of CPU in the first seconds, then it goes down to normal values. And I can see the images (from lilypond-doc package, version 2.14.2). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 2-1: LilyPond is part of GNU
2012/7/16 David Kastrup d...@gnu.org: It works quite fine for me (Debian testing, yelp 3.4.2-1). yelp starts at 100% of CPU in the first seconds, then it goes down to normal values. And I can see the images (from lilypond-doc package, version 2.14.2). Well, I have yelp 3.4.1 from Ubuntu 12.04, and it does not really seem to work. But it is great if it works and even displays images for you: in that case, I think we have reasonable grounds for trying to deliver an images-preferred packaging of info. info manuals are only in english? I can't see other languages in /usr/share/info both info and yelp show only the english version of the manual how can I see another language? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fw: GNU Source-highlight 3.1.7
Il 01/07/2012 08:06, Werner LEMBERG ha scritto: This might be of interest to some of you. Search for `Lilypond'. Werner See issue 1005: http://code.google.com/p/lilypond/issues/detail?id=1005 Still two steps to have highlight in documentation. -- Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR updates and translations
2012/6/20 Phil Holmes em...@philholmes.net: - Original Message - From: Francisco Vila paconet@gmail.com To: Phil Holmes em...@philholmes.net Good, I like it in principle, but how will be changes being tracked using SHA IDs? Currently, translations have a SHA ID which is that of the snippet it is a translation of. Any change to the original snippet is done in a commit whose SHA ID is used to generate a diff against the ID of the translation. This determines what the translators have to work on. That's a bit I'd deliberately glossed over since I didn't/don't fully understand it as yet. My idea would be that, using the new system, changed snippets would look exactly like changed documentation files. If I modify, say, /Documentation/notation/ancient.itely, how do the translators pick up that this has been changed? We copy in the translated file a committish which identifies our latest revision. We may use the committish of the latest commit (of the repository), as recommended in the CG. Or the committish of the latest commit of the original file, as me (and Francisco) do in order to easily see in the log of the file which version we translated/updated. As long as Documentation/snippets is tracked by Git, translators should be able to keep track of the changes in the snippets. Check check-translation.py to see if your changes will break something. When you have a patch, I can test a translation workflow and see if it works as expected. Anyway, your plan seems great. Moving away the translations from the Git-tracked snippets is the easiest solution, as we discussed months ago. Thanks! Federico ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: how to remove a file
I'm putting -devel in CC. Sorry for pushing, I'm in a hurry: I'd like to send the patches within tonight. Il 06/05/2012 15:53, Federico Bruni ha scritto: Hi, I have to remove the .texidoc file of a snippet which has been removed: diff --git a/Documentation/snippets/piano-template-with-centered-dynamics.ly b/Documentation/snippets/piano-template-with-centered-dynamics.ly deleted file mode 100644 index f56fc58..000 --- a/Documentation/snippets/piano-template-with-centered-dynamics.ly +++ /dev/null I wonder if I should use 'rm' or 'git rm'. I know that the difference is that rm keeps the file in the git index, while git rm removes it both from index and working copy. I think that I should use git rm, but I prefer asking as I have a poor understanding of git. Thanks, Federico I made a try: $ git rm Documentation/it/texidocs/piano-template-with-centered-dynamics.texidoc error: 'Documentation/it/texidocs/piano-template-with-centered-dynamics.texidoc' has local modifications (use --cached to keep the file, or -f to force removal) What's the recommended method? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Regarding LSR translation work
Il 25/04/2012 12:04, Graham Percival ha scritto: [..] I'm trying to learn Python and I'd like to contribute to some frog tasks requiring python (I've starred some frog issues in the tracker). Probably this is too much difficult for a newbie. Actually, I've got a good suggestion on how you could get started with python and all this stuff. Currently, makelsr.py adds different amounts of blank lines to some .ly files depending on whether you run it as a full import vs. when you run it locally. It would be nice if that didn't happen. [I've just started looking at this.] I think that blank lines are not the only problem. git log shows that most of the snippets' commits are related to the update of committish in translated texidoc strings. It's what we are talking about in this thread: in order to mark a snippet as updated, a translator updates the committish in the .texidoc file and run makelsr, which copies the new committish in the snippet. So the snippet gets a new (unnecessary?) commit, which makes all the other translations of that snippet out-of-date. It's a dog chasing its tail. These committishes copied inside the snippets are needed? IIUC, check-translation doesn't care about the committishes placed inside a file; it just check the latest git commit hash: line 38 of check-translation.py: vc_revision_parse = 'git log -1 --pretty=format:%%H %s' What happens if we remove all the %% Translation of GIT committish: strings in the snippets and change makelsr so that it will ignore the first line of .texidoc files when it copies them in the snippets? I don't believe that check-translation will stop working. The benefits would be: - no unuseful stuff in the commits of snippets -- cleaner git log - cleaner git log -- less output in check-translation Does it make sense? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Spanish pondings
2012/5/4 Phil Holmes m...@philholmes.net: Try http://lilypond.org/ Oh, I see: it works only if I click on English. Any other language doesn't show the tweets. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Dictionary for musical terms in Lilypond
Il 29/04/2012 12:55, Łukasz Czerwiński ha scritto: Hi, Recently my Polish speaking friend told me that it's a problem for him to look something in Lilypond documentation, because first of all he must translate the musical term he needs to English, which is quite a hard task, because there are several words that might express the same musical element. I came to an idea - what about creating a small dictionary of musical terms used in Lilypond and in Lilypond documentation? It might be just a separate page for each language with pairs: word - translated word. It exists already, it's called Music Glossary :) http://lilypond.org/doc/v2.15/Documentation/music-glossary/index.html New translations are easy because it's just one file for all languages, so you don't have to commit yourself to translate all the doc. The file is Documentation/music-glossary.tely ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
