Re: New breathing mark

Thank you, Carl,
for me it is already a visual bug ;-), but I will take that to heart 
next time and rather contact lilypond-devel in such a case. Regarding 
the breath sign, I will start a request via gitlab.
Kind regards
Andreas

Am 12.11.2022 um 21:47 schrieb Carl Sorensen:
> On Sat, Nov 12, 2022 at 10:00 AM<[email protected]>  wrote:
>
> From: samarutuk<[email protected]>
>> To: bug-lilypond<[email protected]>
>> Cc:
>> Bcc:
>> Date: Sat, 12 Nov 2022 10:10:35 +0100
>> Subject: Breath mark style in LilyPond 2.23.80
>> Dear all,
>> when I tried version 2.23.80 for the first time yesterday, I was
>> absolutely shocked to see the new, very mundane comma as a breath mark
>> when rendering. I know that other notation programs also use the comma,
>> but for me the more caesura-like character used before was always a
>> reason to use Emmentaler/Feta, also and especially in MuseScore. The
>> normal text style comma, with its delicate tadpole continuation, goes
>> down much more easily in an opulent score with lyrics, staccato dots,
>> and other expressive marks. It's a misstep aesthetically and for
>> readability reasons, in my humble opinion. As a brass player, breath
>> marks are very important and actually occur in large numbers, so this
>> comma will really haunt me constantly.
>> However, since I don't expect you to undo it, then I do ask that you
>> still preserve the old style so that each Lilypondian can decide for
>> themselves whether to use the snappy comma or the Emmental original
>> breath mark (tm). If MuseScore (which I still use) adopts the modified
>> font, I may add the old breath mark there as well.
>> Sorry for the long text... and yes, I'm still shocked (and sticking with
>> older versions for now).
>> Kind regards
>> Andreas
>>
>>
> Andreas,
>
> This was an intentional change, implemented in
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1576
>
> At least two developers prefer the new breath mark.
>
> Perhaps you could request that the old mark be added back to Feta, and that
> code allowing one to use the old mark be developed.
>
> Since this was an intentional change, it's not a bug, so bug-lilypond is
> not the best place to discuss it.  Either lilypond-user or lilypond-devel
> would be a better place.
>
> Sincerely,
>
> Carl
> _______________________________________________
> bug-lilypond mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond