gconf string breakage

[Christian Rose <menthos menthos com>]

I'm a bit confused -- gnome-i18n@gnome.org hasn't been informed about a
new gconf branch to use for gnome 2.0 development, and the one (HEAD)
that's listed for use as per the last gconf branch info sent to
translators at gnome-i18n@gnome.org (back in december 2000) has recently
had up to nine string changes or string additions:

----------------------------
revision 1.82
date: 2002/09/19 02:49:07;  author: hp;  state: Exp;  lines: +3 -3
2002-09-18  Havoc Pennington  <hp@pobox.com>

        Merge gconf-markup-hacking branch

        * tests/testbackend.c: add a test for backends

        * gconf/gconftool.c (extract_global_info): add more error
        checking, adding more error strings

        * gconf/gconf-schema.c (gconf_schema_validate): do some more
        validation with error strings that couldn't be added to stable
        branch

        * backends/xml-dir.c: fix quoting in error string

        * backends/xml-backend.c (resolve_address): fix quoting in error
        string

        * backends/markup-tree.c: make it work

        * backends/markup-backend.c: make it work

        * backends/Makefile.am (libgconfbackend_markup_la_SOURCES): add
        markup-backend.c
----------------------------

As the comment for gconf/gconf-schema.c talks about a stable branch, I
suspect there is some lack of communication about gconf branches, rather
than an intended gnome-2-0 string breakage (although the net effect is
still the same). It would be nice if someone could clear this issue up,
preferrably by sending the information about the correct branches to use
to the translators at gnome-i18n@gnome.org.


Thanks,
Christian