LilyPond 2.25.16

We are happy to announce the release of LilyPond 2.25.16. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

Any active Chinese translator?

Dear developers of Lilypond, I'm Lex, a regular Lilypond user now.  And I'm planning to translate the website / manuals into Chinese. Still trying to sort out the translation process. Any help / reminder would be very welcome. Done: - Gitlab account and repository cloning / forking Todo

Re: [RFC] Move GitLab testing to Ubuntu 22.04

On Wed, 2024-05-01 at 22:20 +0200, Michael Käppler wrote: > > > There is one caveat here that I would like to mention: During initial > > testing in my fork, one test job unexpectedly hang during a lilypond > > execution, using 100% CPU and eventually being killed after 60 mi

Re: [RFC] Move GitLab testing to Ubuntu 22.04

Hi Jonas, Hi all, I mentioned this during the transition to Guile 3.0, and now I had the time to prepare the required changes to move the base of our GitLab testing to Ubuntu 22.04. The merge request to do so is here: https://gitlab.com/lilypond/lilypond/-/merge_requests/2318 Many thanks

[RFC] Move GitLab testing to Ubuntu 22.04

Hi all, I mentioned this during the transition to Guile 3.0, and now I had the time to prepare the required changes to move the base of our GitLab testing to Ubuntu 22.04. The merge request to do so is here: https://gitlab.com/lilypond/lilypond/-/merge_requests/2318 There is one caveat here

Re: LilyPond 2.25.15

Great !!!Thanks for fixing the guile 3 bug on Windows... GillesLe samedi 20 avril 2024 à 18:18:24 UTC+2, Jonas Hahnfeld via LilyPond user discussion a écrit : We are happy to announce the release of LilyPond 2.25.15. This is termed a development release, but these are usually reliable

LilyPond 2.25.15

We are happy to announce the release of LilyPond 2.25.15. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

Music property articulations

Hey all, I am trying to add articulations to my music braille generator. As stated before, I am using the event listening system proposed by the "event-listener.ly" example. Browsing through the documentation, I found the music property articulations on

Re: [RFC] Transition to Guile 3.0

Am 08.04.2024 um 23:40 schrieb Jonas Hahnfeld: Thanks for testing! I assume this is also enabling Guile optimizations during LilyPond runtime? It would be interesting to see if there's a gain from just compiling the bytecode with optimizations. That would be a one-time cost that may be worth

Re: [RFC] Transition to Guile 3.0

Am 08.04.2024 um 23:40 schrieb Jonas Hahnfeld: [snip] Thanks for testing! I assume this is also enabling Guile optimizations during LilyPond runtime? It would be interesting to see if there's a gain from just compiling the bytecode with optimizations. That would be a one-time cost that may

Re: [RFC] Transition to Guile 3.0

On Tue, 2024-04-02 at 16:40 +0200, Michael Käppler wrote: > Am 01.04.2024 um 22:03 schrieb Jonas Hahnfeld via Discussions on LilyPond > development: > > As pointed out by Han-Wen in November, this is actually fairly little > > code that gets dropped; we need to keep some relate

Re: [RFC] Transition to Guile 3.0

Am 01.04.2024 um 22:03 schrieb Jonas Hahnfeld via Discussions on LilyPond development: This is now up for review in the following merge request: https://gitlab.com/lilypond/lilypond/-/merge_requests/2293 As pointed out by Han-Wen in November, this is actually fairly little code that gets

Re: extracting markup texts for braille

Hi Aaron, That is a great suggestion. Thanks a lot! I have been playing around with it and noticed that in order to keep the order of the generated braille identical to the Lilypond code, I would need to also override the top-level-score-handler, and possibly others to keep track

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 4: Remove compatibility code for Guile 2.2 > This can happen after we made one or two releases with only Guile 3.0. This is now up for review in the following merge request: https://gitlab.com/lilypond/lilypond/-/merge_request

extracting markup texts for braille

Hey all, I also asked this question on the lilypond-user mailing list, but I gather it is a rather complex question for that list. As you might be aware, I have been working on a braille extension for Lilypond which (based on the music info extraction example) renders Lilypond scores

Re: LilyPond 2.25.14

Hello, Here are my results for MSDM.ly on a M2 Max MacBook Pro: real 12.11 user 11.02 sys 1.06 Thanks a lot! Mathieu

Re: LilyPond 2.25.14

