Le 22/10/2022 à 16:45, Jean Abou Samra a écrit :
I'm going to create an issue for that.
https://gitlab.com/lilypond/lilypond/-/issues/6443
We are happy to announce the release of LilyPond 2.23.80. This is the
first release candidate towards the next stable version 2.24.0 expected
in December. Please test your scores with this version and report back
the experience as well as any problems you encounter. Please refer to
the Installing s
>> We could define a macro `@bscode`, to be used in `@warning` only. Add
>> the following to `common-macros.itely`
>>
>> ```
>> @macro bscode{TEXT}
>> @code{\\\TEXT\}
>> @end macro
>> ```
>
> Honestly, if there isn't a way to fix @warning globally, I think it
> is simpler just not to use it her
Le 22/10/2022 à 16:42, Werner LEMBERG a écrit :
We could define a macro `@bscode`, to be used in `@warning` only. Add
the following to `common-macros.itely`
```
@macro bscode{TEXT}
@code{\\\TEXT\}
@end macro
```
Honestly, if there isn't a way to fix @warning globally, I think it
is simpler
We have many issues related to ties and to slurs. Would anybody mind
creating two GitLab labels ~"Ties" and ~"Slurs" for these? It would ease
searching for defects in those specific areas.
Le 22/10/2022 à 14:21, Werner LEMBERG a écrit :
You just have to "escape" it, like in texidocs:
@code{\\textMark} et @code{\\textEndMark}
I'll prepare a MR later today for text.itely.
If I do that, the backslash does appear in HTML, but there are two
backslashes in the PDF.
We could define a
