tarquin- I presume you have committed your changes to the unstable branch of the CVS code (the default). In that case, it will first have to be merged into the stable branch. This might take a while given that there's still some incomplete stuff (category code, new interlanguage links code) in the unstable branch. If Magnus doesn't finish these soon, I will probably remove them entirely. The code from the live wikis is currently updated to the stable branch regularly but manually. The next update will be in a few days. Before I do it, and bring all wikis to the latest version, I want to make some requested changes to the new features (see [[Wikipedia:Software updates]] on en:). If you want your code to go live with the next update cycle, you should commit it to stable immediately (but be sure it doesn't break anything). Just switch your working copy to stable, or check out a separate working copy from that branch, and commit it there. See http://www.loria.fr/~molli/cvs/doc/cvs_5.html for details. Regards, Erik

tarquin wrote: Someone copies the file into place on a test server, fixes the inevitable syntax errors, puts the fixed version into CVS, and copies the file onto the live server. No. Anyone with login access on pliny, but usually me. Since this whole process is much more difficult than it needs to be, I plan on replacing it all with an interface for editing the translations directly through the site, with a one-button "approve and install" for sysops. Hopefully that'll be up in the next few days. -- brion vibber (brion @ pobox.com)