Am 24.03.2024 um 11:50 schrieb Jonas Hahnfeld: Just out of interest, do we tweak the JIT_THRESHOLD somewhere or do we use the default value? I don't think we change it from LilyPond, so likely using the default value. I did a test with the opposite extremes. Again, 10 subsequent runs

Re: LilyPond 2.25.14

  0m0.090s > sys 0m0.185s > > without JIT: > real    4m45.295s > user    0m0.046s > sys 0m0.277s Thanks for testing on a larger score! > Just out of interest, do we tweak the JIT_THRESHOLD somewhere or do we > use the default value? I don't think we change it from L

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:08 -0700, Kenneth Wolcott wrote: > Hi Jonas; > > I hope that the following information is useful: > > Lilypond performance stats for the engraving of one very small and one > medium sized pieces > > native = Apple Silicon build > foreign = x

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:24 -0500, Karlin High wrote: > On 3/23/2024 2:00 PM, Jonas Hahnfeld wrote: > > Would be interesting to see how this compares to the "vanilla" package > > I tried it, 3 runs. First one maybe unfair because font cache > initialization or something. > > real0m48.643s >

Re: LilyPond 2.25.14

On Sun, 2024-03-24 at 03:20 -0700, Aaron Hill wrote: > The error occurred from my WSL1 environment running Ubuntu 18.04. > Probably my own fault for keeping bionic around. Ah ok; yes, Ubuntu 18.04 is end-of-life since last year already, so I didn't check its versions. > I do have Ubuntu 20.04

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 18:18 -0700, Aaron Hill wrote: > On 2024-03-23 6:25 am, Jonas Hahnfeld wrote: > > We are happy to announce the release of LilyPond 2.25.14. This is > > termed a development release, but these are usually reliable for > > testing new features and rece

Re: LilyPond 2.25.14

the second and third page, as if I had inserted > a forced page break in two or three places. There were no conversion > errors or warnings in any of my engravings. > > I don't know what was the cause of the speedup, but it is > appreciated! I have been using the MacPorts version of

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 17:46 +0100, Jean Abou Samra wrote: > Le samedi 23 mars 2024 à 16:02 +0100, Jonas Hahnfeld via Discussions on > LilyPond development a écrit : > > Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D > > This is a native arm64 ve

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 11:41 -0500, Karlin High wrote: > On 3/23/2024 10:02 AM, Jonas Hahnfeld via LilyPond user discussion wrote: > > Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj > > This turns on just-in-time compilation that was added in Guile 3.0,

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:25 +0100, Jonas Hahnfeld wrote: > We are happy to announce the release of LilyPond 2.25.14. This is > termed a development release, but these are usually reliable for > testing new features and recent bug fixes. Following this release, I made two speci

LilyPond 2.25.14

We are happy to announce the release of LilyPond 2.25.14. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

[RFC] Upgrade platforms for official binaries

Hi all, as noted in https://gitlab.com/lilypond/lilypond/-/merge_requests/2246, we are starting to run into some issues because of dated software in CentOS 7 and Ubuntu 20.04. For that reason, I'm proposing in https://gitlab.com/lilypond/lilypond/-/merge_requests/2261 to upgrade our platforms

LilyPond 2.25.13

We are happy to announce the release of LilyPond 2.25.13. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

Auto-resetting of context properties

