Re: Musings on our translated documentation build

Il giorno lun 13 mar 2023 alle 22:20:12 +0100, Jonas Hahnfeld ha scritto: > I would like to see a test for a language in order to better understand. Here's a proof-of-concept for the French Usage Manual (sorry, if I had correctly remembered that it was you and not Jean-Charles, I would have

Re: Documentation viewer in Frescobaldi

Yes, I mean the Google Group Il giorno ven 20 gen 2023 alle 20:43:02 +1100, Andrew Bernard ha scritto: Where is the Frescobaldi mailing list? Do you mean Google Groups? Andrew On 20/01/2023 8:09 pm, Federico Bruni wrote: The answer to the other questions is more complex. We are working

Re: Musings on our translated documentation build

Il giorno mer 4 gen 2023 alle 23:36:39 +0100, Jonas Hahnfeld ha scritto: On Wed, 2023-01-04 at 22:58 +0100, Federico Bruni wrote: Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld ha scritto: > The other two formats we care about for the translated documentation > a

Re: Musings on our translated documentation build

Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld ha scritto: The other two formats we care about for the translated documentation are PDF and HTML. Of the two, HTML is arguably the more complex one in terms of infrastructure for cross-references: For PDF, we just link to the

Re: New CI runner

Il giorno lun 12 dic 2022 alle 17:34:27 +0100, Jean Abou Samra ha scritto: Le 12/12/2022 à 12:24, Karlin High a écrit : No, it is Linux. (Docker in Alpine in ProxMox.) If a macOS machine is wanted, I have a MacBook Air which could help, although its capacities are unremarkable. OK.

Re: string not clear for a translator

Il giorno mar 8 nov 2022 alle 00:16:11 +0100, Jean Abou Samra ha scritto: These are dashHat, dashPlus, etc. See "Modifying default values for articulation shorthand notation" here: https://lilypond.org/doc/v2.23/Documentation/notation/expressive-marks-attached-to-notes.html Il giorno mar 8

string not clear for a translator

I'm updating the italian language and I can't understand what this dash is about here: $ git grep -n -A4 -B4 "Re-defining dash" lily/ lily/parser.yy-3316-// - lily/parser.yy-3317-// obsoletion handling, may be removed at some

Re: source file ... .scm newer than compiled ... .go file

Il giorno mer 2 nov 2022 alle 00:12:07 +0100, Jean Abou Samra ha scritto: Your patch to Guile disables recompilation with a "return 1;" at the end of the function but keeps the logic of the check and the messages. Just additionally remove the code just above the line it's touching, or add

Re: source file ... .scm newer than compiled ... .go file

Il giorno gio 13 ott 2022 alle 00:29:15 +0200, Federico Bruni ha scritto: Il giorno mer 12 ott 2022 alle 23:59:32 +0200, Federico Bruni ha scritto: I'll have to find a solution when building the flatpak. Waiting for minutes or hours while CPU hits 100% is not an option. For the records

Re: weird error engraving two files with 2.23.14

Il giorno lun 17 ott 2022 alle 20:45:01 +, Werner LEMBERG ha scritto: \column \override #'(font-name . "Arial Bold") { D A F♯ D A D } Using `font-name` is 'absolute', that is, it overrides any LilyPond font switching mechanism. This means that `\number` doesn't work. There

