Hmm, including files, even things like italiano.ly currently gets disabled via -dsafe

I suppose we could manually include them in a preprocessing step if they're from a list of safe sources, or something like that.

It would be great!

The files "italiano.ly" and "gregorian.ly" (imho the most useful) are standard LilyPond files, so they shouldn't be a security problem.

Is anyone willing (and able) to include these files as explained by Bawolff please?

jeanluc.thiebaut wrote:

In the case of "italiano.ly",
this file contains only (useful lines) : \language "italiano"

The following code should work :

<score>
\language "italiano"
\relative do' {do4 mi sol do}
</score>

This is important for a good localisation of the Score extension. Other languages than English should be able to use their local notation. Thanks, Yann

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make available many medieval pieces.

rickard.pontus.olof.lind wrote:

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

If there is no separate feature request for gregorian.ly, please file one as it's a separate issue. See https://www.mediawiki.org/wiki/How_to_report_a_bug for general information. it It won't be high priority as per https://www.mediawiki.org/wiki/Bugzilla/Fields#Priority but providing patches speeds up the process.

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

rickard.pontus.olof.lind wrote:

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into the regular interpreter. Am I right? Then it should be a LilyPond feature request.

Lilypond feature requests must go to http://code.google.com/p/lilypond/issues/list instead.

(In reply to Rickard Lind from comment #10)

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into
the regular interpreter. Am I right? Then it should be a LilyPond feature
request.

I'm not sure, but it seems that this feature was incorporated in LilyPond in 2010: https://code.google.com/p/lilypond/issues/detail?id=903

This issue should be solved for a while then, but it is still present. How is it possible?

rickard.pontus.olof.lind wrote:

(In reply to Ayack from comment #12)

(In reply to Rickard Lind from comment #10)

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into
the regular interpreter. Am I right? Then it should be a LilyPond feature
request.

I'm not sure, but it seems that this feature was incorporated in LilyPond in
2010: https://code.google.com/p/lilypond/issues/detail?id=903

This issue should be solved for a while then, but it is still present. How
is it possible?

The code included with \include "italiano.ly" was apparently quite simple code unlike gregorian.ly and fixed with a new \lanugage command. This does not include what is in gregorian.ly. See: https://codereview.appspot.com/2699041/

(In reply to Rickard Lind from comment #13)

(In reply to Ayack from comment #12)

(In reply to Rickard Lind from comment #10)

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into
the regular interpreter. Am I right? Then it should be a LilyPond feature
request.

I'm not sure, but it seems that this feature was incorporated in LilyPond in
2010: https://code.google.com/p/lilypond/issues/detail?id=903

This issue should be solved for a while then, but it is still present. How
is it possible?

The code included with \include "italiano.ly" was apparently quite simple
code unlike gregorian.ly and fixed with a new \lanugage command. This does
not include what is in gregorian.ly. See:
https://codereview.appspot.com/2699041/

Maybe, but "italiano.ly" is not working either...

rickard.pontus.olof.lind wrote:

(In reply to Ayack from comment #14)

(In reply to Rickard Lind from comment #13)

(In reply to Ayack from comment #12)

(In reply to Rickard Lind from comment #10)

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into
the regular interpreter. Am I right? Then it should be a LilyPond feature
request.

I'm not sure, but it seems that this feature was incorporated in LilyPond in
2010: https://code.google.com/p/lilypond/issues/detail?id=903

This issue should be solved for a while then, but it is still present. How
is it possible?

The code included with \include "italiano.ly" was apparently quite simple
code unlike gregorian.ly and fixed with a new \lanugage command. This does
not include what is in gregorian.ly. See:
https://codereview.appspot.com/2699041/

Maybe, but "italiano.ly" is not working either...

Does \language "italiano" work?

(In reply to Rickard Lind from comment #15)

(In reply to Ayack from comment #14)

(In reply to Rickard Lind from comment #13)

(In reply to Ayack from comment #12)

(In reply to Rickard Lind from comment #10)

(In reply to comment #9)

(In reply to comment #7)

(In reply to comment #6)

(In reply to comment #5)

This is important for a good localisation of the Score extension. Other
languages than English should be able to use their local notation. Thanks,
Yann

Yes, and please do not forget "gregorian.ly" which would allow us to make
available many medieval pieces.

I think "gregorian.ly" should be High priority!

Its unlikely we are going to rewrite lillypond's safemode. Sorry.

Then it is a LilyPond issue to incorporate the features of gregorian.ly into
the regular interpreter. Am I right? Then it should be a LilyPond feature
request.

I'm not sure, but it seems that this feature was incorporated in LilyPond in
2010: https://code.google.com/p/lilypond/issues/detail?id=903

This issue should be solved for a while then, but it is still present. How
is it possible?

The code included with \include "italiano.ly" was apparently quite simple
code unlike gregorian.ly and fixed with a new \lanugage command. This does
not include what is in gregorian.ly. See:
https://codereview.appspot.com/2699041/

Maybe, but "italiano.ly" is not working either...

Does \language "italiano" work?

No. I tried:

<score>
\language "italiano"
{ do re mi fa sol la si }
</score>

which generated:

Impossible de compiler le fichier d’entrée LilyPond :

Processing `.../file.ly'
Parsing...
.../file.ly:13:0: error: syntax error, unexpected '{'

{ do re mi fa sol la si }
.../file.ly:22:24: error: syntax error, unexpected '}'

}error: failed files: ".../file.ly"

exited with status: 1

(Cf. https://fr.wikipedia.org/wiki/Utilisateur:Ayack/Brouillon/Score)

<score lang="italiano">
{ do re mi fa sol la si }
</score>

Doesn't work either.

jeanluc.thiebaut wrote:

"language" works when using raw mode :

<score raw vorbis>
\score {
<<
\language "italiano"
\relative do' { do re mib fad sol la sib do }

\layout { }
\midi {  }

}
</score>

Ok, so, if I have understood correctly, the bug is:

"Score should support the following languages in standard mode:
arabic.ly
catalan.ly
deutsch.ly
english.ly
espanol.ly
italiano.ly
nederlands.ly
norsk.ly
portugues.ly
suomi.ly
svenska.ly
vlaams.ly"

Change 401820 had a related patch set uploaded (by Phantom42; owner: Phantom42):
[mediawiki/extensions/Score@master] Add support for notes languages

https://gerrit.wikimedia.org/r/401820

Change 401820 merged by jenkins-bot:
[mediawiki/extensions/Score@master] Add support for notes languages

https://gerrit.wikimedia.org/r/401820

In T49604#3876541, @Phantom42 wrote:

Closing this as resolved because the patch is merged now. This is one more step in making this extension better support score writing in different languages!

Thanks @Phantom42! It's a major step for this extension. Is your patch adding support for "gregorian.ly" or "only" current languages?

Languages added by this change are:

arabic.ly
catalan.ly
deutsch.ly
english.ly
espanol.ly
italiano.ly
nederlands.ly
norsk.ly
portugues.ly
suomi.ly
svenska.ly
vlaams.ly

Languages can be switched by using note-language attribute, for example:

<score note-language="italiano">
...
</score>

Unluckily, this patch does not add "gregorian.ly" support, as it is not the language which is supported by \language statement.