Folks, the following is triggered mainly (but not solely) by my short exchange with Dan (https://gitlab.com/lilypond/lilypond/-/merge_requests/1617#note_1735195563): We have some context properties that are persistent (e.g. figuredBassPlusDirection), whereas others are effective once

Re: [RFC] Transition to Guile 3.0

ple because the system is missing the development package for Guile > 3.0... This next step (requiring Guile 3.0 and removing automatic detection of Guile 2.2 from configure) is now available as https://gitlab.com/lilypond/lilypond/-/merge_requests/2228 Jonas signature.asc Description: This is a digitally signed message part

LilyPond 2.25.12

We are happy to announce the release of LilyPond 2.25.12. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

Re: numbers

On 2023-12-27 10:51 pm, Werner LEMBERG wrote: Well, both `#+3` and `#-3` work, so it might be tempting to assume that `+3` and `-3` also work (outside of `\markup`). So does ##e+3.0 and so does #3/1 so should we be supporting those as well? The former? Rather not. The latter, maybe. I can

Re: Can't automatically merge

On Thu, 2023-12-14 at 17:43 +, Werner LEMBERG wrote: > > > > Looks like it was fixed? > > > > https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 > > > > > > Yep, thanks. > > > > I spoke too early – it's still not working properly. > > On this page I read: > >   For

LilyPond 2.25.11

We are happy to announce the release of LilyPond 2.25.11. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 3: Switch to Guile 3.0 > Afterwards, we can merge > https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 I put the merge request back on Patch::review, along with https://gitlab.com/lilypond/lilypond/-/merge_requ

LilyPond 2.24.3 released!

We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. This version contains a number of fixes since

Re: Plan for LilyPond 2.24.3

in case anybody wants to test before the official announcement tomorrow (evening): https://gitlab.com/lilypond/lilypond/-/packages/20395285 Cheers, Jonas signature.asc Description: This is a digitally signed message part

Re: LilyPond 2.25.10 with Guile 3.0

On Thu, 2023-11-16 at 11:11 -0600, Karlin High wrote: > On Sun, Nov 12, 2023 at 6:26 AM Jonas Hahnfeld via LilyPond user > discussion wrote: > > If you have some time, please test them in your setups and report back in > > case of problems! > > Seems OK so far. Window

Plan for LilyPond 2.24.3

ovember 18, and the final release on Sunday, November 19 - in the worst case this may slip to Monday, but I don't really have much time then so hopefully not... The draft release announcement text is: --- We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond is a music engraving progr

LilyPond 2.25.10 with Guile 3.0

On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote: > We are happy to announce the release of LilyPond 2.25.10. And here are the binaries with Guile 3.0, built using https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and https://gitlab.com/lilypond/lilypond/-/merge_requests/2

Re: [RFC] Transition to Guile 3.0

On Sat, 2023-11-11 at 18:37 +0100, Han-Wen Nienhuys wrote: > On Sun, Nov 5, 2023 at 10:36 PM Jonas Hahnfeld wrote: > > Hi all, > > > > I hear LilyPond hasn't changed its Guile version since some time (more > > than 18 months). So before we get too comfortable with the

LilyPond 2.25.10

We are happy to announce the release of LilyPond 2.25.10. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer

Plan for LilyPond 2.24.3 and Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 1: Officially support Guile 3.0 and add optional CI testing > I opened https://gitlab.com/lilypond/lilypond/-/merge_requests/2162 to > add some compatibility with earlier versions of Guile 3.0 and then > implement detec

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:48 +0100, Jean Abou Samra wrote: > What I don't really understand is why you want to add compatibility > with Guile 3.0.x for small x. Upstream completely breaks the normal > expectation from what you would find in a point release, by putting > features and even severely

[RFC] Transition to Guile 3.0

Hi all, I hear LilyPond hasn't changed its Guile version since some time (more than 18 months). So before we get too comfortable with the current situation, let me propose to move to Guile 3.0. Below is a plan for that switch, with a transition period to test the official binaries. Last time

SVGs in Documentation

I noticed that the online documentation often uses PNG images of the engraving output, rather than SVG images.  Now that SVG images are widely supported in browsers, perhaps we should consider transitioning the documentation to SVG images.  I'm sure that this would be a low priority, but it

LilyPond 2.25.9

We are happy to announce the release of LilyPond 2.25.9. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer

Re: [RFC] HTML documentation with texi2any

On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > For a possible timeline, we could wait for the release of LilyPond > 2.25.8 (probably September 16/17 because I'm travelling next weekend, > unless Jean wants to do it again) and t

Re: Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

not interfere with the existing code, which I agree is quite complex. -- Sent with Tutanota, enjoy secure & ad-free emails. Sep 21, 2023, 06:37 by j...@abou-samra.fr: > Le mercredi 20 septembre 2023 à 05:06 +0200, yuanyelele--- via Discussions on > LilyPond developme

Re: Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

Attached is a sample of Jianpu notation. The two patches I submitted are necessary for the underlines to function correctly here. -- Sent with Tutanota, enjoy secure & ad-free emails. Sep 20, 2023, 14:41 by w...@gnu.org: >> These two patches introduce a boolean context property called >>

Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

Dear list, I'm currently bug fixing and improving an older script, jianpu10a.ly <https://github.com/nybbs2003/lilypond-Jianpu/blob/master/jianpu10a.ly>, which aims to introduce Jianpu (numbered musical notation) <https://en.wikipedia.org/wiki/Numbered_musical_notation>

Re: [RFC] HTML documentation with texi2any

On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld wrote: > For a possible timeline, we could wait for the release of LilyPond > 2.25.8 (probably September 16/17 because I'm travelling next weekend, > unless Jean wants to do it again) and then merge the changes right > after

LilyPond 2.25.8

We are happy to announce the release of LilyPond 2.25.8. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer

Re: Source tarballs on lilypond.org

On Sun, 2023-09-03 at 15:18 +0200, Jean Abou Samra wrote: > Le dimanche 03 septembre 2023 à 14:48 +0200, Jonas Hahnfeld a écrit : > > Can you please > > change it to something more like: > > "IMPORTANT: Binaries and documentation archives are NOT updated on > > lilypond.org anymore, please refer

Re: Source tarballs on lilypond.org

On Sun, 2023-09-03 at 14:29 +0200, Jean Abou Samra wrote: > Le vendredi 01 septembre 2023 à 19:56 +0200, Jonas Hahnfeld a écrit : > > Yes, could be a good idea. Looking at the directory, it seems like the > > contents of README.html are displayed below the list of directories, > > maybe we should

[RFC] HTML documentation with texi2any

ting https://gitlab.com/lilypond/lilypond/-/merge_requests/1109 It is (in my opinion) a very minor cosmetic change and, as you can read up in that merge request, it already hit some objections when it was introduced one and a half years ago. With texi2any, we do not have the same customization hook and

Re: Source tarballs on lilypond.org

On Fri, 2023-09-01 at 16:25 +0200, Jean Abou Samra wrote: > > As for the issue, I consider that somewhat of an outlier: Most users > > will follow the links on the website, and everything will work for > > them. A small fraction tries to find the binaries where they used to be > > (and I'm

Re: Source tarballs on lilypond.org

On Fri, 2023-09-01 at 14:31 +0200, Jean Abou Samra wrote: > Hi, > > Per the release procedure > https://lilypond.org/doc/v2.25/Documentation/contributor/release-checklist , > GitLab releases for LilyPond contain both binaries + doc tarballs and source > tarballs generate by

Prototype for HTML documentation with texi2any

Hi all, after months of preparations (if not years) and actual implementation work during the last few weekends, I would like to share the first complete prototype for generating LilyPond's HTML documentation with texi2any: https://gitlab.com/lilypond/lilypond/-/merge_requests/2089 Before you

LilyPond 2.24.2 released!

We are proud to announce the release of GNU LilyPond 2.24.2. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. This version contains a number of fixes since

Re: Plan for LilyPond 2.24.2

On Tue, 2023-08-08 at 10:57 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > I finally have (fixed) internet again! With that, the plan would be to > first check for additional backports and then build the binaries during > the week, probably tomorrow or Thursday.

Re: Plan for LilyPond 2.24.2

Hi all, On Fri, 2023-07-28 at 08:28 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on

Re: Flex on macOS

On Mon, 2023-07-31 at 09:54 +0200, Jean Abou Samra wrote: > > Yes, but flex has always been there as a dependency of some other > > package I think, only not added in your environment variables. We can > > explicitly add it to the Brewfile if you think that's better, but it > > shouldn't change

Re: Flex on macOS

On Mon, 2023-07-31 at 01:15 +0200, Jean Abou Samra wrote: > Hi, > > As a follow-up to the release: on macOS I encountered a quirk which is > that the compiler spit out build errors on the Flex-generated lexer > out/lexer.cc. (Now I find myself stupid for not saving the error messages >

Re: fix-docsize errors in build-doc.sh

On Sun, 2023-07-30 at 18:31 +0200, Jean Abou Samra wrote: > Trying to do the release, I got these messages during "./build-doc.sh": > > [...] > > Is that expected? Yes, it has always been there for the online pages because the big- pages use language content negotiation and aren't valid file

Re: Plan for LilyPond 2.24.2

On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > I plan to build the binaries next weekend, July 8th or 9th, for > >

Re: Cannot build latest master branch

On 2023-07-27 05:22, Jean Abou Samra - jean(a)abou-samra.fr wrote: By the way, where are all those compiler flags coming from? Did you write them by hand? Did you copy them from somewhere? These flags are mostly for a better debugging experience and strengthened security. A lot of them are

Re: Cannot build latest master branch

On 2023-07-26 14:13, Jean Abou Samra - jean(a)abou-samra.fr wrote: Yes, I deleted the build directory before redoing autogen.sh, redid `mkdir build && cd build` in between autogen.sh and configure Then you failure is pretty strange. Can you show the output of "build/out/bi

Re: Cannot build latest master branch

On 2023-07-26 11:51, Jean Abou Samra - jean(a)abou-samra.fr wrote: I'm not sure we understand "clean build" in the same way. I get that you rerun autogen and configure, but are you starting from a completely empty build directory? Yes, I deleted the build directory before redoing autogen.sh,

Re: Cannot build latest master branch

On 2023-07-26 11:17, Jean Abou Samra - jean(a)abou-samra.fr wrote: I also got the compilation error, but after adding , my locally built LilyPond works fine. Is this from a clean build? Yes. After redoing: * ./autogen.sh --noconfigure * ../configure --prefix=/home/lj/projects/internships

Re: Plan for LilyPond 2.24.2

On Mon, 2023-07-17 at 07:08 +0200, Jean Abou Samra wrote: > Le samedi 08 juillet 2023 à 15:29 +0200, Jonas Hahnfeld via Discussions on > LilyPond development a écrit : > > Unfortunately, this won't happen: My fiber is cut and I don't have > > (fixed) internet  and while I

Re: Plan for LilyPond 2.24.2

On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > I plan to build the binaries next weekend, July 8th or 9th, for > the final release on Wednesday, July 12th. Unfortunately, this won't happen: My fiber is cut and I don't have (fixed) in

Re: `make bytecode && make doc` broken

On Sat, 2023-07-08 at 10:20 +, Werner LEMBERG wrote: > Currently, `make bytecode && make doc` is broken: https://lists.gnu.org/archive/html/lilypond-devel/2023-07/msg8.html (it's not like there are hundreds of messages every day, a duplicate thread doesn't se

Re: Plan for LilyPond 2.24.2

On Sat, 2023-07-01 at 21:34 +0200, Jean Abou Samra wrote: > The idea of the delay between the build and the release is to let people test > the binaries first, right? Yes, I will upload the binaries to GitLab but only do the tagging + announcement + website upload on Wednesday, in case anything

Plan for LilyPond 2.24.2

Hi all, after the unstable release 2.25.6 is out and the included update of bdwgc seems to resolve the rare crashes on Windows (not backported yet), I would like to go ahead with the stable version 2.24.2. If there is anything else that needs to go in, please ping me on GitLab. I plan to build

LilyPond 2.25.6

We are happy to announce the release of LilyPond 2.25.6. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.1, the current stable release. Please refer

Re: MR milestones

On Thu, 2023-06-22 at 14:32 +0200, Jean Abou Samra wrote: > Recently, GitLab gained a "bulk edit" button in the MR view. This button has "always" been there ... > That means the person doing the release (currently Jonas) can > easily assign all the MRs merged during the release in a few >

Re: 2.25.6 release

not clear that a fix will land before the next weekend. > > Regarding (b), I've now submitted  > https://gitlab.com/lilypond/lilypond/-/merge_requests/2041 which I hope will > be satisfactory for everyone. Thanks! In light of that fix, let's delay the release by one week (there's no

Re: Getting beam subdivision working

m just be a Beaming_pattern?  Perhaps using the same class of object would prevent duplication. The purpose of my Subbeam class is to calculate a local baseMoment and beatStructure on the fly. You can see at https://gitlab.com/ljyip/lilypond/-/blob/e7d39a076ccf50555bfa2d352400caaf28db2678/lily/b

Re: Getting beam subdivision working

it?) It's a bit messy at the moment and definitely needs more code comments. Just make the fork public. In FOSS, people usually like when things are public and do not mind to see the ugly guts of your work in progress. Ok, it's at https://gitlab.com/ljyip/lilypond -- - Jason Yip

Re: 2.25.6 release

On Fri, 2023-06-16 at 10:37 +0200, Jean Abou Samra wrote: > I know that 2.25.6 was planned for this weekend. Unfortunately, due to  > https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not > going to work on Kubuntu and possibly other distros. > > I will t

LilyPond 2.25.5

We are happy to announce the release of LilyPond 2.25.5. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.1, the current stable release. Please refer

Re: Fix Lilypond Beaming GSOC Project

Hey Carl, I should have the time to get started with the on-boarding process now. To reiterate, I have a working develop environment for Lilypond now; I can edit whatever source files then build them without much hassle. One thing that concerns me is that generating tests takes a long time

Next releases

Hi all, due to various constraints, I am kind of restricted when I will be able to do the next releases, so I thought I might as well let you know: LilyPond 2.25.5 will happen on the weekend of the 20th/21st (unless I get too bored this next weekend...). I'm planning version 2.25.6

Sign for Flattement (Finger vibrato)

Hi, I'm in the process of re-setting suites from Pierre Danican-Philidors op.1. Philidor is one of the few composers who mark exactly where a flattement, i.e. a finger vibrato, should be played. He does this with a wavy line over the corresponding notes. This sign differs from "\prallprall".

Re: Fix Lilypond Beaming GSOC Project

I got it working on my Arch Linux after trial and error with ./configure. Here are the Arch Linux package names that translate to what Lilypond needs (I didnt include package names that I already had, so obviously there's Python, ghostscript, etc.): * dblatex (optional, configure script keeps

Re: No writable cache directories

On Fri, 2023-04-28 at 15:14 +, Werner LEMBERG wrote: > Creating font configuration... > Adding fontconfig configuration file: > /usr/local/share/lilypond/2.25.5/fonts/emmentaler-font.conf > > Fontconfig error: No writable cache directories Let's state the obvious candidate her

Re: Musings on our translated documentation build

On Wed, 2023-01-04 at 14:39 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: > Now, this works in our current setup, but it seems to me that there is > an easier way to achieve this with "native" Texinfo tools: Instead of > > @node Translated

LilyPond 2.25.4

We are happy to announce the release of LilyPond 2.25.4. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.1, the current stable release. Please refer

Re: Build binaries in CI?

On Mon, 2023-04-17 at 22:52 +0200, Jean Abou Samra wrote: > Hi, > Just a thought related to > https://gitlab.com/lilypond/lilypond/-/merge_requests/1950: maybe we > could add optional CI jobs running on CentOS 7 to compile Linux > official binaries + MinGW binaries ? Windows bin

LilyPond 2.25.3

We are happy to announce the release of LilyPond 2.25.3. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.1, the current stable release. Please refer

Re: Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project

something that will work with you. I am open to use Matrix/Element for messages, Jitsi Meet for video conferencing. I've never used IRC before, but since Lilypond has a developers IRC channel, I can spend some time learning how to use it. Using SMS or phone call may pose problems as my Week 5-6

Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project

Hi Carl, I'm CC'ing the developers mailing list, just to let you know. I would like to first ask you about your preferred mode of communication, if my project proposal is selected. That is, what modes of communication would you prefer for: * Real-time communication for mentor-mentee

Re: Musings on our translated documentation build

On Mon, 2023-03-13 at 22:20 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > 1. All @ref{Translated} become @ref{Origin}, but as far as I understand > >

Re: Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea

some ideas on how to approach rewriting `beaming-pattern.cc`. From my understanding of past GitLab issue discussions and Urs Liska's analysis at https://gitlab.com/lilypond/lilypond/uploads/a4eecb716f9b52ae90da814612ea00a9/beam-subdivisions.pdf, it seems that the `beatStructure`/`beatMoment

Re: Musings on our translated documentation build

On Sun, 2023-03-19 at 23:56 +0100, Federico Bruni wrote: > Actually I was curious to check the html output rather than the changes > in the source. > If it doesn't break working links, it's fine for me. In the parts I touched, it is almost generating identical HTML (except for the links to

Re: Differences in `web.html`

On Mon, 2023-03-20 at 14:34 +, Werner LEMBERG wrote: > Comparing > >   http://lilypond.org/web.html > > with a self-compiled > >   .../out-www/offline-root/Documentation/web/web.html > > I see the attached difference.  Is it an oversight that > `scripts/build/fix-docsize.sh` is not

Re: Musings on our translated documentation build

Hi all, sorry for dropping the ball on this topic... On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: > 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 > &

Re: Lilypond for Apple Processor

On Sun, 2023-03-12 at 22:16 +, Werner LEMBERG wrote: > > Well, what I was trying to say, and what I probably should have > > made more explicit, is that "official" binaries from our side > > require a bit of work.  In fact, the support in our scripts needs > > to be dealt with in advance, so

  1   2   3   4   5   6   7   8   9   10   >