Okay, I have the fully translated Gnome 2.4. But what's it worth when there are a bunch of problems which make it look... well, less translated, and less usable.
One of them is that gnome-panel and nautilus do some crappy .desktop file handling — they strip off the modifier part of "locale" in .desktop files, and thereby, sr@Latn overrides sr translation if it's latter in the file, or vice versa if sr is latter. There's also similar problem in libgnome-desktop (part of module gnome-desktop), which, I believe, is easily solved.
The other is that Gtk+ has it's own Compose and XKB handling. It is great because it provides some stuff that is wonderful for working with both (at the same time) cyrillic and latin keyboard (like smart shortcut handling), but it sucks because one cannot just make XKB and Compose file modifications, and have it work.
Ah well, at least it works in uxterm :-)
I am working on fixing the first issue, and the fix for the other one should be trivial (just editting the corresponding file which contains all the compose combinations, probably the one derived from XFree86's en_US.UTF-8/Compose file. So, for the Serbian live Gnome CD Slobo is working on, all of these should be included, because we don't want people to report things that are known problems.
The second issue, while trivial to fix in terms of coding, is a bit politically charged. Unicode has decided not to include accented cyrillic letters in the basic glyph repository. It would be all fine if there was enough good software that could make use of "combining" characters as specified in Unicode. Alas, there isn't, so there's no way to type „long o“ which is one of the most used letters. What people usually do is to type „latin small letter o with circumflex“, and that does the job graphicaly. Since there are not even intentions to include cyrillic accented letter in Unicode in the future, this is atm the best solution possible.
Actually, I do use that in my Compose file, but it works only in X programs that don't do any sophisticated keyboard handling (meaning, Gtk+ and fellas don't work with it). The proper solution might be to fix Pango to render sequence <dead_circumflex>+<Cyrillic_o> the same as <dead_circumflex>+<o> (or, <o with circumflex>), but it's not going to happen anytime soon, either. Yet, if Pango can render right-to-left scripts, complicated compositing for Arabic, it sure can and should handle this. Perhaps, it's also just a thing of modifying a certain table in it's internals.
Okay, this was my first sane input in English, because I hope to have some non-Serbian speaking audience on these issues.