User talk:Jean Abou Samra

Test of email notifications

This is a test. Jean Abou Samra Test Account (talk) 02:46, 2 November 2025 (UTC)

Another test. Jean Abou Samra Test Account (talk) 03:04, 2 November 2025 (UTC)

Third test. Jean Abou Samra Test Account (talk) 03:05, 2 November 2025 (UTC)

Reply test. Jean Abou Samra (talk) 03:05, 2 November 2025 (UTC)

Yet another test. Jean Abou Samra Test Account (talk) 03:14, 2 November 2025 (UTC)

Default stylesheet for the Wiki

Jean,

you've recently removed paper indentation settings from Rest styles, arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- Lemzwerg (talk) 16:51, 23 November 2025 (UTC)

I'm surprised. This page of the contributor's guide implies indent = 0 is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… Jean Abou Samra (talk) 17:13, 23 November 2025 (UTC)

I took the style settings used on the wiki right from the usage manual in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… Jean Abou Samra (talk) 17:15, 23 November 2025 (UTC)

D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)

Sorry for the noise -- Lemzwerg (talk) 17:22, 23 November 2025 (UTC)

cropped SVG images

Jean, please have a look at the image in Custodes – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- Lemzwerg (talk) 10:40, 25 November 2025 (UTC)

Seems a bit overkill to me. I've added a simple workaround to that snippet. Jean Abou Samra (talk) 12:41, 25 November 2025 (UTC)

Nice, thanks! I didn't think of this simple fix. -- Lemzwerg (talk) 13:27, 25 November 2025 (UTC)

Some CSS code for <samp>

Jean, what do you think of adding something like the following

body { quotes: '‘' '’'; }
samp:before { content: open-quote; } 
samp:after  { content: close-quote; }

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code> in the Wiki and @code in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use @samp for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <samp>, which makelsr.pl converts to @samp. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter s is marked with <samp>. My suggestion: The letter ‘s’ is marked with <samp>.

An alternative would be to give <samp> the same appearance as <code>. -- Lemzwerg (talk) 17:15, 30 November 2025 (UTC)

Done. Thanks for providing the CSS code. Jean Abou Samra (talk) 15:28, 6 December 2025 (UTC)

Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add font-family: sans-serif; to both the samp:before and samp:after block.

[I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

Done. I don't know a better solution either. Jean Abou Samra (talk) 14:30, 8 December 2025 (UTC)

Thanks! -- Lemzwerg (talk) 13:48, 9 December 2025 (UTC)

Search issues

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet Using \arpeggioBracket to make divisi more visible cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- Lemzwerg (talk) 13:55, 9 December 2025 (UTC)

AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. Jean Abou Samra (talk) 14:13, 9 December 2025 (UTC)