> for rast.ly
>
> \include "hel-arabic.ly"
> \version "2.25.13"
> \relative {
> \key c \rast
> c' d edb f | g a bdb c | eb a g f | edb d c
> }
>
> Tmust give rast.pdf , But that's not the case
Of course not. You are using the current development version without
my fix. Again: please
> \include "hel_arabic.ly"
It's `hel-arabic.ly`, not `hel_arabic.ly`.
Werner
for rast.ly
\include "hel-arabic.ly"
\version "2.25.13"
\relative {
\key c \rast
c' d edb f | g a bdb c | eb a g f | edb d c
}
Tmust give rast.pdf , But that's not the case
rast.pdf
Description: Adobe PDF document
I installed lilypond-2.23.6-1 ,lilypond-2.24.3 and lilypond-2.25.13:
for each version I do : LilyPond rast.ly
for the unstable version it's normal hel-arabic has been truncated.
I would like to point out that my initial version of hel-arabic.ly that I am
using is functional.
I tested them
> \include "hel-arabic.ly"
> \version "2.23.3"
> \relative {
> \key c \rast
> c' d edb f | g a bdb c | eb a g f | edb d c
> }
You must have done something wrong; I've just downloaded the 2.24.3
binary bundle for GNU/Linux, and this code compiles fine – this means
that it works for
hello again
\include "hel_arabic_initial.ly"
\relative {
\key c \rast
c' d edb f | g a bdb c | eb a g f | edb d c
}
This should ensure full backward compatibility if you process your old
files with `convert-ly`.
Which file?
This file: \include "hel_arabic.ly" \relative { \key c \rast
I have this :
lilypond rast.ly
=>
GNU LilyPond 2.25.13 (running Guile 3.0)
Traitement de « rast.ly »
Analyse...
rast.ly:1:10: Erreur : fichier non trouvé : « hel_arabic.ly »
(chemin de recherche : «
hello again
I did some tests on version 2.24.3, 2.21.0-1 , 2.23.6-1
it doesn't work either.
hassan
lilypond rast.ly =>
GNU LilyPond 2.25.13 (running Guile 3.0)
Traitement de « rast.ly »
Analyse...
rast.ly:5:8: Erreur : « edb » n'est pas un nom de note
c' d
edb f | g a bdb c | eb a g f | edb d c
rast.ly:5:20: Erreur : « bdb » n'est pas un nom de note
c' d edb f | g a
> > This should ensure full backward compatibility if you process your
> > old files with `convert-ly`.
>
> Which file?
Any input file that uses `hel-arabic.ly`.
Example:
```
\version "2.24.0"
\include "hel-arabic.ly"
\relative {
\key c \rast
c' d edb f | g a bdb c | eb a g f | edb d c
> I did some tests on version 2.24.3, 2.21.0-1 , 2.23.6-1
>
> it doesn't work either.
What *exactly* did you do?
Werner
Hello again
In fact it no longer works, I gave the operational version of hel-arabic.ly and
by trying
to make hel-arabic.ly dependent on arabic.ly without consulting me,
you screwed up the hel-arabic.ly file. I can still repair the damage
if you give me the opportunity to do that.Indeed edb
On Thu, 7 Mar 2024, 14:24 , wrote:
>
> \include "hel-arabic.ly"
> \relative {
> \key do \rast
>
Shouldn't this be
\key c \rast
?
c' d edb f | g a bdb c | eb a g f | edb d c
> }
>
> => rast1.png
>
>
> Hassan
>
Neil
>
> In fact it no longer works, I gave the operational version of
> hel-arabic.ly and by trying to make hel-arabic.ly dependent on
> arabic.ly without consulting me, you screwed up the hel-arabic.ly
> file. I can still repair the damage if you give me the opportunity
> to do that. Indeed edb and
>> [...] Indeed edb and sdb are no longer recognized
>
> It's not screwed up at all, however, current LilyPond is not
> backward compatible. I'm already working on a patch.
Please check
https://gitlab.com/lilypond/lilypond/-/merge_requests/2268
This should ensure full backward
On 2024-03-07 09:24, hassan.elfat...@free.fr wrote:
by trying to make hel-arabic.ly dependent on arabic.ly without consulting me,
you screwed up the hel-arabic.ly file.
Neighbor,
1. You contributed to an open-source project. Proposed
changes are posted for public review. GitLab sends
16 matches
Mail list logo
