Re: translation of the doc into italian

Carl D. Sorensen wrote: On 6/9/09 10:39 AM, "Federico Bruni" wrote: Hi all, as far as I can see there is not an italian documentation for lilypond. I'd like to help with that, could you please tell me how can I contribute? If other italians want to join, either for just

Re: translation of the doc into italian

Francisco Vila wrote: New files you have not told git about are not affected, see git commit --help. You must to "git add" them first. I did not really started the translation yet (but I'll do it soon). Anyway, the few changes I made should be committed now. This is my Git status: f...@fe

Re: translation of the doc into italian

Graham Percival wrote: On Sun, Jun 14, 2009 at 01:04:13AM +0200, John Mandereau wrote: After that, it would be best translating the lilypond.org main web site before translating the rest of the documentation, as the former has much more audience than the latter. Umm, I'm expecting to almost

arpeggio example in Notation Reference - tiny edit

Hi, I would have a very tiny edit for the documentation. It's a very small detail and normal users of lilypond will laugh at me, but I think it's useful for newbies (like me). Notation Reference, 1.3.3, section "Arpeggio": This is the second example: 2\arpeggio \arpeggioArrowUp 2\arpeggio

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Il giorno gio 6 feb 2020 alle 23:04, Carl Sorensen ha scritto: I think that the presence (in the proposed CoC )of an enforcement committee that has the power to sanction participants in response to anonymous complaints is more than just a bit of prose. It's the creation of a new structure tha

Re: [RFC] switch to GitLab / gitlab.com

Il giorno ven 7 feb 2020 alle 08:59, Jonas Hahnfeld ha scritto: I first want to gather consensus that GitLab is really a platform that (at least) a large part of the community could agree on, for the scoped purpose of replacing the three tools we currently use. I'm totally in favour of GitLa

Re: [RFC] switch to GitLab / gitlab.com

Il giorno ven 7 feb 2020 alle 10:36, Urs Liska ha scritto: To recap at this point: the worry about gitlab.com is similar to that wrt guthub: their TOS won't give us a substantial amount of trust in continuity of service. It's always been this situation unfortunately (see Google Code shutdown

Re: [RFC] switch to Gerrit

Il giorno ven 7 feb 2020 alle 12:09, Han-Wen Nienhuys ha scritto: Gerrit lacks an issue tracker or integrated CI solution This is a big disadvantage IMO. It means we should keep using SourceForge, right? My experience with Sourceforge is terrible, really terrible. It's the worse tracker I've

Re: Fw: Re[2]: [RFC] switch to GitLab / gitlab.com

Il giorno ven 7 feb 2020 alle 12:45, Trevor ha scritto: The Allura software that we use at SourceForge is also Open Source, I believe. See I don't know to what extent the SourceForge team have modified this, but if self-hosting is a possibility this should at lea

Re: [RFC] switch to GitLab / gitlab.com

Il giorno ven 7 feb 2020 alle 10:33, Federico Bruni ha scritto: I guess that the quality of the issue migration might influence the decision. I forgot I already investigated the SF -> GitLab migration almost 2 years ago: http://lilypond.1069038.n5.nabble.com/Allura-SourceForge-to-Git

Re: [RFC] switch to GitLab / gitlab.com

Il giorno dom 9 feb 2020 alle 22:50, Jonas Hahnfeld ha scritto: Thanks for sharing! I put together a simplistic script to create a proof-of-concept: https://gitlab.com/lilypond-issues/lilypond/issues It's only 1137 issues (now my server is blacklisted for spamming...), but it has some important

Re: [RFC] switch to GitLab / gitlab.com

Il giorno mar 11 feb 2020 alle 13:18, Jonas Hahnfeld ha scritto: > Another shortcoming is that links to other issues are broken > (transformed in links to non-existing anchors in current issue). I think that is because some issues have not (yet) been migrated. I hope these links start to wo

Re: German translation

Il giorno gio 13 feb 2020 alle 11:11, Lukas-Fabian Moser ha scritto: What's the right place to send such suggestions to? If there's going to be a new stable release soon, maybe it would be nice to get some of the more amusing translation gaffes fixed in time. LilyPond has a dedicated mailing

Re: [translations] 2.20 and 2.21 release plans

Il giorno lun 17 feb 2020 alle 22:35, David Kastrup ha scritto: Jean-Charles Malahieude writes: Le 17/02/2020 à 13:25, David Kastrup a écrit : Ok, I think 2.20 is basically done and we should push it out by the end of this week. This leaves a few days for the translation team to ca

web/introduction.itexi: replace opera series with opera seria

Can anybody fix this typo in the website? http://lilypond.org/productions.html /opera series/opera seria/ See https://en.wikipedia.org/wiki/Opera_seria It was reported by Luca Rossetto. He suggests the following wording: Luca Rossetto Casel, for his Ph.D. thesis, created a critical edition of

Re: [translations] 2.20 and 2.21 release plans

Il giorno lun 17 feb 2020 alle 22:49, Federico Bruni ha scritto: Il giorno lun 17 feb 2020 alle 22:35, David Kastrup ha scritto: Jean-Charles Malahieude writes: Le 17/02/2020 à 13:25, David Kastrup a écrit : Ok, I think 2.20 is basically done and we should push it out by the

Re: 2.20.0 release coordination with translation, also Germans? (was: [translations] 2.20 and 2.21 release plans)

Il giorno gio 20 feb 2020 alle 14:06, David Kastrup ha scritto: In unrelated news, I tried my hand at translating at least the Changes file into German and am about 50% done. Anybody want to work from the bottom so that we should coordinate in order to avoid duplicate effort? I got kind of a h

Re: [translations] Re: 2.20.0 release coordination with translation, also Germans?

Il giorno gio 20 feb 2020 alle 15:21, David Kastrup ha scritto: I could not actually get any script to do anything helpful. I remember this being different at some point of time in the past. I use `make check-translation` regularly and has always worked. But you should be aware that: 1. you

Re: lilypond.org now serving HTTPS

Il giorno ven 21 feb 2020 alle 00:01, Han-Wen Nienhuys ha scritto: The translated pages still have mixed mode data. Is it OK to edit these directly in the source tree, or will that upset our translation infrastructure? Which files are you going to change? Consider that translators are working

Re: lilypond.org now serving HTTPS

Il giorno ven 21 feb 2020 alle 16:18, Han-Wen Nienhuys ha scritto: On Fri, Feb 21, 2020 at 3:32 PM Federico Bruni wrote: Il giorno ven 21 feb 2020 alle 00:01, Han-Wen Nienhuys ha scritto: > The translated pages still have mixed mode data. Is it OK to edit > these directly

Re: 2.20.0 release coordination with translation. Other showstoppers? (was: 2.20.0 release coordination with translation, also Germans?)

Il giorno sab 22 feb 2020 alle 19:25, David Kastrup ha scritto: German Changes file has been added by now. Where are we with regard to the other translations? Federico? I'm still working on it. My spare time is limited and the changes by Werner requires a lot of meticulous edits. If you

Re: [translations] Re: 2.20.0 release coordination with translation. Other showstoppers?

Il giorno sab 22 feb 2020 alle 23:54, David Kastrup ha scritto: My principle plan would be to tell Phil to go ahead (after receiving the last OK from people doing last-minute work) at a point of time where he thinks he may be somewhat responsive in the followup days, just in case something hi

Re: [translations] Our language downloads are chaotic.

Il giorno gio 27 feb 2020 alle 02:10, David Kastrup ha scritto: For example, try downloading any French documentation from if your browser locale is not French. Possibly even if it is. I am currently setting up the size

Re: [translations] Our language downloads are chaotic.

Il giorno gio 27 feb 2020 alle 16:17, David Kastrup ha scritto: Federico Bruni writes: Il giorno gio 27 feb 2020 alle 02:10, David Kastrup ha scritto: For example, try downloading any French documentation from <http://lilypond.org/doc/v2.19/Documentation/web/notation.fr.html&g

Re: a new way to build LilyPond binary releases

Il giorno mer 11 mar 2020 alle 16:56, Jonas Hahnfeld ha scritto: This is _not_ (yet) a proposal to switch over, but rather my ideas about a possible replacement. So take this as a request for feedback and testing as well as general discussion. I've just made a test and was able to build the Li

Re: a new way to build LilyPond binary releases

Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld ha scritto: I think this one actually has the same root case as Karlin reported: I traced this back to the garbage collector freeing objects prematurely. Apparently it's not really happy that I made it unaware of threading... I've just finishe

Re: a new way to build LilyPond binary releases

Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld ha scritto: The usage of plain archives has the advantage that the user can install and move the files anywhere, without invoking any installer. That is by design, but maybe there's a valid use case for installers that I'm missing? Uninstall

Re: a new way to build LilyPond binary releases

Il giorno ven 13 mar 2020 alle 14:08, Jonas Hahnfeld ha scritto: Am Freitag, den 13.03.2020, 13:59 +0100 schrieb Federico Bruni: Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld < hah...@hahnjo.de > ha scritto: > The usage of plain archives has the advantage that the

python error running make doc

Fedora 31. /usr/bin/python points to version 3.7.6. I'm running `make doc` in the translation branch and I get this error: $ make -j3 doc GNUmakefile:30: warning: overriding recipe for target 'po-update' /home/fede/src/lilypond-translation/stepmake/stepmake/podir-targets.make:14: warning: ignori

Re: python error running make doc

Il giorno sab 11 apr 2020 alle 14:44, Jonas Hahnfeld ha scritto: This is odd, this "syntax" works fine for Python 3. However I see the mentioned error when pasting the line into Python 2. Could you double- check that your build indeed uses Python 3 (as is required for master)? I have python3

Re: poll: switching our development platform

I am in favour of Gitlab. I'm not a developer. Sometimes I contributed doc or website fixes. My (main) work of translator won't be affected at all by this decision. What I care most is the replacement of Sourceforge with something better. If choosing Gerrit means keeping Sourceforge, I would se

Re: poll: switching our development platform

Il giorno mar 21 apr 2020 alle 19:54, Jonas Hahnfeld ha scritto: Given that I would like to propose that we carry a trial of gitlab.com. I would have liked this to happen in the https://gitlab.com/lilypond group, but I haven't heard back from Janek on granting access. So I guess I will prune t

Re: Frescobaldi distribution packages

Il giorno mer 22 apr 2020 alle 15:22, Andrew Bernard ha scritto: How does lilypond get into distribution repositories anyway? Is there any thing I can do to help in this regard? You may ask the distro maintainer to upgrade the package. In Fedora, lilypond 2.20 is currently available in rawhid

Re: Make doc currently broken

Il giorno gio 23 apr 2020 alle 16:01, Jonas Hahnfeld via Discussions on LilyPond development ha scritto: Am Donnerstag, den 23.04.2020, 13:37 + schrieb Valentin Villenave: Hey everybody, For the past few days, I’ve been unable to make doc because of the following error: *** No rule

Re: [trial] getting started

Il giorno mer 22 apr 2020 alle 14:28, Jonas Hahnfeld ha scritto: here we go: https://gitlab.com/lilypond-issues/lilypond-trial To reiterate: This is _NOT_ meant for "production" work, just for evaluation. If we decide to fully use GitLab, I'll do a fresh migration into the https://gitlab.com/l

Re: [trial] getting started

Il giorno mar 28 apr 2020 alle 09:02, Jonas Hahnfeld ha scritto: Am Dienstag, den 28.04.2020, 00:27 +0200 schrieb Federico Bruni: Il giorno mer 22 apr 2020 alle 14:28, Jonas Hahnfeld ha scritto: > here we go: > https://gitlab.com/lilypond-issues/lilypond-trial > > To rei

Re: [trial] getting started

Il giorno lun 27 apr 2020 alle 22:36, Carl Sorensen ha scritto: git checkout $RELEASE_BRANCH if [ 0 -eq $(git merge-base --is-ancestor $COMMIT_ID HEAD) ]; then echo "true"; else echo "false"; fi with $RELEASE_BRANCH being the name of the branch, and $COMMIT_ID replaced with the commit id you

Re: Start contributin and Error in startup script: couldn't connect to display ":0"

Hi Caio For me (on Fedora) these two requirements are enough (to launch gitk or lily-git): https://github.com/fedelibre/LilyDev/tree/master/mkosi#running-graphical-applications-from-the-container (I've just noticed a bug in the PATH variable in LilyDev. I'll fix it soon.) If you need help w

Verifying issues on Gitlab

Hi all I've started verifying issues on Gitlab. It's quite straightforward, but still boring :-) I think that most of the times it's "useless", meaning that I can't find any error.. but sometimes you may find something useful to report: a new command to be documented, an unclear new feature, et

Re: Verifying issues on Gitlab

Il giorno lun 11 mag 2020 alle 17:12, Karlin High ha scritto: On 5/11/2020 5:01 PM, Federico Bruni wrote: If nobody else jumps in, I will probably give up soon. If someone wants to help, are there step-by-step directions anywhere? Start from this list: https://gitlab.com/lilypond

Re: Verifying issues on Gitlab

Il giorno mar 12 mag 2020 alle 08:15, Kevin Barry ha scritto: Another handy way to do this is to run git tag --contains . (For me this is faster than github.) Right, I forgot it. It's faster indeed. Thanks to everybody for jumping in so quickly!

Re: GitLab review email

Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha scritto: Rietveld used to send email to lilypond-devel for all comments by default, though one could disable that when commenting. Are we satisfied with GitLab's not doing that? As non developer, I'm satisfied :-) I'm interested in foll

