Re: Language selection code

[Simon Albrecht]

Hello everybody,

this is now <https://code.google.com/p/lilypond/issues/detail?id=4337>.
I will look into this again after the holidays – as a church musician I 
have other things to do in the meanwhile. :-)
Can anybody comment on the ‘proceeding’ section below? I’m not exactly 
sure there – especially with the syntax question. Is there any standard 
way to get an agreement on this? Make a survey on ly-user (which I 
started to work on already, but put on hold)? Propose a patch first and 
then discuss it on Rietveld?
Else I’ll try and cope with the CG on my own, which seems (perhaps 
unnecessarily) difficult…

Yours, Simon

Am 27.03.2015 um 00:43 schrieb Simon Albrecht:
> Hello,
>
> triggered by a discussion on -user I have begun to implement a new 
> \language command which in addition to setting the note names input 
> language also automatically translates the default text fields in 
> tagline and table of contents, or may be used for both tasks separately.
> By now, with help from David N. and Harm, I made a one-file working 
> version of this feature (see attachment) and would like to bring this 
> feature into the code base. There are many comments inline explaining 
> the design and coding.
> I could not manage to combine a convincing new interface with full 
> backwards compatibility, partly because optional arguments were not 
> working as expected. As a result, the previous \language "english" 
> syntax would have to be updated into the equivalent \language 
> input.english – which I estimate to be feasible using convert-ly, 
> although I have no knowledge of python.
> How to proceed further? I think it unlikely that I am soon going to 
> make contributions regularly, but I think it would be good to have a 
> mentor, as suggested by the CG. I work with ubuntu and have also 
> started using git, so I might be able to incorporate these changes in 
> the code base and propose a patch myself, though I’m not much into it 
> yet and will need help in addition to the CG explanations…
> So the roadmap would include
> – discussing design and coding (?)
> – placing the code in the respective .ly and .scm files where it belongs
> – modifying the documentation
> – and adding a convert-ly rule.
>
> I hope that I can thus contribute something of use.
>
> Yours,
> Simon
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel