libgtop string freeze breakage

[Christian Rose <menthos gnome org>]

There has been an unannounced string freeze breakage in the string
frozen libgtop gnome-2-4 branch.

This seems to be the commit in lib/read.c, lib/read_data.c, and
lib/write.c that caused the three unannounced string changes:

----------------------------
1.16 <hadess> 2003-10-20 17:33
2003-10-20 Bastien Nocera <hadess@hadess.net>

* lib/read.c: (glibtop_read_l):
* lib/read_data.c: (glibtop_read_data_l):
* lib/write.c: (glibtop_write_l): apply patch for ngettext support
by Christian Neumair <chris@gnome-de.org>
----------------------------

These are the changes:
http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvs/gnome&subdir=libgtop/lib&command=DIFF_FRAMESET&file=read.c&rev2=1.16&rev1=1.15
http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvs/gnome&subdir=libgtop/lib&command=DIFF_FRAMESET&file=read_data.c&rev2=1.15&rev1=1.14
http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvs/gnome&subdir=libgtop/lib&command=DIFF_FRAMESET&file=write.c&rev2=1.14&rev1=1.13

Communication with translators regarding string changes at supposedly
frozen times is very important. This is also true even for bug fixes. If
you feel the need to break a freeze, follow the procedure outlined on
http://developer.gnome.org/dotplan/tasks.html#ApprovingFreezeBreaks to
get approval first, and please respect the freezes otherwise.

While this i18n bug fix should definately go into the non-frozen HEAD,
it's not clear that this should go into the string frozen gnome-2-4
branch. And even if it should, it shouldn't go into that branch without
notifying all translators.

I suggest this be reverted from the gnome-2-4 branch.


Christian