Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-11 Thread Jean Abou Samra
Le 09/01/2023 à 19:02, Werner LEMBERG a écrit : Have a look at https://lilypond.org/doc/v2.24/Documentation/notation/font and check the example for `\figured-bass`, which is wrong. If I compile this with a current lilypond binary, I get correct output (see attached image). I also get thi

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Werner LEMBERG
>> Hmm. Just to be sure it makes probably sense to also check whether >> the Emmentaler OTFs are identical in the binary and documentation >> builds... > > How can I check for this? You disassemble the fonts with `ttx` from 'fonttools' and compare the created XML files. Thanks for the OTF, I've

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jean Abou Samra
Le 09/01/2023 à 22:52, Werner LEMBERG a écrit : It seems that with the versions of Pango/Fontconfig in this Docker image, the backslash character, which doesn't exist in Emmentaler, causes a fallback text font to be used, which obviously defeats the Emmentaler OTF feature that causes "9" and "\"

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jean Abou Samra
Le 09/01/2023 à 20:48, Jean Abou Samra a écrit : It seems that with the versions of Pango/Fontconfig in this Docker image, the backslash character, which doesn't exist in Emmentaler, causes a fallback text font to be used, which obviously defeats the Emmentaler OTF feature that causes "9" and "

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Werner LEMBERG
> It seems that with the versions of Pango/Fontconfig in this Docker > image, the backslash character, which doesn't exist in Emmentaler, > causes a fallback text font to be used, which obviously defeats the > Emmentaler OTF feature that causes "9" and "\" to be combined > specially. Hmm. Just

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jean Abou Samra
Le 09/01/2023 à 20:48, Jean Abou Samra a écrit : Le 09/01/2023 à 19:26, Jonas Hahnfeld a écrit : I build the documentation in a Docker container, steered by release/doc/build-doc.sh and documented in the CG. It is veeery unlikely that there is anything to this theory. Right. I did a quick te

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jean Abou Samra
Le 09/01/2023 à 19:26, Jonas Hahnfeld a écrit : I build the documentation in a Docker container, steered by release/doc/build-doc.sh and documented in the CG. It is veeery unlikely that there is anything to this theory. Right. I did a quick test with \markup $(markup-lambda (layout props ar

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jonas Hahnfeld via Discussions on LilyPond development
On Mon, 2023-01-09 at 19:19 +0100, Jean Abou Samra wrote: > Le 09/01/2023 à 19:02, Werner LEMBERG a écrit : > > Have a look at > > > >https://lilypond.org/doc/v2.24/Documentation/notation/font > > > > and check the example for `\figured-bass`, which is wrong. If I > > compile this with a cur

Re: Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Jean Abou Samra
Le 09/01/2023 à 19:02, Werner LEMBERG a écrit : Have a look at https://lilypond.org/doc/v2.24/Documentation/notation/font and check the example for `\figured-bass`, which is wrong. If I compile this with a current lilypond binary, I get correct output (see attached image). I also get this

Wrong `\figured-bass` markup rendering in documentation

2023-01-09 Thread Werner LEMBERG
Have a look at https://lilypond.org/doc/v2.24/Documentation/notation/font and check the example for `\figured-bass`, which is wrong. If I compile this with a current lilypond binary, I get correct output (see attached image). I also get this if I build the documentation by myself on my compu