Re: GitLab review email

Il giorno mar 12 mag 2020 alle 15:52, Thomas Morley ha scritto: Am Di., 12. Mai 2020 um 14:23 Uhr schrieb James : Hello On 12/05/2020 13:09, Federico Bruni wrote: > > Il giorno mar 12 mag 2020 alle 07:40, Dan Eble ha > scritto: >> Rietveld used to send email to

Re: releasing 2.21.2

Phil, while rebasing a local branch I noticed that you forgot to bump the latest version here: https://gitlab.com/lilypond/lilypond/-/blob/master/Documentation/web/news-headlines.itexi#L23 should be 2.21.2 BTW, the anchors for the @uref items in news-headlines.itexi are giving me headache

Re: `make all` too verbose after merge #84

On Wed, 5 Aug, 2020 at 07:53, James wrote: I am pretty sure I have been seeing these page counts for a while. Me too. I think it happens when you have extractpdfmark installed.

Re: fix-docsize.sh errors in make doc

Il giorno lun 14 set 2020 alle 13:44, Han-Wen Nienhuys ha scritto: On Mon, Sep 14, 2020 at 12:21 PM Michael Käppler wrote: Hi Jean, Am 12.09.2020 um 13:28 schrieb Jean Abou Samra: > Hi, > > Towards the end of the process, `make doc` outputs warnings coming > from fix-docsize.sh. Th

