Re: Issue 1635 in lilypond: clean up misleading warnings in website build

[lilypond]

Comment #22 on issue 1635 by address@hidden: clean up misleading  
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635

The idea of a single file containing the list of required files, had also  
occurred to me, and suggests a similar approach to issues 1004, 1050, 1441  
and 1556: storing a list of supported languages in a central file, to be  
included where required.  We could then have the option of passing a comma  
separated list of languages on the command line, to override the otherwise  
included by default list.  Combining the two ideas with the intent of 1556  
suggests an array with file names as keys and locations and language codes  
as values in the record.  The attraction for me is that it gets rid of the  
hard-coded for l in '','cs','de', etc structures sprinkled through the  
build.  Granted, the for .. do loop probably has to stay, but at least it  
would be something like for l in LANG_LIST do