my worry about the recent libxml change

[Darin Adler <darin eazel com>]

The current code in xml-i18n-tool, OAF, and Nautilus depends on the
following property: Text in XML files, localized strings that come from
gettext, file names, GTK widget labels, and other strings all use the same
character set (the local one for each locale, often Latin-1).

Adding code to libxml to properly handle character sets when reading and
writing XML will retroactively decide that existing files are in some
particular character set, when they are actually in a mix of character sets.

Making libxml DOM trees in memory always use UTF-8 will break all the code
that puts strings in and takes them out without doing any translation.

I don't see how to make a program that works compatibly with both the old
and new versions of libxml. I have no idea how to address this issue in the
code for the various packages.

I hope someone can prove with testing or coding or both that I am wrong, and
this change can be done compatibly.

    -- Darin