Re: Missing items to make Cairo ready

I am not at all convinced by these workarounds just to get Cairo a bit earlier and avoid walking the proper road to the clean solution (ie properly deprecating what we don't want to or cannot support). \postscript can be deprecated on other grounds, but we cannot really deprecate \epsfile

Re: [WISH] ‘smart’ punctuation for Lyrics

Le 30/12/2022 à 12:09, Simon Albrecht a écrit : Does that seem feasible Yes. Introduce an event and make Lyric_engraver read it and change the LyricText's text property. OpenPGP_signature Description: OpenPGP digital signature

Re: The hel-arabic.ly file story...

Le 28/12/2022 à 23:09, Werner LEMBERG a écrit : Exactly. We are *not* experts for music from Arabia/Turkey/Iran. We take what we get. It was our mistake then to not asking you or other guys for for an expert opinion – this time I've directly contacted Hassan for comments on your MR (hopefully

Re: Missing items to make Cairo ready

Le 29/12/2022 à 12:19, Jonas Hahnfeld a écrit : (FWIW I don't think it is a good idea to add features that will only work with Cairo. That sounds like a recipe for confusion to me, but I haven't yet had the time to properly look into the merge request...) I don't really see what the problem

Re: Missing items to make Cairo ready

Le 29/12/2022 à 11:53, Jonas Hahnfeld a écrit : On Thu, 2022-12-29 at 01:53 +0100, Jean Abou Samra wrote: Hi, I have just opened issues for the missing features of the Cairo backend that I am aware of. https://gitlab.com/lilypond/lilypond/-/issues/6500 https://gitlab.com/lilypond/lilypond

Missing items to make Cairo ready

Hi, I have just opened issues for the missing features of the Cairo backend that I am aware of. https://gitlab.com/lilypond/lilypond/-/issues/6500 https://gitlab.com/lilypond/lilypond/-/issues/6501 https://gitlab.com/lilypond/lilypond/-/issues/6502

Re: Duplicate SVG attribute

Le 25/12/2022 à 21:01, Paolo Prete a écrit : Thanks as always for your help, and also for the snippet you provided. You're right it's not usual to do that override twice for the same grob, and I'll update you with a concrete test-case in which the mentioned issue happens, so to see if we have

Re: (top-repl): suggestions for a demo?

Le 19/12/2022 à 01:59, Eduardo Ochs a écrit : Can anyone give me some examples of how to use the REPL to inspect some interesting variables and data structures? I am hoping to get something like a 5-line demo that I can use as a starting point... This is a late reply, but try this: \version

Re: LSR update?

Le 27/12/2022 à 18:06, Thomas Morley a écrit : True, though it's still valid code for 2.24... That makes a convert-ly rule even *more* important. If code that was previously valid now results in an error, at least you have a strong signal that you need to change something. If it compiles

Re: LSR update?

Le 27/12/2022 à 17:44, Thomas Morley a écrit : Here string-delete has one argument, a procedure. No; check the parentheses again. OpenPGP_signature Description: OpenPGP digital signature

Re: LSR update?

Le 27/12/2022 à 17:06, Thomas Morley a écrit : TODO guile message about `string-delete' adding-fingerings-or-string-numbers-or-stroke-fingerings-outside-of-the-music-code.ly Can be fixed by just inverting the arguments to string-delete. Surprisingly not. ? I took the snippet code

Re: LSR update?

Le 27/12/2022 à 16:55, Thomas Morley a écrit : I'd volunteer to update all lsr-snippets, though I surely need some help. Thanks! Especially for the snippets in (1) a) b) c) Your comments below are already helpful. Lateron, when LSR runs 2.24.0, we need to insert all snippets from

Re: LSR update?

Le 27/12/2022 à 15:06, Thomas Morley a écrit : Well, I started to update the snippets to 2.24.0 locally. Thank you for doing this. Do you intend to do them all, or do you need help? Some observations: (1) I'm stuck with three snippets: a) clip-systems.ly It's tagged "doc" I've no clue how

Re: Issue with deep-copy/map-some-music a tuplet

Le 25 déc. 2022 à 19:44, Paolo Prete a écrit :  On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra <[1]j...@abou-samra.fr> wrote: > Le 25 déc. 2022 à 19:10, Paolo Prete <[2]paolopr...@gmail.com> a écrit : > >  > BTW: >

Re: Issue with deep-copy/map-some-music a tuplet

> Le 25 déc. 2022 à 19:28, Thomas Morley a écrit : > > Am So., 25. Dez. 2022 um 18:18 Uhr schrieb Jean Abou Samra > : >> >> >> >>>> Le 25 déc. 2022 à 18:08, Paolo Prete a écrit : >>> >>>  >>> Hello Jean, >

Re: Issue with deep-copy/map-some-music a tuplet

> Le 25 déc. 2022 à 19:10, Paolo Prete a écrit : > >  > BTW: > > { > \override TupletBracket.bracket-visibility = ##f > \tuplet 3/2 { s8 s8 s8 } > } > > In 2.24.0 and previous versions this raises the "omitting tuplet bracket with > neither left nor right bound" warning, even if the

Re: Duplicate SVG attribute

Le 24/12/2022 à 15:38, Paolo Prete a écrit : Hello, I'm noting that the generated SVG of this...: { \once \override DynamicText.output-attributes.val = "x" \once \override DynamicText.output-attributes.val = "y" c'\mf } ... creates the following SVG tag, with a duplicate "val"

Re: Issue with deep-copy/map-some-music a tuplet

Le 25/12/2022 à 18:40, Paolo Prete a écrit : What error are you referring to, exactly? In case of my last snippet, which produces a tuplet of three skips, it compiles fine with previous versions. For me, \version "2.24.0" \tuplet 3/2 { s s s } gives (in 2.24.0) Interpreting music...

Re: lyric font change problem in ver 2.24.0

Le 25/12/2022 à 16:19, rajwn via Discussions on LilyPond development a écrit : I have problem regarding the Indian ascii fonts nudi 01 e in version 2.24.0, It doesnt change. This problem did not exist in version 2.22.0 Pease help. \version 2.24.0 #(ly:font-config-add-directory

Re: Issue with deep-copy/map-some-music a tuplet

> Le 25 déc. 2022 à 18:08, Paolo Prete a écrit : > >  > Hello Jean, > > I just verified that 2.25 doesn't accept a tuplet of skips ( i.e: \tuplet > 3/2 { s s s }, while all the previous versions do. > Is this really intended? No, as I wrote on a comment in the issue. It was not an

Re: Issue with deep-copy/map-some-music a tuplet

Le 25/12/2022 à 13:27, Jean Abou Samra a écrit : Le 25/12/2022 à 13:02, Paolo Prete a écrit : Hi Harm, I deleted that character, but the error remains (it doesn't compile on 2.25.0 but it compiles on all the previous versions). I tested it on Linux (Ubuntu 22.04) This is https

Re: Issue with deep-copy/map-some-music a tuplet

Le 25/12/2022 à 13:02, Paolo Prete a écrit : Hi Harm, I deleted that character, but the error remains (it doesn't compile on 2.25.0 but it compiles on all the previous versions). I tested it on Linux (Ubuntu 22.04) This is https://gitlab.com/lilypond/lilypond/-/issues/6482 Using

Re: PATCHES - Countdown to December 23

Le 22/12/2022 à 02:21, Colin Campbell a écrit : !1765 Add and use GLib regex interface - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1765 I should stress that the low-level parts of this patch need to mix three memory management models: Guile GC, C++ RAII, GLib

Re: Darwin 64 questions

Le 21/12/2022 à 22:29, Paolo Prete a écrit : 1) Why does the official LilyPond website not mention the GitLab unofficial builds anymore? Because they were done in order to provide 64-bit binaries as there were no official binaries of 2.22 for 64-bit macOS, which was a big problem. Now that

LSR update?

Hi Sebastiano and everyone, Now that 2.24.0 is released, we need to update LSR. Are you ready to make the update on the LSR server if we provide updated snippets? And under what form should the update be provided exactly? Thanks, Jean OpenPGP_signature Description: OpenPGP digital signature

Re: Figured bass bug in 2.23.82?

I have created an issue for this problem, https://gitlab.com/lilypond/lilypond/-/issues/6485 OpenPGP_signature Description: OpenPGP digital signature

Re: Prioriziting a directory

Le 18/12/2022 à 22:27, Jean Abou Samra a écrit : Le 18/12/2022 à 22:22, Abraham Lee a écrit :     By the way, is there already an issue for your request in the     LilyPond     tracker? No, I haven't submitted an issue about this. I've tolerated it for long enough that I just keep

Re: Thoughts on GLib regexes

Le 19/12/2022 à 15:14, Jean Abou Samra a écrit : Phooey, Sorry, I meant "Phew" here. OpenPGP_signature Description: OpenPGP digital signature

Re: Thoughts on GLib regexes

Phooey, I finally got this patch ready. https://gitlab.com/lilypond/lilypond/-/merge_requests/1765 OpenPGP_signature Description: OpenPGP digital signature

Re: Silent install of versions up to 2.23.6 for Windows

Le 19/12/2022 à 02:46, Paolo Prete a écrit : Hello, Is there a way to install versions up to 2.23.6-1 for Windows without the installer GUI interaction, with a command line that specifies the destination directory? AFAIK, this is possible for Darwin and Linux, but I can't find a way for

Re: Prioriziting a directory

Le 18/12/2022 à 22:22, Abraham Lee a écrit : By the way, is there already an issue for your request in the LilyPond tracker? No, I haven't submitted an issue about this. I've tolerated it for long enough that I just keep forgetting about it lol. Then I suggest to create one.

Re: Prioriziting a directory

Le 18/12/2022 à 22:03, Abraham Lee a écrit : Great questions, Jean. As a font creator (both text and music) and semi-power user, I've always hated that LilyPond only looks within its own data folder for music fonts. This has required me to duplicate all my fonts to the data directory of

Prioriziting a directory

Hi, Is there a way to express this in a Fontconfig configuration file: "If you find a matching font in this directory given as relative path, ignore other matches and choose that one"? Context: LilyPond (the GNU music typesetter) uses Fontconfig via Pango for finding text fonts, but also for

Re: LilyPond 2.24.0 released!

Le 15/12/2022 à 22:42, Jonas Hahnfeld via Info-lilypond a écrit : We are proud to announce the release of GNU LilyPond 2.24.0. Congrats everyone. Looking back at this release, I'm quite proud of what we achieved. Too bad that we can't go together to a restaurant to celebrate. And thank you

Re: LilyPond 2.24.0 released!

Le 16/12/2022 à 00:34, Hendursaga a écrit : Completely rewritten, you say? Hopefully that will make it easier to update the GNU Guix package for LilyPond! I don't think so. It was a rewrite of the infrastructure for making official releases, which mostly means compiling LilyPond's

Re: LilyPond 2.24.0 released!

Le 15/12/2022 à 23:15, Paul Scott a écrit : Any idea when there will be a Debian package?  (Not that I can't install it the way I have done the all the other 2.23.x versions). [Removing informational lists from the recipients. Please don't reply to info-lilypond and info-gnu, as these are

Re: Deprecation of instrumentCueName and instrument switch stuffs

Le 14/12/2022 à 21:39, Kieren MacMillan a écrit : You can *always* convert any use of \addInstrumentDefinition / \instrumentSwitch by turning \addInstrumentDefinition "x" #`((prop1 . val1) (prop2 . ,val2) ...) \instrumentSwitch "x" into x = { \set Staff.prop1 = #'val1 \set Staff.prop2 =

Re: Deprecation of instrumentCueName and instrument switch stuffs

Le 14/12/2022 à 21:00, Kieren MacMillan a écrit : Hi Jean, I totally agree that the \instrumentSwitch and \addInstrumentDefinition functions are useless. Just use variables. (Contrary to what its name suggests, \instrumentSwitch isn't directly related to Instrument_switch_engraver.) Please

Re: Deprecation of instrumentCueName and instrument switch stuffs

Le 13/12/2022 à 10:55, Xavier Scheuer a écrit : Hello, While replying to a query on the French-speaking list I realized that in the latest versions of LilyPond the instrumentCueName property was considered deprecated (as well as the engraver "Instrument_switch_engraver", the grob

Re: Deprecation of instrumentCueName and instrument switch stuffs

Just noting here that I will reply on the -devel list only. OpenPGP_signature Description: OpenPGP digital signature

Re: Testing binaries for 2.24.0 and release announcement

Le 14/12/2022 à 08:13, Jonas Hahnfeld a écrit : Yes, good idea. I will list them on GitLab and in the announcement email, I think the news item on lilypond.org should stay short. Agreed. Linux and Windows binaries seem to work fine in a smoke test on my machine, tested on two scores,

Re: Testing binaries for 2.24.0 and release announcement

Le 13/12/2022 à 22:44, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Please let me know what you think, I'm sorry that I forgot to share the text in advance. For the upcoming announcements, the text is very easy to adapt and I can also rebuild the tarball and binaries, if

Re: Strange behavior with unfound text font,Strange behavior with unfound text font

Le 12/12/2022 à 11:25, Werner LEMBERG a écrit : Hmm. Using FreeType 2.12.1 (self-compiled) and FontConfig 2.13.1 (as provided by my openSUSE box), running `lilypond --verbose` (from current git) on the above input gives ``` ... [nonexistent_bold_3.8662109375] Finding the ideal number of pages...

Re: Figured bass bug in 2.23.82?

Le 13/12/2022 à 07:12, Werner LEMBERG a écrit : *Theoretically*, this fixes the issue. I still don't understand how this MR helps. Say I am running 2.25.0 which has this fix, but I have 2.25.1 installed globally. It will predictably make 2.25.0 use the font files from 2.25.1 because they

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 23:33, Lukas-Fabian Moser a écrit : Yes, I kept a backup. I attach the .ly file and the ps file generated by 2.23.10. Thanks. I think this finishes to explain what is happening. In the big blob of data that embeds the emmentaler-11 font in the PS file, there is the string

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 23:22, Lukas-Fabian Moser a écrit : This solves the problem. OK, we're getting closer to the root of the problem. There is one more thing I'd like to know before I go to bed: can you restore a failing setup (I hope you kept a backup of the fonts in ~/.local? ...) and send

Re: Figured bass bug in 2.23.82?, Re: Figured bass bug in 2.23.82?, Re: Figured bass bug in 2.23.82?,Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 23:02, Werner LEMBERG a écrit : Masamichi-san, can you advise a solution? Would it be possible and would make it sense to add a directory specifier to `00-lilypond-fonts.conf`? I didn't find a way to do it in the configuration file directly, [...] What about adding ```

Re: Figured bass bug in 2.23.82?

Ha: [... ... ...] (utf-8-string "emmentaler-11 3.9453125" "6" (translate-stencil (0.0 . 0.0) (glyph-string # "Emmentaler-11" 3.9443359375 #f ((0.785296062992126 (0.0 . 1.1225612496924213) 0.0 0.0 "six")) "/home/lukas/.local/share/fonts/emmentaler-11.otf" <<<== Whoops again ... [... ...

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 22:43, Jean Abou Samra a écrit : Le 12/12/2022 à 22:33, Lukas-Fabian Moser a écrit : For me, \version "2.23.82" \markup $(markup-lambda (layout props x) (markup?)    (let ((stil (interpret-markup layout props x))) (pretty-print (ly:stencil-expr stil) (current-

Re: Figured bass bug in 2.23.82?

Ah, another question, Lukas: what does the "locale" command give you? Call me paranoid, but the accidental characters are obviously non-ASCII, so the Unicode handling might go wrong somewhere. OpenPGP_signature Description: OpenPGP digital signature

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 22:33, Lukas-Fabian Moser a écrit : Am 12.12.22 um 01:36 schrieb Jean Abou Samra: Le 12/12/2022 à 01:20, Jean Abou Samra a écrit : Werner will know about this better than me, but I am still curious. What does this give you? \version "2.23.82" #(ly:message &qu

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 22:35, Lukas-Fabian Moser a écrit : I would very strongly suspect 2.23.10 with https://gitlab.com/lilypond/lilypond/-/merge_requests/1409 New data: The problem starts with 2.23.8, incidentally the same release that contain's Werner's modifications to bass figure glyph sizes.

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 22:11, Lukas-Fabian Moser a écrit : I'm sorry not to have been more prompt in my replies, as I'm still quite swamped. To my knowledge, I have no globally installed lilypond. I don't remember installing one, and there is no globally available "lilypond" command on my system.

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 21:23, Jonas Hahnfeld a écrit : On Mon, 2022-12-12 at 01:36 +0100, Jean Abou Samra wrote: Note the path in /usr/share/fonts/lilypond, which is a folder provided by the lilypond package from my Fedora system This should be reported, it's not how Fedora is supposed to package

Re: Figured bass bug in 2.23.82?,Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 12:16, Werner LEMBERG a écrit : Masamichi-san, can you advise a solution? Would it be possible and would make it sense to add a directory specifier to `00-lilypond-fonts.conf`? I didn't find a way to do it in the configuration file directly, but using this:

Re: Figured bass bug in 2.23.82?,Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 17:44, Werner LEMBERG a écrit : I think https://gitlab.com/lilypond/lilypond/-/merge_requests/1758 will help in the future. Interesting, but for me, LilyPond 2.22 also reads from /usr/share. OpenPGP_signature Description: OpenPGP digital signature

Re: New CI runner

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. What version of macOS does this MacBook Air have? The main goal would be to find a

New CI runner

Am I understanding it correctly that the new runner provided by Karlin is a macOS machine? If so, what macOS version? (Context: planning a Frescobaldi release.) Thanks, Jean

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 01:36, Jean Abou Samra a écrit : Le 12/12/2022 à 01:20, Jean Abou Samra a écrit : Werner will know about this better than me, but I am still curious. What does this give you? \version "2.23.82" #(ly:message "~s" (ly:font-config-get-font-file "

Re: Figured bass bug in 2.23.82?

Le 12/12/2022 à 01:20, Jean Abou Samra a écrit : Werner will know about this better than me, but I am still curious. What does this give you? \version "2.23.82" #(ly:message "~s" (ly:font-config-get-font-file "emmentaler-20")) \markup "♯" So

Re: Figured bass bug in 2.23.82?

Le 11/12/2022 à 23:15, Lukas-Fabian Moser a écrit : Hi Werner, In any case, here are images again as attachments. They don't look like Werner's. Assuming that you run under GNU/Linux: Try to recreate all FontConfig files with `fc-cache --really-force` (probably as a superuser, too). I

Strange behavior with unfound text font

Folks, Coincidentally, at the same time as Lukas, I found another font-related glitch, although I don't think it's the same: \markup \override #'(font-name . "Nonexistent Bold") "ABC" With 2.22, this compiles without warning, and the resulting PDF contains the font "DejaVuSans-Bold"

Re: Figured bass bug in 2.23.82?

Le 11/12/2022 à 22:19, Lukas-Fabian Moser a écrit : Hi all, if I do \version "2.23.82" \new FiguredBass \figuremode {   <6> <_+> <_-> <_!> } I get: As soon as I do \version "2.23.82" \new FiguredBass \figuremode {   <6> <_+> <_-> <_!> <6!> } this becomes I'm pretty sure this is not how

ly:parser-include-string and include order...

Hi, This came up while debugging an issue in Frescobaldi's layout control options panel (I'm updating it to be compatible with LilyPond 2.23). $ ls included1.ily  included2.ily  include-order.ly $ cat include-order.ly \version "2.25.0" #(begin    (define (inc filename)

Re: Another user complaint about incompatible mark-like events

Le 03/12/2022 à 16:18, Dan Eble a écrit : On Dec 3, 2022, at 08:48, Jean Abou Samra wrote: It rejects the \sectionLabel that comes at the same time as an implicit \codaMark. Printing "Coda" instead of a coda mark is the defining use case for \sectionLabel. I'll try to take a c

Re: Plan for releasing 2.24.0

SGTM. Regarding this: Le 08/12/2022 à 20:08, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Until Sunday, December 11th: - merge https://gitlab.com/lilypond/lilypond/-/merge_requests/1710 and other release preparations (VERSION, convert-ly rule, something else?)

Re: `@lilycode` for highlighting LilyPond code snippets

> Another issue has come up in the discussion of MR 1753, namely whether > `@lilycode` should actually be named `@lilypond[code]`. There are > four proposals, and I would like to hear opinions. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/1753 > > (0) Two preliminaries. > > * The

Re: `@lilycode` for highlighting LilyPond code snippets

Le 06/12/2022 à 12:11, Jean Abou Samra a écrit : OK (and I'll be happy if we can have this for normal @code too, #6275). In this case, shouln't the MR be on Patch::needs_work for now? Alternatively, as you mentioned on #6275, we can wait for having switched to LuaTeX and do that in Lua

Re: `@lilycode` for highlighting LilyPond code snippets

Le 06/12/2022 à 07:47, Werner LEMBERG a écrit : Since the whole LilyPond code string is under the control of `lilypond-book`, I thought of inserting `@/` automatically. I would also insert `@tie{}` after `^[^ ] ` and before ` [^ ]$` to avoid a single character at the beginning or end of a line

Re: `@lilycode` for highlighting LilyPond code snippets

> Le 5 déc. 2022 à 21:06, Werner LEMBERG a écrit : > > I suggest to apply > `@lilycode` only if highlighting has some useful effects, which means > that in most cases it should be rather *not* used because inline code > is very short. AFAICT, the argument to inline @lilycode will always be a

Re: Another user complaint about incompatible mark-like events

Le 03/12/2022 à 18:00, Dan Eble a écrit : It's the same concern as from the beginning: I was reluctant to allow assigning multiple labels to the same moment in a performance because of known and unknown complications. For example, if a moment were marked with both 턌 and Part II, what should

Re: Another user complaint about incompatible mark-like events

Le 03/12/2022 à 16:18, Dan Eble a écrit : Printing "Coda" instead of a coda mark is the defining use case for \sectionLabel. But judging from how \repeat segno uses it and from its break-visibility, \codaMark is for a jump to the coda, not for the start of the coda itself, isn't it?

Another user complaint about incompatible mark-like events

I thought that with c7b238579b3d19c6ac2bc9e7160c803390f7bc07 as well as text marks, all meaningful cases of simultaneous mark-like events were covered, but there is a question on -user-fr about this case: \version "2.25.0" {   \repeat segno 2 {     \sectionLabel "Part I"     c'1     \break    

Re: Automated testing for users' LilyPond collections with new development versions

Le 28/11/2022 à 23:49, Karlin High a écrit : This message intrigued me: In it, Eric Benson reported a setup that allows testing new versions of LilyPond on a sizable body of work in a somewhat automated fashion. Now,

Re: LilyPond 2.23.82

Le 30/11/2022 à 23:13, Jean Abou Samra a écrit : The latter has length 0, the former has length 1/16. However, you didn't have this hack in the dynamics variables, so now your dynamics are all desynchronized. You need to remove an "s16" in both parts. One more thing: you may find t

Re: LilyPond 2.23.82

Le 30/11/2022 à 22:33, Jean Abou Samra a écrit : Le 30/11/2022 à 21:50, Galen Hazelwood a écrit : A minimized example will take some time. In the meantime, I'm attaching output from both 2.22 and 2.23.82, showing the difference. If this isn't useful, hold on, and I'll produce a minimized

Re: LilyPond 2.23.82

Le 30/11/2022 à 21:50, Galen Hazelwood a écrit : A minimized example will take some time. In the meantime, I'm attaching output from both 2.22 and 2.23.82, showing the difference. If this isn't useful, hold on, and I'll produce a minimized example when I'm free.

Re: LilyPond 2.23.82

Le 30/11/2022 à 19:33, Galen Hazelwood a écrit : Moved from 2.22.2 straight to this release. Everything seems to be fine, except that the final lines of both the 2-piano and full score of my project don't extend to the right edge of the page like they used to. It looks like "ragged-last" was

Thoughts on GLib regexes

Hi, As shown by https://gitlab.com/lilypond/lilypond/-/issues/6463, Guile regular expressions are a trap when it comes to Unicode. Under a non-Unicode locale, characters that can't be expressed in the locale encoding get converted to "?", both in the pattern and the search string, before

Re: Prefer luatex for documentation

Le 29/11/2022 à 07:29, Werner LEMBERG a écrit : In the long run, however, it would be good to have correctly sorted indices in the non-English manuals. AFAIK, and assuming that `texindex` is eventually capable of doing that, we will need UTF-8 locales for that, because virtually all programs,

Re: Prefer luatex for documentation

Le 28/11/2022 à 22:23, Jean Abou Samra a écrit : Le 28/11/2022 à 11:55, Werner LEMBERG a écrit : It is the doc autogeneration infrastructure that is not correctly writing the NR appendix files as UTF-8. It should be using set-port-encoding!. Will you submit a MR? https://gitlab.com/lilypond

Re: Prefer luatex for documentation

Le 28/11/2022 à 11:55, Werner LEMBERG a écrit : It is the doc autogeneration infrastructure that is not correctly writing the NR appendix files as UTF-8. It should be using set-port-encoding!. Will you submit a MR? https://gitlab.com/lilypond/lilypond/-/merge_requests/1747

Re: Prefer luatex for documentation

> Le 28 nov. 2022 à 09:18, Jean Abou Samra a écrit : > > I would like to understand why this happens. The French translation has > accents everywhere, and I never saw problems while reading it. Judging from > the image, the texi input itself output by lilypond-book

Re: Prefer luatex for documentation

> Le 28 nov. 2022 à 06:54, Werner LEMBERG a écrit : > >  >>> What I'm now working on are macros for `configure.ac` to find a >>> UTF-8 locale, which is important for the documentation generation >>> in the long run. [...] >> >> Phooey, that sounds complicated. I wonder if it would not

Re: Guile 2 vs. Guile 3

Le 26/11/2022 à 22:36, Eric Benson a écrit : In anticipation of the impending release of 2.24, I recently ported my Lilypond files from 2.22 to 2.23.81. I have about 100 lead sheets with lyrics, parameterized so that I can easily create them in different keys and in treble clef or bass clef.

Re: Prefer luatex for documentation

> Le 27 nov. 2022 à 19:40, Werner LEMBERG a écrit : > > What I'm now working on are macros for > `configure.ac` to find a UTF-8 locale, which is important for the > documentation generation in the long run. Alas, it is non-trivial to > write a portable solution, and I wasn't able to find

Re: Prefer luatex for documentation

Le 23/11/2022 à 22:52, Jean Abou Samra a écrit : Le 22/11/2022 à 22:57, Jean Abou Samra a écrit : OK, I'll do a one-core test. pdfTeX: real    29m37,883s user    28m28,375s sys    2m9,725s LuaTeX: real    30m42,967s user    29m14,973s sys    2m31,694s This is with a single core

Re: Download links

Hello, Le 27/11/2022 à 01:30, Paolo Prete a écrit : What seems to me possibly against link stability is that GitLab is a platform focused on the development of a project, and not specifically a repository of releases, although, of course it does include releases of the programs it hosts

Re: pygment regex question,Re: pygment regex question

Le 26/11/2022 à 16:16, Werner LEMBERG a écrit : OK, but where exactly is this documented? Is this missing, or am I blind? I think it's not written anywhere. If it is missing, could a Scheme expert please write some lines that I could incorporate into an MR? Nothing complicated: If a

Re: pygment regex question

Le 26/11/2022 à 11:32, Lukas-Fabian Moser a écrit : Hi Werner, In the NR, most such functions have its argument starting with `#`, for example ``` \ottava #-2 ``` Are there still cases where `#` is mandatory for numbers? Otherwise the documentation could be updated to remove all `#`.

Re: pygment regex question

Le 25/11/2022 à 20:28, Luca Fascione a écrit : On Fri, 25 Nov 2022, 18:11 Jean Abou Samra, wrote: What makes you think Pygments can’t do this? You can do (?<=\w+)\d+ Nothing but my not remembering lookaheads/lookbehinds, which I may argue aren't very commom constructs. In f

Re: pygment regex question

> Le 25 nov. 2022 à 18:03, Luca Fascione a écrit : > > It's not a validation, it's an anchor, it avoids it matching other numbers. > That's why the capture. If pygments was better designed it'll let you do > semi-context-sensitive > stuff like this, so you could say "numbers, but only if the

Re: pygment regex question,Re: pygment regex question

> Le 25 nov. 2022 à 17:54, Werner LEMBERG a écrit : > >  >> >>> Note that at the time this regex is active, numbers are taken care >>> of. >> >> Floats are, integers not. > > OK, but shouldn't this be rather > > ``` > (-?\d+|\\longa|\\breve)\.* > ``` > > then? Why not. If you want to

Re: pygment regex question

> Le 25 nov. 2022 à 17:52, Werner LEMBERG a écrit : > >  >> well -3 seems to be matching it, (say in a-3, I'm aware this is a >> fingering/articulation mark, not a duration). It appears to be an >> attempt to match a signed integer followed by zero or more dots. > > The thing is that the

Re: pygment regex question

 > Le 25 nov. 2022 à 17:16, Luca Fascione a écrit : > well -3 seems to be matching it, (say in a-3, I'm aware this is a > fingering/articulation mark, not a duration). > It appears to be an attempt to match a signed integer followed by zero or > more dots. > > It sucks that pygments regexes

Re: pygment regex question

Le 25/11/2022 à 14:23, Werner LEMBERG a écrit : Note that at the time this regex is active, numbers are taken care of. Floats are, integers not. Jean OpenPGP_signature Description: OpenPGP digital signature

Re: Guile potentially changing its GC a second time

> Le 24/11/2022 15:10 CET, Kevin Barry a écrit : > > > On Thu, Nov 24, 2022 at 02:58:16PM +0100, Jean Abou Samra wrote: > > What would be the difference with 'make doc'? > I was referring to the kind of scores used to test/reproduce the > heisenbug we had on Windows,

Re: Guile potentially changing its GC a second time

> Le 24/11/2022 14:05 CET, Kevin Barry a écrit : > > > On Thu, Nov 24, 2022 at 12:26:57PM +0100, Jean Abou Samra wrote: > > Le 24/11/2022 à 12:12, Kevin Barry a écrit : > > > > GC is definitely not the kind of thing where "passes the > > regtests&qu

Re: Guile potentially changing its GC a second time

Le 24/11/2022 à 12:12, Kevin Barry a écrit : To practically answer your question: I don't think there's much we can do: we are more or less at the mercy of the Guile project. Yup. I'm tempted to suggest we add some tests that might catch breaking changes to Guile's GC, but of course our

Re: BDWGC fix in 2.24?

Le 23/11/2022 à 23:47, Jonas Hahnfeld a écrit : I played a bit this week, and at least the crash for the score in https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html (which is finally a crash that I can reproduce) seems to be solved by the current tip of the release-8_2

<    1   2   3   4   5   6   7   8   9   10   >