Re: Lilypond build

Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6 as a "normal" unstable release, without any extra wording. The issue with the Documentation build should again be fixed, so from my perspective you should be good to go (

Re: Lilypond build

Il giorno mer 16 set 2020 alle 15:39, Michael Käppler ha scritto: Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6

Re: issue verification

Il giorno ven 18 set 2020 alle 14:48, Michael Käppler ha scritto: Having looked at only four issues now, there were already two that described bugs, but lacked a description how to reproduce the problem Yes, it's quite common: I would say >90% of cases. In my experience verifying issues was ma

Re: Lilypond build

Il giorno ven 18 set 2020 alle 10:18, Michael Käppler ha scritto: Am 18.09.2020 um 00:49 schrieb Federico Bruni: Il giorno mer 16 set 2020 alle 15:39, Michael Käppler ha scritto: Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno

experimental code on Gitlab (bend-spanner repository)

Hi I'm writing to ask the permission to place some "experimental" code in a repository within the LilyPond group. The project would be called bend-spanner, so the link would be: https://gitlab.com/lilypond/bend-spanner Of course the description would highlight that it's a work in progress of

Re: experimental code on Gitlab (bend-spanner repository)

Il giorno mer 23 set 2020 alle 09:33, Jonas Hahnfeld ha scritto: Why moving it to Gitlab? - It would have more visibility for users as well as developers. - Perhaps Harm may start working on that repository instead of posting files on the mailing list :-) as he has an account on Gitlab. We

