Re: L-R reversed mensural flag

2022-06-14 Thread Jean Abou Samra




Le 15/06/2022 à 05:53, Adam M. Griggs a écrit :

Hello list,

Just a quick request today, if I may. What I'd like is a stem-down 
fusa (mensural-style quaver or eighth-note) with its flag extending to 
the right instead of the left. A mirror image of the regular engraving.


I can get close by overriding the flag back into standard style but I 
want to retain the mensural shape, so that isn't ideal.


Thank you!



Something like this?

\version "2.22.2"

\new MensuralStaff {
  \override Flag.stencil =
    #(grob-transformer
  'stencil
  (lambda (grob original)
    (ly:stencil-scale original -1 1)))
  c''8
}


Best,
Jean




Re: Exited with return code -1073741819

2022-06-14 Thread Jean Abou Samra

Le 15/06/2022 à 06:10, Ahanu Banerjee a écrit :

Hi, has an issue been created for this problem? I don't see one in gitlab.



https://gitlab.com/lilypond/lilypond/-/issues/6361



Any progress in identifying the cause?



It happens that yes, but I would like to remind that everyone in this
project is a volunteer and thus you shouldn't expect fixes within days.
2.23 is a unstable release series after all. If things do not work,
please downgrade to 2.22.

Thanks,
Jean




Re: Exited with return code -1073741819

2022-06-14 Thread Ahanu Banerjee
Hi, has an issue been created for this problem? I don't see one in gitlab.
Any progress in identifying the cause?

Thanks,

-Ahanu


On Fri, Jun 10, 2022 at 7:52 AM David Kastrup  wrote:

> Paul Hodges  writes:
>
> > From:   Paul Hodges 
> >
> > From: David Kastrup 
> > Try deleting
> >
> > C:/Program Files/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go
> >
> > which sounds like an outdated compilation cache (though I have no idea
> > why).
> >
> > That fixed it.
> >
> > Actually, it fixed the compiled cache error, but I still have
> >
> >
> >
> > ERROR: In procedure apply-smob/1:
> > Wrong number of arguments to #
> > Exited with return code 1.
> >
> > The reason I didn't realise before is that the run that I had done
> > after deleting the cache  spent a long time twiddling its thumbs with
> > Frescobaldi's progress bar at 100% before giving the -1073741819
> > error.  It would appear that the -1073741819 error was triggered
> > before the code giving this boot-closure error.
>
> Ok, it was worth a try.  With a mismatch of that precompiled file (for
> whatever reason) to the version of Guile, this would have been a
> possible cause for the problem.
>
> --
> David Kastrup
>


Re: L-R reversed mensural flag

2022-06-14 Thread Andrew Bernard
I've been away from LilyPond for a few years but my work uses custom 
flags which you can set. You can describe any path and make it for the 
flag. I don't have my example on hand just now, but fear not, this can 
easily be achieved. I'm sure the others will give more detail.


Andrew


Adam M. Griggs wrote on 15/06/2022 1:53 PM:
Just a quick request today, if I may. What I'd like is a stem-down 
fusa (mensural-style quaver or eighth-note) with its flag extending to 
the right instead of the left. A mirror image of the regular engraving.





L-R reversed mensural flag

2022-06-14 Thread Adam M. Griggs
Hello list,

Just a quick request today, if I may. What I'd like is a stem-down fusa
(mensural-style quaver or eighth-note) with its flag extending to the right
instead of the left. A mirror image of the regular engraving.

I can get close by overriding the flag back into standard style but I want
to retain the mensural shape, so that isn't ideal.

Thank you!


Re: UTF-8 characters in filenames with Lilypond 2.23

2022-06-14 Thread Jonas Hahnfeld via LilyPond user discussion
On Wed, 2022-05-25 at 13:24 -0600, David F. wrote:
> 
> > On May 25, 2022, at 11:21 AM, Jonas Hahnfeld  wrote:
> > 
> > On Sat, 2022-05-21 at 15:20 -0600, David F. wrote:
> > > System: Intel-based macOS
> > > 
> > > I make extensive use of UTF-8 characters in the filenames of my Lilypond 
> > > files.  This works in Lilypond up through version 2.22.  But Lilypond 
> > > 2.23 cannot handle UTF-8 characters in filenames.
> > > 
> > > Filename: tést.ly
> > > 
> > > \version "2.22"
> > > 
> > > { c' }
> > > 
> > > 
> > > Under v2.22, this file complies without problem.  With 2.23 (including 
> > > the just release 2.23.9) I get the following error:
> > > 
> > > Starting lilypond 2.23.9 [tést.ly]...
> > > warning: cannot find file: `/Users/david/Projects/Lily Scratch/te??st.ly'
> > > fatal error: failed files: "/Users/david/Projects/Lily Scratch/te??st.ly"
> > > Exited with return code 1.
> > > 
> > > I thought that this problem had already been reported, but I can’t find 
> > > any mention of it now.  So I’m reporting it.
> > > 
> > > David F.
> > 
> > Hi David,
> > 
> > I can indeed reproduce this on macOS, which I think is the critical
> > piece of information here. It would just be too boring if all operating
> > systems agreed on how to handle filenames with special characters... In
> > this case, it might also have to do with the file system because if I
> > do 'ls', I also get question marks (but this might also be because I'm
> > ssh-ing from Linux...)

No, it didn't have to do with the file system, the scripts for building
the binaries were just missing an environment variables so that libintl
was properly found on macOS, which is apparently required for some
locale settings. The problem should be fixed in the next release, see
https://gitlab.com/lilypond/lilypond/-/merge_requests/1410
(Actually, this will also fix localized messages on macOS which didn't
work so far.)

> 
> Thanks for looking into this Jonas.  As I said in my original message 
> Lilypond up to v2.22 handles UTF characters just fine.

LilyPond 2.22.x used Guile 1.8 with binaries produced by a different
system (called GUB).

Jonas


signature.asc
Description: This is a digitally signed message part


Re: Changes to dynamics in 2.23

2022-06-14 Thread Jean Abou Samra

Hi,

Le 14/06/2022 à 02:50, Edizioni Migliori a écrit :

Hi,

Somewhere between 2.23.7 and 2.23.9, the Feta rendering of "mf" and 
"mp" has changed, with increased spacing between the letters. It looks 
nice, but there is no announcement of the change in the documentation. 
Is there a reason for this?



Actually, it was a bug fix. The kerning was intendd like that, but 
broken. See


https://gitlab.com/lilypond/lilypond/-/merge_requests/1353



Also, with the new spacing, it would be great if the tail of the "m" 
had a steeper curve to match the slope of the "p"... Is there a place 
to submit such requests?



See https://lilypond.org/bug-reports.html

(This may be a little misworded because the bug-lilypond list is for 
feature requests as well as bugs.)


Your input is appreciated.

Best,
Jean