Re: [Mutopia-discuss] Copy of the mutopia project in Belgium and translations
Hi Nicolas Unfortunately Mutopia is a staled project. The last commit in the repository was made three years ago and there are several pull requests waiting to be reviewed and merged: https://github.com/MutopiaProject/MutopiaProject The main problem is finding some people willing to do all the hard work required to keep the project alive: reviewing contributions on Github, maintain the infrastructure, etc. I'm against forking this project in any way. I think we should keep using Github (or similar public platforms) instead of privately owned servers. I'm sure that the old maintainers would be happy to give write permissions to persons who can show to have the skills and the will to take it over. A couple of years ago I would have liked to do something for Mutopia... now I don't have time at all. Your ideas look very interesting, but there are many many issues to be solved and IMO the translation is the last problem. Contributing to Mutopia in an "active" way (i.e. submitting pull requests on Github) requires English. Anyway, I do not recommend contributing to Mutopia until the project has been taken over by a new (or old) maintainer. I don't want to sound discouraging, but I think you should be aware of the current situation. Thanks Federico Il giorno lun 5 dic 2022 alle 19:09:26 +0100, Nicolas Pettiaux ha scritto: Dear all, I have been a long time promoter of free culture, free software and related topix (more than 25 years) and I am now at least beginning to read and play music myself, so I want to contribute more to Mutopia. I also happen to live with a professional pianist who is also the director of a Belgian, French speaking « académie de musique » (in La Hulpe) and I would very much like her 500 students and about 40 teachers to be able to use and contribute to Mutopia. This implies that the project be also in French. I also think that if the project was available natively in many languages, it would help with the participations of many different public. I therefore propose to help with the hosting of a copy of the mutopia project in Belgium if it is possible any help towards the translation to French, including translations of many pages. But for it to be efficent, I think that tools using the gettext suite should be put in place eg. po4a, as well as the use of modern communication such as a channel (if it does not exist yet) within element.io (that I have not seen advertised) like many other free software projects. I hope to read you soon, Best regards, Nicolas -- Nicolas Pettiaux, PhD in Physics - gsm +32 496 24 55 01 Communication sécurisée avec element.io : @npettiaux:matrix.org Professeur de mathématique - Cours-libres.org, l'éducation démocratisée. Educode asbl : informer, former & réfléchir aux défis du numérique - wiki.educode.be Lisez & partagez la connaissance libre grâce aux licences libres, surtout CC-BY-SA Boites mail éthiques, légales, sécurisées avec agendas, contacts, documents, photos, tâches ... Stocker, synchroniser, collaborer, partager, sécuriser ... avec nubo.coop ou ik.me ou mailfence.com. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Is the Mutopia Project still going?
+1 I'm currently involved in other lilypond stuff and can't contribute to Mutopia right now, but I will in the future. I think we need more reviewers of pull requests. It's not a fun task, but it's important and can't be left to only one/two persons. I guess that after some time an active and experienced reviewer may gain write access and help also with merging PRs. I think a checklist for PR's review would be very useful. Let's wait for ideas from Chris and Glen. Il giorno mer 19 feb 2020 alle 10:43, j.scholb...@posteo.de ha scritto: I am by far not one of the strongest contributors to Mutopia. But I would like to express that I value the project very much and that I will definitely contribute in the future. I would be very sad if Mutopia stalled or went down. And I am sure, many people feel alike. Chris, could you explain how the community could help to make run Mutopia smoothely again? Jonathan Scholbach Am 18.02.2020 16:15 schrieb Knute Snortum: That's great! I believe the main gatekeeper is Chris Sawer, and if I remember correctly the finalizing process is moderately complex. It would make sense to have another gatekeeper if Chris is too busy. --- Knute Snortum (via Gmail) On Mon, Feb 17, 2020 at 9:20 PM Mike Blackstock wrote: I'm interested. I have some stuff to contribute in the next little while and, additionally, I'd be willing to help out in other ways to keep the project going if it's in jeopardy. Quoting Knute Snortum : It looks like pull requests are starting to back up and nothing has been committed for months. I'm trying to decide if trying to contribute is worth it anymore. Is there still interest in this project? --- Knute Snortum (via Gmail) -- "Large streams from little fountains flow, Tall oaks from little acorns grow" - D. Everett Website: https://blackstock.media [1] ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss [2] Links: -- [1] https://blackstock.media [2] http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] checking Mutopia headers with Mutopia.java
Hi folks In this wiki page: https://github.com/MutopiaProject/MutopiaProject/wiki/Updating-Lilypond-files-for-the-Mutopia-Project#mutopia-headers I read: ``` Even if it compiles cleanly and looks like the original, you should still check the Mutopia header elements before you commit your changes. If you have a java run-time environment on your machine you can check the header consistency with this command, $ java Mutopia -c score.ly The details of getting a java run-time environment, setup, etc., are beyond the scope of this article. If you don't have java, you will simply have to do this check visually. ``` I see that the script is now located in the MutopiaWeb repository: https://github.com/MutopiaProject/MutopiaWeb/blob/master/mpcore/Mutopia/src/main/java/Mutopia.java I haven't tested it yet, but I see there are some instructions here: https://github.com/MutopiaProject/MutopiaWeb/tree/master/mpcore Perhaps Updating files wiki page should link there? ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] 403 Forbidden for any file on Mutopia website
Hi all Yesterday I noted that I cannot get access to any file on Mutopia website. Main pages in the web root as well as cgibin/ pages are accessible, but it seems that any other page within ftp/ is not. Example: Forbidden You don't have permission to access /ftp/AlkanCV/O31/alkan-op31-8/alkan-op31-8.mid on this server. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] frescobaldi manuscript viewer (still in development)
Hi all I think that you might be interested to checkout the manuscript-viewer branch of Frescobaldi. It's still in early stages of development but already working. See this screenshot: http://postimg.org/image/gs4lgw80v/ More information: https://github.com/wbsoft/frescobaldi/issues/112 https://github.com/wbsoft/frescobaldi/issues/704 Cheers Federico ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] reviewing pull requests in github
Il giorno ven 5 dic 2014 alle 18:36, Federico Bruni f...@inventati.org ha scritto: Perhaps it's better using 'git format-patch' in case the contributor approves it and what to apply to his branch? I don't know if the patch generated with the command above can be applied with 'git am'. sorry, typo: ... and want to apply to... ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] reviewing pull requests in github
Il giorno mer 3 dic 2014 alle 4:24, Javier Ruiz-Alma jav...@ruiz-alma.com ha scritto: Having a link to this guide would've made things easier for the few times I've copy/pasted code to compile some else's pull-requests. This doesn't happen often, though, so maybe you can create a new wiki page for advanced topics. Ok, I'll add it in the afternoon. Is it possible to also submit changes to someone else's open pull-request via github? If so, add a link to this too. Speaking for myself: I'd be lost on how to process a change request to one of my open PR's thru github. Changing and updating your own pull request is very easy. You just have to work on the same branch used for that specific pull request (that's why using a different branch from master is highly recommended in github, unless you know that you are going to merge it immediately). You add a commit to that branch and push it to your remote/branch; the pull request will be updated automatically. I don't think it's possible to submit changes to someone else's open pull request. You can upload the .patch file of your changes in the comments of the pull request, if you want the author of the PR to see your ideas. Or you can copy his branch in your repository and send a new PR, if you want to take up his work. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] reviewing pull requests in github
Il giorno mer 3 dic 2014 alle 10:23, Federico Bruni f...@inventati.org ha scritto: I don't think it's possible to submit changes to someone else's open pull request. You can upload the .patch file of your changes in the comments of the pull request, if you want the author of the PR to see your ideas. Or you can copy his branch in your repository and send a new PR, if you want to take up his work. And of course the full commit history, including commits of the first author, is present. You can see an example of a patch taken over by a new developer here: https://github.com/tomchristie/mkdocs/pull/222/commits He created a new pull request.. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] reviewing pull requests in github
Hi all I'm reading this guide: https://help.github.com/articles/checking-out-pull-requests-locally/ I see that I can easily checkout the branch submitted through a pull request with this command: git fetch origin pull/ID/head:BRANCHNAME git checkout BRANCHNAME Now, if the author of the pull request add one or more commits, what's the best way to update it to the last commit? If I repeat the fetch above I get this error: fatal: Refusing to fetch into current branch refs/heads/search of non-bare repository The simple (stupid) solution I found is deleting the branch so I can repeat the two commands above without any problem. But I'm sure that there's something better. Mmmmh, I think I found it. If I checkout master again and run the fetch again it works. I guess that I'm missing what the fetch does. Anyway, do you think it's worth adding a small page in the wiki about reviewing patches? Cheers Federico PS For Glen and Javier: what about another round of updates? Or some focus to close the Phase 3 milestone? I got a bit stuck on writing a piece from scratch. But during Christmas I might have some time to get some things done. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] First Typetting Request: Checkpoint Summary
Hi Javier I've realized that Paganini Caprices are too complex, can you please take me off? I've started working on this instead: https://github.com/chrissawer/The-Mutopia-Project/issues/363 Sorry, I should have committed to a piece when I have time to work on it. Now I have some time.. Anyone willing to work on the Caprices, please go ahead. BTW, caprice 2 is in mutopia, update this page: https://github.com/chrissawer/The-Mutopia-Project/issues/362 Il giorno mer 10 set 2014 alle 9:27, Javier Ruiz-Alma jav...@ruiz-alma.com ha scritto: First off, our thanks to those that volunteered their time and effort for our first typesetting request, some of which are contributing to the Mutopia Project for the first time: Knute Snortum, Steve Taylor, Abel Cheung, Federico Bruni, Joram Berger, and Glen Larsen. If you missed the background and goals of this request, please check our initial announcement. We posted an ambitious list of 12 popular works, including several collections of pieces for piano, violin, and voice; in all, 300+ pages of scanned music to choose from. Since our request back in April, more than 60% of the works have been claimed. By our 4-month checkpoint of August 15th, volunteers had submitted 22 new pieces, adding 83 pages of music to Mutopia, at a pace of 770 lines of LilyPond code per week. Taking into account completed works only, the corresponding scans of added pieces get 300 downloads per day from the IMSLP website. Mutopia doesn’t currently track download traffic, but to get some early reference, we posted one of the typesets to IMSLP. The LilyPond version got 300+ downloads in it’s first month. These are great, encouraging results, and I hope you join me in congratulating the volunteers that made it happen. In the months ahead, we’ll continue tallying completion of already-assigned works, and welcome others that want to contribute. Armed with this baseline of stats, we plan further collaboration with IMSLP to fine-tune and automate the effort that was done manually to select future “wanted” music lists. Javier Ruiz-Alma ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] OK to use devel version of LilyPond?
Il giorno sab 19 lug 2014 alle 4:17, Abel Cheung abelche...@gmail.com ha scritto: On Sun, Jul 13, 2014 at 10:48 PM, Chris Sawer ch...@mutopiaproject.org wrote: The \version in the .ly file should match the version of LilyPond that you want us to compile with. Thanks, then there's only one missing puzzle left. Say if I have a piece with (hypothetically) \version 2.19.3, but the machine rendering the scores have 2.19.7, then would it be rendered with the nearest version (2.19.7), or 2.19.3 will be installed on that machine to generate score? Interesting.. I thought that Mutopia used only the latest stable as most recent version. How Mutopia website is built (roughly) would be a nice add in the github wiki. BTW, website is currently down: http://www.downforeveryoneorjustme.com/mutopiaproject.org ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Renaming file names of movements
I would not hard-code the numbers in the names. If you have a file for the whole suite, which includes all the movements in the right order, you have already defined the order. Cleaner and more flexible, in my opinion. On 14 maggio 2014 04:46:22 CEST, Knute Snortum ksnor...@gmail.com wrote: I brought up the problem here of how to present a set of movements that can be individually downloaded and yet allow the user to play the suite as a whole in the correct order. The easiest solution was deemed the best, that is, rename the movements with numbers as the beginning of their name so that the order is evident. To that effect, I'd like to propose the renaming of these files. First, from The-Mutopia-Project\ftp\BachJS\BWV814\french-suite-3\french-suite-3-lys 01-bach-french-suite-3-allemande.ly 02-bach-french-suite-3-courante.ly 03-bach-french-suite-3-sarabande.ly 04-bach-french-suite-3-menuet.ly 05-bach-french-suite-3-trio.ly 06-bach-french-suite-3-gavotte.ly 07-bach-french-suite-3-gigue.ly Second, from The-Mutopia-Project\ftp\BachJS\BWV817\french-suite-6\french-suite-6-lys 01-bach-french-suite-6-allemande.ly 02-bach-french-suite-6-courante.ly 03-bach-french-suite-6-sarabande.ly 04-bach-french-suite-6-gavotte.ly 05-bach-french-suite-6-polonaise.ly 06-bach-french-suite-6-bourree.ly 07-bach-french-suite-6-menuet.ly 08-bach-french-suite-6-gigue.ly Knute Snortum (via Gmail) ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss -- Federico___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Renaming file names of movements
Il 14.05.2014 14:43 Knute Snortum ha scritto:
This is how I propose to have the movements and the suite:
https://drive.google.com/folderview?id=0B_aEseOV9KTXamtCeUhXenF2eWcusp=sharing
[21]
A couple of comments:
- your -all.ly file, which includes all the movements, doesn't print
the titles of each movement.
You may use print-all-headers, but I think that it's better using
\bookpart
- personally I don't like splitting each piece in two files (one for the
music definitions and one for the \score block), unless it's really
necessary
I've changed the suite file and the first two pieces.
This is how I would do it, but of course others may have different
opinions.\version 2.18.2
\language english
\header {
title= French Suite no. 6 in E major
composer = J. S. Bach (1685-1750)
opus = BWV 817
style= Baroque
license = Creative Commons Attribution-ShareAlike 4.0
enteredby= Knute Snortum
lastupdated = 2014/Apr/28
date = 1722
source = Bach-Gesellschaft, 1863
mutopiatitle = French Suite no. 6 in E major
mutopiacomposer= BachJS
mutopiaopus= BWV 817
mutopiainstrument = Harpsichord, Piano
maintainer = Knute Snortum
maintainerEmail= knute (at) snortum (dot) net
maintainerWeb = http://www.musicwithknute.com/;
footer = Mutopia-2014/04/27-1935
copyright = \markup { \override #'(baseline-skip . 0 ) \right-column { \sans
\bold \with-url #http://www.MutopiaProject.org; { \abs-fontsize #9 Mutopia
\concat { \abs-fontsize #12 \with-color #white \char ##x01C0 \abs-fontsize #9
Project } } } \override #'(baseline-skip . 0 ) \center-column {
\abs-fontsize #12 \with-color #grey \bold { \char ##x01C0 \char ##x01C0 } }
\override #'(baseline-skip . 0 ) \column { \abs-fontsize #8 \sans \concat {
Typeset using \with-url #http://www.lilypond.org; LilyPond \char ##x00A9
2014 by \maintainer \char ##x2014 \footer } \concat { \concat {
\abs-fontsize #8 \sans{ \with-url
#http://creativecommons.org/licenses/by-sa/4.0/; Creative Commons Attribution
ShareAlike 4.0 International License \char ##x2014 free to distribute,
modify, and perform } } \abs-fontsize #13 \with-color #white \char ##x01C0 } }
}
tagline = ##f
}
\include bach-french-suite-6-allemande.ly
\include bach-french-suite-6-courante.ly
%\include bach-french-suite-6-sarabande.ily
%\include bach-french-suite-6-gavotte.ily
%\include bach-french-suite-6-polonaise.ily
%\include bach-french-suite-6-bourree.ily
%\include bach-french-suite-6-menuet.ily
%\include bach-french-suite-6-gigue.ily
%%% Include file for allemande.ly and all.ly
\version 2.18.2
% Repeat 1
alleHighVoiceOne = \relative c'' {
\partial 16 b16
| gs16 ( a b e ) e, e' fs, e' gs, ( a b e ) e, e' fs, e'
| gs,16 ( e' fs gs ) a, ( gs' fs e ) ds ( e fs b ) b, b' d, b'
| cs,16 ds e a a, a' cs, a' b, a' e gs a, b cs fs
| gs,16 e' b e fs, gs a ds e4 ~ e16 gs ds fs
| e16 ds cs e gs cs, e b as gs fs as cs fs, e' fs,
| ds'16 cs b ds fs b, ds a gs fs e fs b e, ds' e,
| cs'16 ds e gs fs e ds cs b' as gs fs e ds e cs
\barNumberCheck #8
| ds8. \prall e16 cs8. \mordent b16 b8 fs' ds fs16 as,
| b8 ds16 gs, a8 b16 fs gs8 e'4 cs8
| as8 fs'4 ds8 b gs' ~ gs16 as b gs
| e16 ds e8 ~ e16 gs fs e ds cs b gs' b,8 as16. b32
| b16 cs ds fs b fs ds fs b,4. r16 \break % partial, -1/16
}
alleLowVoiceOne = \relative c {
\partial 16 r16
| r8 e gs b e e, gs b
| e ds cs a b a gs e
| a8 gs fs e ds e cs a
| b8 gs a b r16 e, gs b e8 bs
| cs8 gs' e cs fs fs, as cs
| b8 fs' ds b e e, gs b
| e8 cs ds e fs gs as fs
\barNumberCheck #8
| b8 e, fs fs, b16 cs ds fs b fs b e,
| ds16 e fs b b, b' ds, b' e, fs gs cs cs, cs' e, cs'
| fs,16 gs as ds ds, ds' fs, ds' gs, as b e e, e' gs, e'
| as,16 b cs fs fs, fs' as, fs' b,8 gs e fs
| b2 ~ b16 fs ds fs b,8. \break % partial, -1/16
}
% Repeat two
alleHighVoiceTwo = \relative c'' {
fs16 % partial bar
| ds16 e fs b b, b'cs, b' ds, e fs b b, b' cs, b'
| ds,16 fs gs a b, a' gs fs gs fs e gs b, gs' gs, gs'
| as,16 bs cs fs ds fs bs, fs' e ds cs e gs, e' e, e'
\barNumberCheck #16
| fs,16 gs a d b d gs, d' cs a b cs fs cs a' cs,
| d16 e fs a d, fs a, d fs, e d fs a fs d' a
| ds16 e fs a ds, fs bs, ds fs, e ds fs bs fs ds' bs
| gs'16 fs e gs cs, gs' a, gs' fs e ds fs bs, fs' gs, fs'
| e16 ds cs e gs, cs ds bs cs8 gs'16 e cs8 e16 gs,
| a8 cs16 a fs8 a16 cs, ds8 fs'16 ds b8 ds16 fs,
| gs8 b16 gs e8 gs16 b, cs8 a'4 fs8
| ds8 b'4 gs8 e cs' ~ cs16 ds e cs
\barNumberCheck #24
| a gs a8 ~ a16 cs b a gs fs e cs' fs,8. \trill e16
| e16 ( fs gs a ) b e, d' e, cs' b a cs e a, cs gs
| fs16 ( gs as b ) cs fs, e' fs, ds' cs b ds fs ds a' fs
| ds16 e fs a gs fs e ds b' a gs fs e ds cs b
| e16 b cs a gs e' fs, ds' e4. r16 % partial, -1/16
}
alleLowVoiceTwo = \relative c {
r16 % partial bar
| r8 b ds fs b b, ds fs
| b8 fs ds b e e, r e'' ~
| e8
Re: [Mutopia-discuss] Renaming file names of movements
Il 14.05.2014 17:02 Knute Snortum ha scritto: I would put all the changes into one pull request (I wouldn't even use a branch) but Glen has said (and this document [1] implies) that there should be one file per branch per pull request. I admit that this seems strange but I'm trying to do things the Mutopia way. [1] https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB [1] I don't know where in the link above you read that there should be one file per branch per pull request. I would say that every branch is always connected to the same pull request (see the Notes at the bottom of the wiki page above). Which means that you must create a new branch when you want to submit a new pull request (a new set of work). You can change as many files as you need, as long as they belong to the same kind of work you are doing in your topic branch. If the topic branch is updating the tagline of all the Mutopia pieces, then you'll work on a lot of files in different directories. If you are updating a piece, you'll probably have just one or more files in a single directory. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] clean pull requests?
Il giorno mar 13 mag 2014 alle 23:09, Javier Ruiz-Alma jav...@ruiz-alma.com ha scritto: Hi Federico, Glen graciously added instructions on how to setup your github fork, and basic workflow involved in maintaining existing pieces in Mutopia using github. He also a started a document to highlight LilyPond coding practices for new submissions to Mutopia, which enhance the maintainability moving forward. Today, I drafted a new doc covering new submissions: https://github.com/chrissawer/The-Mutopia-Project/wiki/Guidelines-for-new-score-submissions-using-github Github has proven to be a great environment for code collaboration, and we welcome contributors using pull-requests. Javier Ruiz-Alma Thanks Javier, this new page was the missing bit! I've updated the main page of the wiki and added an index of the articles (even if there's an automatic list under Pages on the right). It seems that wiki links are better: - [[|]] https://help.github.com/articles/adding-links-to-wikis https://github.com/chrissawer/The-Mutopia-Project/wiki ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] Update to 2.16/2.18: next step?
Glen, I see that most of pull requests are cleared. Let's start a new session of updates? -- Federico___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] spurious git diff
Hi all I think that a good practice to ancourage and ease the review of updates is splitting a pull request in at least two commits: one for the initial convert-ly and the second for the manual changes. I think it may be added to the wiki page: https://github.com/chrissawer/The-Mutopia-Project/wiki/Updating-Lilypond-files-for-the-Mutopia-Project I have a question: do you know why git diff after convert-ly doesn't show a proper diff line by line? I've already read a complain about this from Keith on lilypond-user, pointing to this commit: https://github.com/chrissawer/The-Mutopia-Project/commit/81a588f5d16a3bcb4110bd1e8197dbdc5a08137e If I add the file to a new git repository, the 'git diff' of the updated file is correct. What's wrong with the main repository? It's not a big deal, it means only that the actual changes made by convert-ly won't be visible. But still I want to understand why it happens. Thanks Federico ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
[Mutopia-discuss] file encoding should be UTF-8, right?
$ file -i ftp/ScriabinA/O59/prelude/prelude.ly ftp/ScriabinA/O59/prelude/prelude.ly: text/plain; charset=us-ascii Can I run iconv on it, right? This again will break the diff (see previous thread), but it's needed. One more thing to add to the wiki? If you give me the ok, I can edit the page myself. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] file encoding should be UTF-8, right?
Il sab, feb 22, 2014 at 6:38 , Federico Bruni f...@inventati.org ha scritto: $ file -i ftp/ScriabinA/O59/prelude/prelude.ly ftp/ScriabinA/O59/prelude/prelude.ly: text/plain; charset=us-ascii Can I run iconv on it, right? This again will break the diff (see previous thread), but it's needed. One more thing to add to the wiki? If you give me the ok, I can edit the page myself. I can convert with Gedit. However, what's wrong with the following commands? $ iconv -f US-ASCII -t UTF-8 ftp/ScriabinA/O59/prelude/prelude.ly ftp/ScriabinA/O59/prelude/prelude.ly $ file -i ftp/ScriabinA/O59/prelude/prelude.lyftp/ScriabinA/O59/prelude/prelude.ly: inode/x-empty; charset=binary I've tried also recode, but it doesn't work: $ recode -v UTF-8 ftp/ScriabinA/O59/prelude/prelude.ly Request: UTF-8..:libiconv:..CHAR Shrunk to: UTF-8..CHAR Recoding ftp/ScriabinA/O59/prelude/prelude.ly... done $ file -bi ftp/ScriabinA/O59/prelude/prelude.ly text/plain; charset=us-ascii ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] file encoding should be UTF-8, right?
Il sab, feb 22, 2014 at 7:12 , Noeck noeck.marb...@gmx.de ha scritto:
Hi,
I might be wrong, but the file has no property like utf8 orascii,
it
is just encoded as such. Ascii is a subset of utf8. If there are only
ascii charachters in the file, there is no reason for the file command
to say anything else but us-ascii. There is no difference between
ascii and utf8, in case there are only ascii characters in the file.
Thanks, I realized it afterwards by trial and error.
I was misled by this diff:
$ git diff
diff --git a/ftp/ScriabinA/O59/prelude/prelude.ly
b/ftp/ScriabinA/O59/prelude/prelude.ly
index ccb31de..b66a87f 100644
--- a/ftp/ScriabinA/O59/prelude/prelude.ly
+++ b/ftp/ScriabinA/O59/prelude/prelude.ly
@@ -38,7 +38,7 @@ upperOne = \relative c' {
a e' a8-- gis' gis'4- cis, bis'4.-- |
a a'4-- gis' gis'8- cis, bis'4.-- |
a a'4-- gis' gis'8- a, a'4-- gis' gis'8- |
- r r gis bis gis'-\p\^\markup{\italic avec d\\'efi} gis bis
gis'- gis bis gis'- gis bis gis'-\! |
+ r r gis bis gis'-\p\^\markup{\italic avec dC3A9fi} gis bis
gis'- gis bis gis'- gis bis gis'-\! |
\tieUp
gis'-\f e8.- dis16- gis4.- ~ |
gis4 e8- dis- bis- a- |
@@ -72,7 +72,7 @@ upperOne = \relative c' {
ees ees'4-- d' d'8- ees, ees'4-- d' d'8- |
r r d fis d'-\p\ d fis d'- d fis d'- d fis d'-\! |
\tieUp
- d d'-\f^\markup{\italic avec d\\'efi} bes bes'-- a a'-- d
d'4.- ~ |
+ d d'-\f^\markup{\italic avec dC3A9fi} bes bes'-- a a'--
d d'4.- ~ |
d d'4 bes bes'8- a a'- fis fis'- ees ees'- |
\phrasingSlurDown
fis bes ees fis4.- bes,16\( ees fis bes d ees |
I see now that it is because of LESSCHARSET env. This fixes it:
export LESSCHARSET=utf-8
___
Mutopia-discuss mailing list
Mutopia-discuss@mutopiaproject.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] 3 requests to improve the project communication (and hopefully get new contributors)
Hi Chris thanks for your prompt reply Il dom, gen 5, 2014 at 9:26 , Chris Sawer ch...@mutopiaproject.org ha scritto: [...] 3. Licenses - http://www.mutopiaproject.org/legal.html Can you please add on that page the reason why licenses are limited to public domain, CC By and CC By-Sa? Cc By-Sa-Nc is not listed because it's not approved as free cultural license? http://creativecommons.org/freeworks Yes, I will go through all the new CC licenses and update that page with some more information following your suggestion. Ok, thanks. Please consider also the Free Art License, as reported by this lilypond user: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00207.html Regards, and best wishes to all for 2014. I wish you and Mutopia all the best for 2014. ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] Help with Lilypond
Hi Huw I'm CCing lilypond-user because you'll probably get more help from there 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Yes, you can: search \include in the documentation. \include is the same as pasting the content of the file in the point you use it. You should have a good understanding of file structure. If you can provide a minimal example or a link to the files you've written, we'll be able to help you. Anyway, this is the relevant part of the documentation: http://lilypond.org/doc/v2.17/Documentation/notation/input-structure Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Maybe someone from lilypond-user lives there... 2013/4/21 Huw Richards a...@eng.cam.ac.uk Dear All, I have been using Lilypond to transcribe various pieces of music for Mutopia for 2 or 3 years now, but have not yet uploaded anything to Mutopia. I am very happy with typing in the notes, clefs, time signatures etc. but I struggle to know how to produce a complete assembled document with page numbers, cover, text etc. As an example of what I mean, I have produced a set of six viola/ violin duets by Benjamin Blake. I have them as multiple files (- viola file, violin file, score file) for each duet. I would like to be able to combine them elegantly into a book. I think I may have started in the wrong way and perhaps should have understood more about possible file structures before I started. I do not understand how, or if, Lilypond can combine files together to produce a single output. Is there any way / anywhere I can get face-to-face training or help with this in particular and with Lilypond in general? I live in Cambridge, UK. Huw Richards - a...@eng.cam.ac.uk ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
Re: [Mutopia-discuss] review of GalileiV/saltarello
Il 15/12/2012 11:20, Felix Janda ha scritto: Sorry, you should leave the composer field as it was and only change the mutopiacomposer field. (The composer field is what will be seen on the pdf whereas mutopiacomposer is for example used to list pieces by composer on the mutopia page.) Sure, thanks for catching this! ___ Mutopia-discuss mailing list Mutopia-discuss@mutopiaproject.org http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
