Layout translations (bug #1476)

[Paul A. Rubin]

Bug #1476 deals with the intermittent problem of a user discovering that 
headings defined in layout files (such as "Theorem" or "Lemma" in the 
AMS stuff) manifest in English irrespective of the document language.
Am I correct that nobody is currently working on this?  If so, I have an 
idea for how to deal with it, although I may be overengineering the 
solution a bit.  My concept consists of:

1.  a database of terms that show up in layout files (presumably inside 
LaTeX commands/macros) and need translating;

2.  a web front end that allows volunteers to supply translations of 
those terms without having to edit layout/include files themselves 
(translations to be stored in a database);

3.  a set of layout/include "templates", which would be the original 
(English-language) files with the terms requiring translation flagged by 
metacharacters; and

4.  an application (hosted on a server, not inflicted on the user) that 
would apply the translations upon request and archive a zipped copy of 
the translated files someplace accessible (most likely, a download page 
on the wiki).

So a user who wants to use, say, the AMS classes in Flemish would look 
for translated AMS files on the wiki and, finding none, would go to a 
web page where s/he would select the classes and the language and 
request a translation.  Assuming all necessary terms had been translated 
previously by one of our many Flemish-speaking volunteers, the web app 
would (a) translate the files), (b) put them on the wiki (or wherever) 
with suitable text and links, and (c) pass the link to the user making 
the request.  If terms were missing, the web app would steer the user to 
the same page volunteers would see, which would list terms and solicit 
translations.

I envision the translations page showing terms in English and, where 
available, a second language of the user's choice (so if our 
Flemish-speaker is not sure what "Lemma" means in English, perhaps s/he 
can see the French, German or Dutch equivalent).  There would also need 
to be a provision for correcting terms that had already been translated 
but incorrectly (either directly in the web app, or a place on the wiki 
to express concerns).

All of this is actually stuff I can handle (unlike, say, anything in C++ 
or Python), so if this seems like a good solution (and nobody else is on 
the case), I'll undertake it as time permits.

Feedback?

/Paul