On a larger scale, the true solution would be to organize some kind of fairly precise set up in which volunteers could participate. I gave some thought to this idea lately, and realize there will be some touchy points. I thought of writing to Richard Stallman to launch such a project, but feel it might be good to shake out the ideas between ourselves first. Most probably that Linux International has some experience in the field already, or would like to orchestrate the volunteer work, maybe. Food for thought, in any case!
I guess we have to setup something early, somehow, that will help many possible contributors of the same language to interlock and avoid work duplication, and further be put in contact for solving together problems particular to their tongue (in most languages, there are many difficulties peculiar to translating technical English). My Swedish contributor acknowledged these difficulties, and I'm well aware of them for French.
This is surely not a technical issue, but we should manage so the effort of locale contributors be maximally useful, despite the national team layer interface between contributors and maintainers.
GNU needs some setup for coordinating language coordinators.
Localizing evolving GNU programs will surely become a permanent
and continuous activity in GNU, once started. The setup should be
minimally completed and tested before GNU gettext becomes an official
reality. The email address `gnu-translation@prep.ai.mit.edu'
has been setup for receiving offers from volunteers and general
email on these topics. This address reaches the GNU Translation
Project coordinator.
Go to the first, previous, next, last section, table of contents.