replace remaining occurrences of www.lilypond.org with lilypond.org (issue 313350043 by fedel...@gmail.com)
Reviewers: ,
Message:
I've created a new rietveld issue, since I can't remember from which
machine I've uploaded the first patch set.
This applies to current master.
Description:
replace remaining occurrences of www.lilypond.org with lilypond.org
Some occurrences of www.lilypond.org were overlooked in previous
patch for issue 5014. Command used:
git grep -l "@uref{http://www.lilypond.org/"; | xargs sed -i
"s|@uref{http://www.lilypond.org/|@uref{http://lilypond.org/|g"
Please review this at https://codereview.appspot.com/313350043/
Affected files (+12, -12 lines):
M Documentation/contributor/regressions.itexi
M Documentation/es/web/news.itexi
M Documentation/web/news.itexi
M input/regression/musicxml/00-Introduction.itexi
Index: Documentation/contributor/regressions.itexi
diff --git a/Documentation/contributor/regressions.itexi
b/Documentation/contributor/regressions.itexi
index
365582e87f7a8beef00a6e437f67d7b005fba98a..9b13c25d53107f5696a528af18b04347f98a2639
100644
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -506,7 +506,7 @@ code has been exercised by the tests.
For tracking memory usage as part of this test, you will need
GUILE CVS; especially the following patch:
@smallexample
-@uref{http://www.lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch}.
+@uref{http://lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch}.
@end smallexample
@subheading Code coverage
Index: Documentation/es/web/news.itexi
diff --git a/Documentation/es/web/news.itexi
b/Documentation/es/web/news.itexi
index
61d5b8d8913967d42c80aa2bd89f860927a662e2..4a9ba9de9fa051bf4b6bcb8880fe8a105ad17480
100644
--- a/Documentation/es/web/news.itexi
+++ b/Documentation/es/web/news.itexi
@@ -613,10 +613,10 @@ funcionalidades es coherente, que la documentación es
correcta y
que no se ha pasado por alto ningún problema importante. Para la
actualización de la sintaxis de sus archivos de entrada a la
última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
Updating files with convert-ly}. Le rogamos que pruebe esta
versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
de fallo}.
@newsEnd
@@ -631,10 +631,10 @@ el conjunto de funcionalidades es coherente, que la
documentación
es correcta y que no se ha pasado por alto ningún problema
importante. Para la actualización de la sintaxis de sus archivos
de entrada a la última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
Updating files with convert-ly}. Le rogamos que pruebe esta
versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
de fallo}.
@newsEnd
@@ -649,10 +649,10 @@ el conjunto de funcionalidades es coherente, que la
documentación
es correcta y que no se ha pasado por alto ningún problema
importante. Para la actualización de la sintaxis de sus archivos
de entrada a la última versión, consulte
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
+@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
Updating files with convert-ly}. Le rogamos que pruebe esta
versión y nos informe de cualquier problema, véase
-@uref{http://www.lilypond.org/website/bug-reports.html, Informes
+@uref{http://lilypond.org/website/bug-reports.html, Informes
de fallo}.
Index: Documentation/web/news.itexi
diff --git a/Documentation/web/news.itexi b/Documentation/web/news.itexi
index
d5d907d0073c3fd719cf6b14e9093b98071ac3c1..20a91fa78020e3993e18c2b13e1ad09b2606d6ce
100644
--- a/Documentation/web/news.itexi
+++ b/Documentation/web/news.itexi
@@ -715,9 +715,9 @@ a potential final beta release for the upcoming stable
release@tie{}2.18. The
developers believe this to be feature-complete, the
documentation to be accurate, and no important issues to be
overlooked. For upgrading the syntax of your input files to the
-latest version, see
@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
Updating files with convert-ly}.
+latest version, see
@uref{http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly,
Updating files with convert-ly}.
Please test this release and report back any problems, see
-@uref{http://www.lilypond.org/website/bug-reports.html, Bug reports}.
+@uref{http://lilypond.org/website/bug-reports.html, Bug reports}.
@newsEnd
@@ -729,9 +7
Re: ly2musicxml / possible sponsoring
Hello Christoph, On 01/16/2017 04:24 AM, Christoph Hagemann wrote: I'm a music professional in Germany. A few years ago I set a large- scale orchestral project in lilypond (score around 200 pages). Now the publisher wants MusicXML data. I understand there was some work done on an export function during last year's GSoC. Is there any chance for completion? If it helps, I'm willing to put an resonable amount of money into this and fund the completion of this feature. I'd probably be interested in working on this, especially if you are willing and able to sponsor the work to some extent. (Maybe others would also be willing to contribute?) This was a GSOC 2015 project, and I have a copy of the code. Looking at it again, it seems that it should at least be possible to get it to where it could be used. As is, it should cover some of the needs you listed[0], and perhaps more could be added. (Now that guile2 support has reached a somewhat-usable state, that will help since guile2 is required for the musicxml conversion.) We should discuss details and expectations, as I wouldn't want to over-promise and under-deliver. I'm curious about your time frame. Are there deadlines? Kind regards, -Paul Morris [0] The README file says: "Currently limited to single-voice SequentialMusic contexts of notes, chords, articulations (not all are supported, such as early-music or instrument-specific examples), key signatures, time signatures, and clefs" ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
New Dutch PO file for 'lilypond' (version 2.19.54)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Dutch team of translators. The file is available at: http://translationproject.org/latest/lilypond/nl.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/lilypond.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev 5.0 released
On 01/03/2017 03:42 PM, Federico Bruni wrote: Il giorno ven 23 dic 2016 alle 17:26, Paul ha scritto: Hi Federico, I double-checked and I do/did have the box checked to enable PAE. I tried un-checking it and Virtual Box complained about it right away upon starting up the VM. So when I get a chance I may try James' approach of using a newer version of Virtual Box, or else your approach with libvirt. (No time at the moment though...) Today I've installed Virtual Box 5.1.10 on Fedora from rpmfusion. When I started the machine the first time I got an error about the kernel and I followed VB advice to run two commands as root user: akmods systemctl restart systemd-modules-load.service Then it worked fine. But Ubuntu doesn't use systemd, right? Hi all, Following James' instructions I've upgraded to VirtualBox 5.1.13 r112787 (Qt5.6.1) And I tried creating and installing a new VM with LilyDev5 but I get the same problem. (Black screen after the 'loading initial ramdisk...') I also tried the commands Federico mentioned, but they did not help. (akmods seems to be a fedora thing, not found on ubuntu, and the other command worked, but did not change anything.) I tried opening in 'recovery mode' and got this far on the screen before it froze up: rtc_cmos rtc_cmos: setting system clock to [...] UTC Freeing unused kernel memory: 740K Write protecting the kernel text: 5744k Write protecting the kernel read-only data: 1704k Loading, please wait... In the Virtualbox log files it always gets to the same place shown below. I'm at a loss on what to try next. Any ideas? Thanks in advance for any pointers or suggestions. -Paul [omitting earlier parts...] 00:00:23.677316 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x379fd000 - u32TscScale=0xcd47be37 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x0 uVirtNanoTS=0x0 00:00:23.677344 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored 00:00:23.922374 GIM: KVM: Enabled wall-clock struct. at 0x1a8c1108 - u32Sec=1484682583 u32Nano=222082000 uVersion=2 00:00:24.056792 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0) 00:00:24.242835 PATM: Disabling IDT 80 patch handler da599460 00:00:24.243921 PATM: Disabling IDT fd patch handler da599bb8 00:00:24.244665 PATM: Disabling IDT fc patch handler da599c30 00:00:24.245348 PATM: Disabling IDT fb patch handler da599ca8 00:00:24.246134 PATM: Disabling IDT 20 patch handler da599d20 00:00:24.246496 PATM: Disabling IDT f8 patch handler da599d58 00:00:24.246850 PATM: Disabling IDT f7 patch handler da599d94 00:00:24.247536 PATM: Disabling IDT f2 patch handler da599e0c 00:00:24.247907 PATM: Disabling IDT f1 patch handler da599e48 00:00:24.248251 PATM: Disabling IDT ef patch handler da599e84 00:00:24.248799 PATM: Disabling IDT fe patch handler da599efc 00:00:24.249499 PATM: Disabling IDT f0 patch handler da599f74 00:00:24.250016 PATM: Disabling IDT f6 patch handler da599fec 00:00:24.250329 PATM: Disabling IDT fa patch handler da59a064 00:00:24.250424 PATM: Disabling IDT f9 patch handler da59a0dc 00:00:24.250526 PATM: Disabling IDT f4 patch handler da59a154 00:00:24.250625 PATM: Disabling IDT 10 patch handler da59a1cc 00:00:24.250678 PATM: Disabling IDT 13 patch handler da59a1dc 00:00:24.250724 PATM: Disabling IDT 7 patch handler da59a1ec 00:00:24.250771 PATM: Disabling IDT 4 patch handler da59a200 00:00:24.250815 PATM: Disabling IDT 5 patch handler da59a210 00:00:24.250861 PATM: Disabling IDT 6 patch handler da59a220 00:00:24.250904 PATM: Disabling IDT 9 patch handler da59a230 00:00:24.250944 PATM: Disabling IDT a patch handler da59a240 00:00:24.250984 PATM: Disabling IDT b patch handler da59a250 00:00:24.251025 PATM: Disabling IDT c patch handler da59a260 00:00:24.251063 PATM: Disabling IDT 11 patch handler da59a270 00:00:24.251097 PATM: Disabling IDT 0 patch handler da59a280 00:00:24.251133 PATM: Disabling IDT 12 patch handler da59a290 00:00:24.251166 PATM: Disabling IDT f patch handler da59a2a0 00:00:24.251250 PATM: Disabling IDT e patch handler da59a48c 00:00:24.251287 PATM: Disabling IDT 1 patch handler da59a500 00:00:24.251319 PATM: Disabling IDT 2 patch handler da59a564 00:00:24.251353 PATM: Disabling IDT 3 patch handler da59a640 00:00:24.832869 PATM: Disabling IDT 30 patch handler da599578 00:00:24.937255 PIT: mode=0 count=0x1 (65536) - 18.20 Hz (ch=0) 00:00:25.247422 OHCI: Software reset 00:00:26.403126 PATM: Disabling IDT 3c patch handler da5995d8 00:00:26.411515 PATM: Disabling IDT 31 patch handler da599580 00:00:26.508906 PATM: Disabling IDT 14 patch handler da7ed120 00:00:26.508952 PATM: Disabling IDT 15 patch handler da7ed129 00:00:26.508972 PATM: Disabling IDT 16 patch handler da7ed132 00:00:26.508989 PATM: Disabling IDT 17 patch handler da7ed13b 00:00:26.509006 PATM: Disabling IDT 18 patch handler da7ed144 00:00:26.509022 PATM: Disabling IDT 19 patch handler da7ed14d 00:00:26.
Re: replace remaining occurrences of www.lilypond.org with lilypond.org (issue 313350043 by fedel...@gmail.com)
LGTM, feel free to push directly to staging. https://codereview.appspot.com/313350043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyDev 5.0 released
Hi Paul Il giorno mar 17 gen 2017 alle 21:42, Paul ha scritto: On 01/03/2017 03:42 PM, Federico Bruni wrote: Il giorno ven 23 dic 2016 alle 17:26, Paul ha scritto: Hi Federico, I double-checked and I do/did have the box checked to enable PAE. I tried un-checking it and Virtual Box complained about it right away upon starting up the VM. So when I get a chance I may try James' approach of using a newer version of Virtual Box, or else your approach with libvirt. (No time at the moment though...) Today I've installed Virtual Box 5.1.10 on Fedora from rpmfusion. When I started the machine the first time I got an error about the kernel and I followed VB advice to run two commands as root user: akmods systemctl restart systemd-modules-load.service Then it worked fine. But Ubuntu doesn't use systemd, right? Hi all, Following James' instructions I've upgraded to VirtualBox 5.1.13 r112787 (Qt5.6.1) And I tried creating and installing a new VM with LilyDev5 but I get the same problem. (Black screen after the 'loading initial ramdisk...') I also tried the commands Federico mentioned, but they did not help. (akmods seems to be a fedora thing, not found on ubuntu, and the other command worked, but did not change anything.) I tried opening in 'recovery mode' and got this far on the screen before it froze up: rtc_cmos rtc_cmos: setting system clock to [...] UTC Freeing unused kernel memory: 740K Write protecting the kernel text: 5744k Write protecting the kernel read-only data: 1704k Loading, please wait... In the Virtualbox log files it always gets to the same place shown below. I'm at a loss on what to try next. Any ideas? Thanks in advance for any pointers or suggestions. Some ideas to help isolate the problem: - have you checked the integrity of LilyDev .iso file with md5sum? - have you started the installation from scratch (i.e. not copied the .vdi file created with previous version of VirtualBox)? - have you tried installing another Linux image on the same version of Virtualbox? - please try also installing LilyDev with virt-manager: https://virt-manager.org/ I hope to make a new release of LilyDev this week. I'd be interested to know if making LilyDev work for you requires some change to LilyDev itself (I don't think so, but let's see..). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
