To see Damned Lies in your own language, be sure to have Accept-Language properly set.

Smallprint for translators: make use of existing iso_639 translations for your language to save a lot of work; it's not easy to reuse it directly and completely because we've got teams which are not exactly per ISO 639 language code.

They provide a bunch of improvements over the old translation status pages, including:

• Support for Subversion — including external support for both CVS and Subversion, meaning we can also list stats for things like GnomeScan and XKeyboardConfig.
• Integrated documentation stats provide with side-by-side listing of documentation and user interface translation stats.
• Per-module pages which are excellent resource for module maintainers, giving them an overview of translation support for their modules, and notifying them of some common i18n problems like missing files from POTFILES.in, languages missing from po/LINGUAS or PO files not passing "msgfmt -c" check.
• Release pages suitable for general overview of GNOME translation work, so you can easily get the status of GNOME 2.18 translation work as it happens (percentage values go crazy because of broken modules and POT file regeneration, so guys—fix your modules!).
• Translation Teams pages which are to replace old static page, providing more details and pointers to starting a translation (such as Bugzilla and mailing list links). Teams can also translate more than one language.
• Faster updates are there as well: after initial run of couple of hours, each additional update is much faster, since Damned Lies tries hard not to update things which need no updating (like, if POT doesn't change, only recently uploaded PO files are updated). In a couple of days you should also expect to see fully integrated SVN commit hook giving you almost-real-time updates. :)
• Automatic String Freeze Monitoring (HAHA :) with emails to gnome-i18n list: no need for us to track nasty changes maintainers do with their string frozen modules. :)
• More potential is there as well: all data is stored in a database (using SQLObject, so any of Postgres, MySQL and SQLite are supported), so we can easily add graphs of language support going up. And it's written in Python with CheetahTemplates as the templating engine, allowing easier output changes (for example, I've added proof-of-concept XML output in 20 mins, after polishing, we'll have that as well).
• Lots of error checking, including mentioned ALL_LINGUAS/LINGUAS, "msgfmt -c", "intltool-update -m" checks, but a couple of others as well, hoping to help translators identify problems more quickly and easily.
• Lots of new bugs which are introduced with a lot of care, and waiting for you to report them using Bugzilla. And you can add your feature requests in l.g.o as well.
• And most important, hackergotchis for both maintainers and translation team coordinators: provide yours today!