Re: source file ... .scm newer than compiled ... .go file

Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra ha scritto: Le 19/10/2022 à 17:25, Federico Bruni a écrit : You have to manually add `/app/dev/bin/lilypond` in Frescobaldi. (it's explained in the Github README) It's a Frescobaldi limitation: it checks and adds only

Re: source file ... .scm newer than compiled ... .go file

Il giorno mer 19 ott 2022 alle 17:12:31 +0200, Jean Abou Samra ha scritto: Basically it limits "never recompile" to files whose path starts with "/app/". I don't know Flatpak enough to be certain that /app/ is the right path to check, though. I think it's correct. I'll test and let you

Re: source file ... .scm newer than compiled ... .go file

Il giorno dom 16 ott 2022 alle 21:35:39 +0200, Jean Abou Samra ha scritto: Le 16/10/2022 à 20:41, Federico Bruni a écrit : Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra  ha scritto: Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond development a écrit

Re: weird error engraving two files with 2.23.14

Il giorno dom 16 ott 2022 alle 21:07:22 +0200, Jean Abou Samra ha scritto: Le 16/10/2022 à 20:54, Federico Bruni a écrit : Il giorno dom 16 ott 2022 alle 12:19:46 +0200, Jean Abou Samra  ha scritto: Le 14/10/2022 à 22:19, Federico Bruni a écrit : I also had to replace # with ♯ (utf8

Re: source file ... .scm newer than compiled ... .go file

Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra ha scritto: Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond development a écrit : For the records, another application using Guile (GNU Cash) had the same problem with flatpak three years ago. Their workaround

Re: weird error engraving two files with 2.23.14

Il giorno ven 14 ott 2022 alle 12:38:55 +0200, Thomas Morley ha scritto: Thanks for the files. The culprit seems to be: tuningOpenBb = \markup { \with-dimensions #'(0 . 0.8) #'(0 . 1.0) \postscript "/Arial-Bold findfont 1.3 scalefont setfont -0.5 3.6 moveto

Re: weird error engraving two files with 2.23.14

Il giorno gio 13 ott 2022 alle 10:06:47 +, Kevin Barry ha scritto: Hi Federico, On Thu, Oct 13, 2022 at 01:06:17AM +0200, Federico Bruni wrote: Hi folks I've recently used convert-ly to update my private music sheet library and test version 2.23.14 (official binaries). Two

weird error engraving two files with 2.23.14

Hi folks I've recently used convert-ly to update my private music sheet library and test version 2.23.14 (official binaries). Two files are failing with the same error message: Drawing systems... Converting to `foo.pdf'... warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH

Re: source file ... .scm newer than compiled ... .go file

Il giorno mer 12 ott 2022 alle 23:59:32 +0200, Federico Bruni ha scritto: I'll have to find a solution when building the flatpak. Waiting for minutes or hours while CPU hits 100% is not an option. For the records, another application using Guile (GNU Cash) had the same problem with flatpak

Re: source file ... .scm newer than compiled ... .go file

Il giorno mer 12 ott 2022 alle 21:23:03 +0200, Jonas Hahnfeld ha scritto: On Wed, 2022-10-12 at 00:30 +0200, Federico Bruni wrote: Hi all I think I've already seen discussions about this. Can you please remind how to work around this error? Guile looks at file timestamps and the .go

source file ... .scm newer than compiled ... .go file

Hi all I think I've already seen discussions about this. Can you please remind how to work around this error? The 2.23.14 lilypond version built and bundled in Frescobaldi flatpak hangs forever and cannot compile any simple file, probably because it's checking this stuff. [

Re: LilyPond 2.23.8 released

On Tue, Apr 26 2022 at 08:04:40 +0100, J Martin Rushton wrote: On Tue, 2022-04-26 at 00:03 +0200, Jean Abou Samra wrote: I seem to recall that the Frescobaldi Flatpak package actually bundles LilyPond. Maybe Federico can tell more? Frescobaldi hasn't run on some flavours of Linux

Re: LilyPond 2.23.8 released

On Tue, Apr 26 2022 at 00:03:17 +0200, Jean Abou Samra wrote: (Apparently no PPA or Flatpak version.) https://flathub.org/apps/details/org.frescobaldi.Frescobaldi I seem to recall that the Frescobaldi Flatpak package actually bundles LilyPond. Maybe Federico can tell more? Yes, it

Re: error building LilyPond 2.23.7 in Frescobaldi flatpak

Il giorno gio 31 mar 2022 alle 00:27:47 +0200, David Kastrup ha scritto: Sounds like corruption to me. Either you have run out of disk space (unlikely since the file in question is pretty much in the middle), or one process wrote on a file while another process accessed it (write or read) in

error building LilyPond 2.23.7 in Frescobaldi flatpak

Hi folks Can anybody help me with the following error? Making lily/out/lexer.o < cc Making lily/out/parser.o < cc Making lily/out/lilypond /usr/lib/gcc/x86_64-unknown-linux-gnu/10.2.0/../../../../x86_64-unknown-linux-gnu/bin/ld: warning: ./out/ly-module.o has a corrupt string table index -

Re: LilyPond 2.23.7 released

On Sat, Mar 26 2022 at 22:36:05 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: Starting with this release, LilyPond requires Guile 2.2 Can anybody remind me how to build guile2 alongside guile1.8? And which precautions should I take? I use to build the latest lilypond

Re: [translations] How to get started

Hi Werner translations@ list has been dismissed. Same for the translation branch you mentioned below. Now translators work on the master branch just like the developers. The Contributor Guide contained wrong information, but this has been fixed lately and the updated manuals should appear

Re: Texinfo error: need help for debugging

On Tue, Jan 11 2022 at 05:14:37 +, Werner LEMBERG wrote: AFAIK, the problematic error message is the following: .../Documentation/out-www/it/it/usage/updating.texi:14: This command can appear only outside of any environment, not in environment @raggedright. This means that somewhere

Texinfo error: need help for debugging

Hi all I'm testing a translation patch and I cannot understand which mistake is causing the following error: ``` $ make -j3 doc [...] Please check the logfile /var/home/fede/src/lilypond-intree/Documentation/./out-www/it/usage.texi2pdf.log for errors. Last 20 lines: @\node

Re: What autogenerated documentation to translate

Hi Jean I agree with all the points made by Jonas. I would limit the contents to be translated to the minimum (the appendixes of NR). Translating and keeping up-to-date the LilyPond documentation is already a big commitment, especially for a "one man team" (as most translators nowadays).

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:

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 metapost CTAN

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

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: 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

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: 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:

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 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: Need to remove links to lilypondblog.org

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 static site generator and host it on some free platform. Hi Federico, Thanks for your message. I'd like

Re: Need to remove links to lilypondblog.org

Paul, do you have a backup of lilypondblog.org? I might try converting it to a static site generator and host it on some free platform. On Fri, Nov 12 2021 at 22:12:33 -0700, Abraham Lee wrote: Hey, LP team! I went to the LP website and saw a link in the "Pondings" section that said that

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

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.

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

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

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

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: 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: 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: 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

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

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: search-box.ihtml not tracked by check-translation script?

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 the cs translator to get

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

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. > > It worked for me on my computer, even tho

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

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 Documentation $ make ISOLANG=fr

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

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 with the usage

Re: snippets manual is not rebuilt

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 usage manuals --- Documentation/it/essay.tely | 2 +- Documentation

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

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

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

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.

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

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

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

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

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

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.

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: 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

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

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: 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: 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.

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: 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

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: 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

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: 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

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,

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

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

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 > >

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

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

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

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

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

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

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:

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

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?

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

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

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.h

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

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

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: 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 di

  1   2   3   4   5   6   7   >