[12:55:01] https://en.wikisource.org/w/index.php?title=The_Entertainer&action=submit [12:55:09] The score doesn't compile... [12:55:24] Which version of lilypond/GUILE are currently being used? [12:57:30] Hi - [12:57:48] ShakespeareFan00: lilypond 2.22.0, according to https://en.wikisource.org/wiki/Special:Version [12:58:17] edgar-rft: You mentioned something about lilypond needing a different guile version? [12:59:46] The question is: what lilypond version and what guile version does wikimedia currently use? we get unexpected errors that we do *not* get with current stand-alone lilypond versions. [13:00:26] edgar-rft: please file tasks with examples so lego can look at the issues [13:01:02] edgar-rft: The place to file a support ticket would be Wikimedia Phabriactor. [13:01:25] https://phabricator.wikimedia.org/ [13:01:40] We've potentially identified a concern. [13:02:43] edgar-rft: The other erorrs I get with lilypond on Wikimedia are to do with the environment being a 'safe' one [13:03:10] and are to some extent expected by the sandboxed nature of the version mediawiki uses [13:03:56] The version in use at Mediawiki doesn't permit \include currently so that it's less easy to introduce arbitary code. [13:04:18] https://en.wikisource.org/w/index.php?title=The_Entertainer&action=submit looks fine in preview for me [13:05:26] It only looks fine because I replaced the lines in, https://en.wikisource.org/w/index.php?title=The_Entertainer&oldid=11612112 [13:05:36] The Midi generated won't be correct. [13:05:51] Ah [13:06:25] Technically the MIDI section could be dropped as I was using the audio_override [13:06:42] but that would only solve the issue for this particular use case [13:07:19] @edgar-rft: You'd been able to find a more appropriate repair for the line in question? [13:09:42] The repair suggested was replacing '#unfold-repeats' with '{ #unfold-repeats #'(volta) }' in lines 308 and 310 [13:10:01] because the volta's need to unfolded in the generated midi output. [13:10:43] The relevant documentation being -https://lilypond.org/doc/v2.22/Documentation/notation/available-music-functions [13:14:27] The reason was that lilypond's definition of unfold-repeats has changed in some version between 2.11 (where the original score was written) and 2.22 (current), it's *not* a Wikimedia bug. [13:15:58] edgar-rft :- [13:16:00] \context Staff = "up" { \unfoldRepeats ( #'volta ) \top } [13:16:03] also worked. [13:16:10] In that it now renders :) [13:17:02] I've found that sometimes you need to use { } around things to ensure type conversions [13:17:54] (I've applied the same logic to that when (LA)TeX math formatting was misrendering. adding { } braces typically solved things [13:18:24] Also converted back to calling the function directly... [13:19:14] edgar-rft: The reason i asked elsehwere about a linter, was that such tools can typically locate 'deprecated' constructions :) [13:19:30] The wikimedia one for example warns about old HTML tags for example [13:25:18] Lilipond syntax *is* a mess because the syntax of musical notation is not clearly defined. Musical notation intentionally leaves *much* room for interpretation, every item in music notation has minimum seleral possible interpretations. That's why lilypond's Scheme code can change *all* lilypond syntax interpretations. How would you want to parse that with a computer program? [13:26:07] You've not tried to debug wikitext quirks :rofl: [13:37:52] xDD [13:39:46] indeed, we probably only see wikitext as 'simpler' due to being used to it [13:41:35] Parsing human text with a computer is even more difficult, everybody knows what ridiculous crap Google Translator produces :-) [13:42:03] Google translate is funny [13:47:48] Understand not the order of languages certain it does? [13:47:52] :rofl: [13:48:13] Babelfish's translation of some documentation ended up sounding like Yoda at one point. [14:38:21] @Platonides: That said getting a formal spec for Wikitext 2.0 is ongoing I hear [14:41:01] let's define a formal syntax spec for human language first :-) [14:46:50] it's basically impossible to formalize Parser.php [14:48:09] Parsoid was written so it might be possible in the future, but last I checked the plans for a formal spec outside of the Parsoid testcases were dropped [16:17:11] edgar-rft: Wikitext is the mediawiki syntax for things like lists (*,#,:) and tables ({| ,|,|-,|}) and so on [16:17:42] AntiComposite: HTML by comparison IS well defined [16:18:07] well yes, because they wrote the standard before they wrote the parser [16:18:14] it also builds on XML [16:18:50] One of my perrenial rants is the quriks of doLevels and where P tags get inserted [16:19:21] And there not (currently) being a way to mark a list item as being multi paragraph [16:19:59] Currently trying to do multi-paragraph list items causes some otherwise logical bits of code to break [16:20:13] *logical to a contributor [16:20:33] There is also the

wrapping quirk [16:21:21] where an attempt to wrap certain syntax causes a premature termination of the DIV [16:21:24] tag. [16:22:25]

\n<\div> being something that can prematurely end a DIV [16:24:14] AntiComposite: there are many quirks in html parsing [16:24:24] see all the odd things specified in html5 [16:24:52] oh sure [18:07:06] edgar-rft: were you able to figure it out? [18:07:32] We're using lilypond/guile from Debian buster backports [18:08:22] Guile 1.8 I think. [18:11:19] legoktm: thanks, that's lilypond 2.18 and guile 1.8 according to -> https://packages.debian.org/buster/lilypond [18:12:01] No it's 2.22, you want https://packages.debian.org/buster-backports/lilypond [18:14:26] thanx again, I only wanted to make sure that we use the same lilypond version so we might not report wikimedia bugs that in real are lilypond bugs :-) [18:16:07] note this may need a double upgrade when you go from buster to bullseye [18:17:00] https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#libgc1 [18:21:00] Most problems we found so far were that the wikimedia scores often were written for ten year old lilypond versions and the lilypond syntax has changed since then. These are *not* bugs in the wikimedia software. I'm not a lilypond developer but I write lilypond scores since more that ten years and read the lilypond devel lists. [18:26:19] That's good to hear, kind of. I would've hoped the lilypond syntax was more stable. [18:26:42] Platonides: luckily it's all containerized now, so fresh installs every time :) [18:31:12] :) [18:31:23] I'm currently rebuilding containers in bullseye [18:31:44] precisely [20:45:58] Change on 12meta.wikimedia.org a page Tech was modified, changed by 91.186.233.149 link https://meta.wikimedia.org/w/index.php?diff=21921542 edit summary: [+20] /* ن */ new section [22:10:44] Change on 12meta.wikimedia.org a page Tech was modified, changed by Abdullah08tl07 link https://meta.wikimedia.org/w/index.php?diff=21921743 edit summary: [+350] /* Journey Through Time */ new section