Re: would like to participate
O.K. I will try to have something on this (An overview of all editing environments available) and post what I have to this list. -Ruhan -- Original Message -- Received: 12:50 AM EET, 02/13/2007 From: Bertalan Fodor <[EMAIL PROTECTED]> To: Graham Percival <[EMAIL PROTECTED]>Cc: Ruhan Ikeda <[EMAIL PROTECTED]>, lilypond-devel@gnu.org Subject: Re: would like to participate > > To understand what is going on I would like to start with the > > following task I > >> have seen at the web site: > >> > >> * * * > >> > >> In addition, we are still looking for help with the following website > >> tasks, > >> > >> * An overview of all editing environments available > >> > >> * * * > > > > Bertalan Fodor has offered to do this, although I'm not certain how > > far along he is -- he might be happy to let you do this instead. I've > > CC'd him on this email. > I still have nothing :-( > > Bert > ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: would like to participate
To understand what is going on I would like to start with the following task I have seen at the web site: * * * In addition, we are still looking for help with the following website tasks, * An overview of all editing environments available * * * Bertalan Fodor has offered to do this, although I'm not certain how far along he is -- he might be happy to let you do this instead. I've CC'd him on this email. I still have nothing :-( Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: would like to participate
Ruhan Ikeda wrote: I am a very devoted lilypond user and advocate. Being both a computer scientist and a musician and would like to participate in the lilypond development. Great, welcome! Using lilypond, I found out that instrument specific notation is not developed enough -- I was writing for violin trying to specify with bow movements. (I was using in 2.8, I think) What problem? I'm a string player, and I can't think of any string notation that LilyPond is lacking. To understand what is going on I would like to start with the following task I have seen at the web site: * * * In addition, we are still looking for help with the following website tasks, * An overview of all editing environments available * * * Bertalan Fodor has offered to do this, although I'm not certain how far along he is -- he might be happy to let you do this instead. I've CC'd him on this email. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Singing support for LilyPond
Milan Zamazal escreveu: >> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > HN> * can you use git-format-patch to send a patch? That way, I can > HN> integrate the patch easily. > > HN> * can you use recent relocation mechansism (see the @preamble@ > HN> at the top of .py scripts.) > > Done. > applied. Can you discuss with graham how to document this? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: German site update
John Mandereau wrote: You needn't send an email twice; if I don't reply quickly, just bug me with a private email. Ok, I know this now. There was a nitpick with the committish in about/engraving/input-format.html: it looks like you had made the patch with a revision different from the web/master upstream. Well, I still don't really know what is going on, and why just this file was making problems because I thought I made all changes for all the files and then commited them in one patch, so it is somehow strange to me that one file made a problem, especially because the contents of both files were identical to my eye. Another thing I was wondering about: I did now git pull and got then the conflict in the about/engraving/input-format.html, but I also got the message that sponsor/options.html both from french and spanish were untracked and wondered about this, because I thought the pull would automatically update whatever changes have been made to them. But well, I just commited them to my local tree, hope this is ok. Now I was thinking that I will probably also translate that part quite soon since you (translator teams) did this for french and spanish as well. Any improvements can then be added more quickly. My idea was to manage them the same way as the pictures in the site/switch/howto.html file that is to draw language-specific word on the on compile time. If you have Inkscape installed, you can go ahead on this, taking the pictures in switch/howto as an example. I will see if I understand that, and will then send my results. And altogether it might be worth some thinking if we should combine the benchmarking and shubert file, because the example now given in benchmarking gives kind of poor picture about the abilities of nowaday's lilypond. I guess this would imply updating the essay itself, which IMHO is up to Jan and Han-Wen. That is totally correct! What do you exactly mean? The files for the initial translation are Documentation/user/lilypond.tely -> Documentation/LANG/user/lilypond.tely Documentation/user/tutorial.itely -> Documentation/LANG/user/tutorial.itely Documentation/index.html.in -> Documentation/LANG/index.html.in Note that lilypond.tely shouldn't be fully translated, i.e. translating stuff in @iftex ... @end iftex blocs is useless as we don't generate translated docs with TeX for now. Yes, I was just some time ago quickly checking the directory and didn't immediately discover that. The generated files will be marked as non tracked by git, so they are not damageable. However, I recommend to copy the sources to a different directory before compiling them, especially if you plan to track both stable and master branches on the same local repository, so you can go on working on the sources while compiling. Yes, probably I will make a new directory. I suppose I should also "fork" it with git to make it easy to introduce the changes then back to the main localgit repository? Sounds promising, though I am afraid it will take me some time... The tutorial is 1400 lines long. ;-) Ah yes, and how is it: is there also a script like check-translation for the docs? Yes, there is. I'll have time to write a full README next week, when I have a vacation. Nice to hear. Greetings Till ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Singing support for LilyPond
Milan Zamazal escreveu: > I can't see any straight way to output the .xml file contents directly > from the test .ly files, but if the order in which the test files are > processed is deterministic, I could make a dummy test file that follows > all the test files, reads the generated .xml files and outputs their > contents with ly:progress. Would it be OK? And where's the right place > to remove the generated .xml files? in that case, the easiest way to show is to have the file output, and read it back in. See input/regression/backend-svg.ly -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Yet another correction needed in same file of web
Le dimanche 11 février 2007 à 21:52 +0100, Francisco Vila a écrit : > This refers once again to sponsor/options.html file Thanks, all the typos you mentioned are fixed. Cheers, -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: French version of @qq
Le samedi 10 février 2007 à 06:20 +0100, Werner LEMBERG a écrit :
> I see this in the git:
>
> @c to get decent French quotes in ``foo''
> @macro qq{TEXT}
> @html
> « \TEXT\ »
> @end html
> @end macro
>
> shouldn't this be rather
>
> @c to get decent French quotes in ``foo''
> @macro qq{TEXT}
> @html
> « \TEXT\ »
> @end html
> @end macro
>
> ?
Thanks Werner, this is fixed in Git.
I had already looked for the thin space HTML code, without success. I'd
like to put thin spaces automatically before `?' and `!' too, but this
is another story...
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: German site update
Hi Till, Le lundi 12 février 2007 à 09:34 +0200, Till Rettig a écrit : > > I forward this with a new subject, since you probably didn't see it > because it went to the older thread... No, I was too busy last week-end to switch on my computer. You needn't send an email twice; if I don't reply quickly, just bug me with a private email. > Hi John, > > I updated the German translation: that is the changes in > site/about/automated-engraving. I didn't though touch the site/sponsor > changes yet, because they have the remark of being still a draft. Then > I found a typo in the README and just corrected it. Here are the two > patches for those corrections. Please tell me if they do not apply > cleanly, I will then try to sort it out finally. There was a nitpick with the committish in about/engraving/input-format.html: it looks like you had made the patch with a revision different from the web/master upstream. > One second thought about the essay about automated engraving: There > are a lot of pictures with some kind of explanation like the one > explaning the mistakes in other editions. As I looked at it these > graphics are included into the files: > site/automated-engraving/problem-statement.html; benchmarking.html; > shubert.html; typography-features.html. > My idea was to manage them the same way as the pictures in the > site/switch/howto.html file that is to draw language-specific word on > the on compile time. If you have Inkscape installed, you can go ahead on this, taking the pictures in switch/howto as an example. > And altogether it might be worth some thinking if we should combine > the benchmarking and shubert file, because the example now given in > benchmarking gives kind of poor picture about the abilities of > nowaday's lilypond. I guess this would imply updating the essay itself, which IMHO is up to Jan and Han-Wen. > A third issue is then the generation of the big page of the essay: it > is not yet generated for German. But I guess you know this anyways. Yes, I do, but Jan and Han-Wen don't. I don't understand where the issue come from; you could file a bugreport to make them know this. > > See my related message on this list for the Git details. > > > Ok, I am not really ready with this, I mean: I didn't find all the > files that will be translated then in the end. What do you exactly mean? The files for the initial translation are Documentation/user/lilypond.tely -> Documentation/LANG/user/lilypond.tely Documentation/user/tutorial.itely -> Documentation/LANG/user/tutorial.itely Documentation/index.html.in -> Documentation/LANG/index.html.in Note that lilypond.tely shouldn't be fully translated, i.e. translating stuff in @iftex ... @end iftex blocs is useless as we don't generate translated docs with TeX for now. > But I hope you will give some more explanation further on. One > question already here, though: how does git react when I start > compiling lilypond on a git repository. Will all these files ignored > or should I always compy the contents of the souces directory so some > other place before I start the compilation? The generated files will be marked as non tracked by git, so they are not damageable. However, I recommend to copy the sources to a different directory before compiling them, especially if you plan to track both stable and master branches on the same local repository, so you can go on working on the sources while compiling. > > There is no technical support (makefiles and buildscripts) to translate > > the glossary, but if it is fully translated, this won't be hard to do. > > > > > I am not sure if I understand you here: I picked the file from > http://lists.gnu.org/archive/html/lilypond-user-fr/2006-12/msg3.html > > as you sent the link. It conforms quite well with the glossary, but my > version now contains only english-german equivalents, so it is more > straitforward for a translator. That is why I thought if it should be > included into the lilypond sources as a helper file for future > translators. Oh, then a good place for it is the (unofficial) wiki, on http://lilypondwiki.tuxfamily.org/ > > When you have updated the German web site, you'll be ready to start > > translating the tutorial. > > > Sounds promising, though I am afraid it will take me some time... The tutorial is 1400 lines long. > Ah yes, and how is it: is there also a script like check-translation > for the docs? Yes, there is. I'll have time to write a full README next week, when I have a vacation. Cheers, -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Singing support for LilyPond
Milan Zamazal escreveu: > Here's the modified patch, against a recent LilyPond git source tree: > It doesn't include tests, because I don't know what's a good way to > include them. They are .ly files to be processed with LilyPond, they > output .xml files and those are compared with corresponding samples, > using diff. The visual output is unimportant. * if they don't need external output, just stick them in input/regression/ , and print the XML with (ly:progress "~a" xml) our test-procedures will then monitor the xml output for changes. * can you use git-format-patch to send a patch? That way, I can integrate the patch easily. * can you use recent relocation mechansism (see the @preamble@ at the top of .py scripts.) thanks -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
would like to participate
Hi, I am a very devoted lilypond user and advocate. Being both a computer scientist and a musician and would like to participate in the lilypond development. Using lilypond, I found out that instrument specific notation is not developed enough -- I was writing for violin trying to specify with bow movements. (I was using in 2.8, I think) To understand what is going on I would like to start with the following task I have seen at the web site: * * * In addition, we are still looking for help with the following website tasks, * An overview of all editing environments available * * * -Ruhan ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: git-diff only certain files
Maximilian Albert wrote: Graham Percival schrieb: $ git-diff < lsr-unsafe.txt $ cat lsr-unsafe.txt | xargs git-diff might do what you want. Thanks, that's perfect! Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: git-diff only certain files
Graham Percival schrieb: > Can I get git-diff to only check certain files? I know I can specify > them on the command line, > > $ git-diff foo/bar baz/boozle > > but I'd like to simply point git-diff to a file and have it fill in the > details for me. ie something like > > $ git-diff < lsr-unsafe.txt $ cat lsr-unsafe.txt | xargs git-diff might do what you want. Cheers, Max ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
git-diff only certain files
Can I get git-diff to only check certain files? I know I can specify them on the command line, $ git-diff foo/bar baz/boozle but I'd like to simply point git-diff to a file and have it fill in the details for me. ie something like $ git-diff < lsr-unsafe.txt lsr-unsafe.txt contains: input/lsr/chords/chord-name-exceptions.ly input/lsr/expressive/breathing-sign.ly (I might be missing some basic bash knowledge) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