Re: experimental code on Gitlab (bend-spanner repository)

Il giorno mer 23 set 2020 alle 20:57, Thomas Morley ha scritto: Ok, ok, I will revise the code and probably extend functionality to cover bends in Voice-contexts. If I'm satisfied I'll put up a MR. Though, I doubt I can start before mid-octobre... Wow, this is the news I've been waiting for ye

Re: paconet....@gmail.com

Hi Jean lilynet.net is maintained by Valentin (now in Cc). Did you want to ask feedback for this MR? https://gitlab.com/lilypond/lilypond/-/merge_requests/418 Il giorno mer 7 ott 2020 alle 23:34, Jean Abou Samra ha scritto: Hi all, Last week I sent a message to translati...@lilynet.net to g

cleaning up the binaries in the coming Frescobaldi flatpak package

I'm working on a Linux flatpak package for Frescobaldi which will bundle LilyPond stable (currently 2.20). In order to reduce the size of the final flatpak, I want to remove the binaries which are not needed to _run_ lilypond, lilypond-book or any other lilypond script. Some binaries are creat

Re: cleaning up the binaries in the coming Frescobaldi flatpak package

Il giorno mar 20 ott 2020 alle 22:59, Jonas Hahnfeld ha scritto: The dependencies are also built by flatpak (so not the "official" binaries) and the process is steered through the yaml file that you submitted, right? (https://github.com/flathub/flathub/pull/1277) Yes! No, I think you actual

Re: experimental code on Gitlab (bend-spanner repository)

Il giorno gio 22 ott 2020 alle 10:19, Thomas Morley ha scritto: Hi Federico, see: https://gitlab.com/lilypond/lilypond/-/merge_requests/473 Great! I'll check it out in the next days. There are some changes in usage. - A BendSpanner is now started with \^ and ends automatically at the next

Re: State of 2.22

Il giorno gio, nov 26 2020 at 20:08:53 +0100, Jonas Hahnfeld ha scritto: Anybody disagreeing with this plan? Translators, please let me know if you need more time. I'm glad we are moving towards 2.22. I'll try to work on the italian translation next week.

snippets manual is not rebuilt

I'm translating the snippets manual for the first time and I see that `make doc` does not rebuild it when source is updated. It's a bug or I'm missing something? How can I force it? NOTE: As a translator I do _not_ compile out of tree. $ ls -l out-www/offline-root/Documentation/snippets/index*

Re: snippets manual is not rebuilt

Il giorno mer, dic 9 2020 at 00:04:22 +0100, Knut Petersen ha scritto: I'm translating the snippets manual for the first time and I see that `make doc` does not rebuild it when source is updated. I use make WEB_TARGETS="offline online" top-doc doc Thanks, but it's not workin

search-box.ihtml not tracked by check-translation script?

Any reason why search-box.ihtml is in Documentation/ instead of Documentation/en? It seems it's causing troubles to the check-translation script: $ cd Documentation $ make ISOLANG=fr check-translation | grep 'diff --git' warning: fr/search-box.ihtml: 128 fatal: path 'Documentation/en/search-box

Re: snippets manual is not rebuilt

nknown node in menu entry `Relocation' (in out-www/it/usage/running.texi l. 59) Max error number exceeded From 3f903598f2e317f076747e0120b355eefd62ab9e Mon Sep 17 00:00:00 2001 From: Federico Bruni Date: Tue, 15 Dec 2020 06:17:14 +0100 Subject: [PATCH] Doc-it: Update essay, learning and us

Re: snippets manual is not rebuilt

build. Il giorno mar, dic 15 2020 at 12:06:23 +0100, Michael Käppler ha scritto: Hi Federico, try to delete out-www/it/usage.texi and run 'make doc' again. Cheers, Michael Am 15.12.2020 um 06:51 schrieb Federico Bruni: It's not just the snippets manual. It just happened

Re: snippets manual is not rebuilt

Il giorno mar, dic 15 2020 at 11:46:55 +0100, Knut Petersen ha scritto: Thats all. (un)fortunately I see NO error message. Here's the 'make doc' error I see: Command: DEPTH=../../ TOP_SRC_DIR=/home/fede/src/lilypond-git PERL_UNICODE=SD texi2html --prefix=index --split=section --error-limi

Re: search-box.ihtml not tracked by check-translation script?

other languages are appended. Any advice is welcomed! :-) Il giorno mer, dic 9 2020 at 00:38:05 +0100, Federico Bruni ha scritto: Any reason why search-box.ihtml is in Documentation/ instead of Documentation/en? It seems it's causing troubles to the check-translation script: $ cd Docume

Re: search-box.ihtml not tracked by check-translation script?

ailed Does that point you in the right direction? Kevin On Fri, 18 Dec 2020 at 20:27, Federico Bruni wrote: > > I've just submitted a MR: > https://gitlab.com/lilypond/lilypond/-/merge_requests/545 > > but it doesn't pass the doc build pipeline. > > I

Re: search-box.ihtml not tracked by check-translation script?

than English content. Jonas Am Freitag, dem 18.12.2020 um 22:32 +0100 schrieb Federico Bruni: Ok, thank you Jonas! There's a third option I like more: 3) mandatory translation of search-box.ihtml (it's already in the list of files to be translated in the CG manual) I may contact

Re: empty PNG files in `Documentation/pictures`

Il giorno lun, dic 28 2020 at 17:56:34 +0100, Werner LEMBERG ha scritto: There are six empty PNG files in `Documentation/pictures`: nav1-active.png nav1-bg.png nav1-hover.png nav2-active.png nav2-bg.png nav2-hover.png Is this really correct? I don't think it's correct. If

Re: state of the ’Pond for earnest tadpoles

Il giorno ven, gen 1 2021 at 16:37:40 -0500, Kieren MacMillan ha scritto: Hi Jonas (et al.), I would claim that the contributor experience has been pretty stable since the initial switch to GitLab. Enabling CI and the recent work to also run 'make check' automatically shouldn't change

Re: Update config.guess and config.sub?

Il giorno mar, feb 2 2021 at 15:10:19 -0700, Owen Lamb ha scritto: Hi all, I've found that the config/config.guess and config/config.sub files are pretty out of date. (They aren't able to recognize Ubunto 20.04 running on my Raspberry Pi, anyway, while the latest versions of the files do

Re: Test reader speed of Guile 3.0.6

On Wed, Mar 10 2021 at 10:18:53 PM +0100, Thomas Morley wrote: /bin/bash: gperf: command not found you should install gperf package :-)

Re: Unable to revert mtime: /Library/Fonts

Il giorno ven, mar 12 2021 at 11:10:09 +0800, wyanshan ha scritto: Hi I use Lilypond’s Frescobaldi 3.1.2 on my MacBook Pro 10.15 Catalina. After downloading frescobaldi 3.1.2, I go to directory and run./frescobaldi, I got the following: Starting lilypond 2.20.0 [Untitled]... Unable

Re: Reducing the number of open issues

On Wed, Mar 17 2021 at 08:10:08 PM +0100, Jonas Hahnfeld wrote: In the longer term, I think it could make sense to hold a "bug bash weekend" and try to pick some low-hanging fruits. That would not be limited to developers to write patches, but everybody to try and reproduce old reports with the

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

On Thu, May 13 2021 at 22:46:58 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: After some work, I built binaries from the released sources of LilyPond 2.22.1 for * Linux (compiled on CentOS 7; tested on Arch, CentOS 8, Ubuntu 18.04) Have you thought about adding more a

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

On Thu, May 20 2021 at 08:26:18 +0200, Jonas Hahnfeld wrote: Yes, I *hope* that it would be straight-forward to produce binaries with the same set of scripts, provided dependencies like Guile and friends don't choke about the architecture. It clearly needs a native build host, but it's not obvio

Re: Mailing list for translations

Il giorno mar 22 giu 2021 alle 10:45:17 +0200, Jean Abou Samra ha scritto: Moreover, as Valentin, the administrator of lilynet.net, is (currently) inactive as a developer, I think we should strive to move discussions to mailing lists hosted by gnu.org, which is proven to have long-term reliabili

Re: Mailing list for translations

On Tue, Jun 22 2021 at 17:53:05 +0200, Jean Abou Samra wrote: Yes. And on GitLab, if this turned out to be a significant problem, we could also add a "Translation" label, and let translators use the "Subscribe to label" feature. https://about.gitlab.com/blog/2016/04/13/feature-highlight-subscri

Re: Obsolete labels

I'm too late, as I see you've already delted them. Anyway.. Il giorno sab 26 giu 2021 alle 15:09:31 +0200, Jonas Hahnfeld via Discussions on LilyPond development ha scritto: * Frog: Does this still provide value? I would have suggested to replace it with a word that anybody can easily un

Re: Binaries of LilyPond 2.23.5 with Guile 2.2

On Fri, Dec 3 2021 at 19:17:19 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: here are the binaries of LilyPond 2.23.5 with Guile 2.2, created exactly with the scripts contained in the official source tar: https://gitlab.com/hahnjo/lilypond/-/packages/4049140 (For now I've

Re: Binaries of LilyPond 2.23.5 with Guile 2.2

On Wed, Dec 8 2021 at 21:25:47 +0100, Jonas Hahnfeld wrote: Am Mittwoch, dem 08.12.2021 um 01:43 +0100 schrieb Federico Bruni: On Fri, Dec 3 2021 at 19:17:19 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: > here are the binaries of LilyPond 2.23.5 with Guile

Re: Binaries of LilyPond 2.23.5 with Guile 2.2

On Thu, Dec 9 2021 at 08:24:27 +0100, Jonas Hahnfeld wrote: LilyPond is built from source on Flathub infrastructure. If you click on the green check here: https://github.com/flathub/org.frescobaldi.Frescobaldi/commits/master you'll see the recent builds. This is for aarch64: https:/

Re: Binaries of LilyPond 2.23.5 with Guile 2.2

On Thu, Dec 9 2021 at 18:36:47 +0100, Jonas Hahnfeld wrote: Is it a requirement that you provide AArch64, or are there actually users? (on which platform?) It's not a strict requirement. I may skip this architecture and build only x86_64, but I'd rather keep it. I don't have any statistics

Re: Need to remove links to lilypondblog.org

On Sun, Nov 14 2021 at 21:14:16 +0100, Federico Bruni via Discussions on LilyPond development wrote: On Sun, Nov 14 2021 at 09:06:32 -0500, Paul Morris wrote: On 11/13/21 2:53 AM, Federico Bruni wrote: Paul, do you have a backup of lilypondblog.org? I might try converting it to a

No makefile found

Hi folks I don't know what's happening. Yesterday I could run make without any problem. Today, after some cleaning, I cannot run it anymore. A Makefile should be generated in the build directory? I followed the CG instructions as usual: ./autogen.sh --noconfigure && mkdir build && cd build &&

Re: No makefile found

On Tue, Dec 28 2021 at 22:47:41 -0800, Aaron Hill wrote: Any errors or warnings during configure? Perhaps there was a subtle change in your environment. Yes, I have errors because I did not want to install all the dependencies in my container. What's the package(s) needed to build the Makefi

Re: No makefile found

On Wed, Dec 29 2021 at 12:43:40 +0100, Federico Bruni wrote: ERROR: Please install required programs: TeX Gyre fonts OTF (make sure the fc-list utility can see them, e.g. 'sudo apt-get install fonts-texgyre', or use --with-texgyre-dir) mf-nowin mf mfw mfont mpost kpsewhich met

Doc: is a tag not an environment

Hi While translating I saw that the tag recognized by lilypond-book is called environment (as \lilypond{} in LaTeX). Wouldn't it be more correct to call it tag? Here's the part of the Usage manual where HTML is discussed: https://gitlab.com/lilypond/lilypond/-/blob/master/Documentation/en/usa

Re: ‘Know which branch we’re on’ on Ubuntu 16

Il giorno dom 4 giu 2017 alle 17:58, Simon Albrecht ha scritto: Hello, finally I’ve managed to get Ubuntu 16.04 working, and copied all of my previous home directory including .bashrc. However, the ‘export PS1’ trick suggested in

Re: Micro release feature list

Il giorno lun 26 giu 2017 alle 21:46, kieren_macmillan kieren_macmillan ha scritto: I look for "Fixed__2_19_x" in the issue tracker. Another way is entering the lilypond-git directory and then launch gitk (or similar GUI tools, like gitg), where you'll see the tags associated with releases.

Re: Making LilyPond quickly

Il giorno mar 27 giu 2017 alle 16:58, Charles Winston ha scritto: So far for my chords project, I’ve only been editing Scheme files, so I haven’t needed to build lilypond at all to test. Now I’m working on C++ files, so I need to compile in order to test my changes. It’s frustrating that compi

for Jay Anderson: solution to "MergeFonts: Can't find font: feta11.pfb" problem

Jay, today I've stumbled upon the same problem you reported here: http://lilypond.1069038.n5.nabble.com/Building-issues-lilypond-and-docs-td198696.html#a198786 Context: I'm building a Fedora container which I'd like to make available as an alternative to current LilyDev. As I want to keep it as

LilyDevOS, a LilyDev container

Hi folks I've made a LilyDev container which can be run with systemd-nspawn. You can download v0.1 and find the instructions here: https://github.com/fedelibre/LilyDevOS This is only for Linux users at the moment. I'm not sure if you need a certain version of systemd to run it correctly. Probab

Re: LilyDevOS, a LilyDev container + full VM image

age is ready to be launched. Read the main README on Github for instructions on how to use it. I've tested it only on Linux host. https://github.com/fedelibre/LilyDevOS/releases/tag/v0.1 Il giorno gio 6 lug 2017 alle 17:03, Federico Bruni ha scritto: Hi folks I've made a LilyD

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno sab 15 lug 2017 alle 20:43, Paul ha scritto: On 07/14/2017 05:52 AM, Federico Bruni wrote: https://github.com/fedelibre/LilyDevOS/releases/tag/v0.1 Hi Federico, This looks great! I downloaded the one for linux (I'm on Ubuntu 16.04 LTS) and gave it a try. I ran into

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno lun 17 lug 2017 alle 10:58, Federico Bruni ha scritto: Il giorno sab 15 lug 2017 alle 20:43, Paul ha scritto: And I was able to successfully build lilypond in the container. (Look mom, no VM!) So this is really nice. I can edit files using my usual desktop

Re: Any objections to branching off a stable branch for 2.20?

Il giorno lun 17 lug 2017 alle 19:14, David Kastrup ha scritto: Other things up for cherry-picking are documentation changes and their translations. Since translations usually are done in "bulk", it would make sense to only translate stuff in the stable 2.20 branch in the interregnum: that way

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno lun 17 lug 2017 alle 9:58, Federico Bruni ha scritto: Thanks Paul, I'll update the README. I've now updated the instructions about the container. I've also added instructions on setting up the virtual machine in libvirt (i.e. also GNOME Boxes and virt-manager

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno lun 17 lug 2017 alle 16:58, Federico Bruni ha scritto: Good point. I don't think that there's even any browser in the container now. Perhaps I may install a text browser and set the BROWSER environment variable. I have a small patch to send, I'll let you kn

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno ven 21 lug 2017 alle 20:29, Paul ha scritto: On 07/17/2017 04:58 AM, Federico Bruni wrote: A suggestion: it might be worth clarifying the steps for first setup vs repeat use of the container? I think the main (only?) difference is that you don't need to run the setup s

Re: LilyDevOS, a LilyDev container + full VM image

Il giorno lun 17 lug 2017 alle 17:58, Federico Bruni ha scritto: You can use an alias and forget the special command. Add this line to ~/.bashrc: # Let gitk work on host display alias gitk="DISPLAY=:0 gitk" As .bashrc is the same for container and full VM, I won't add this

  1   2   3   4   5   6   7   >