Re: [Evolution] why use hex in config.xmldb?

I thought it might be something like that alright. How about fixing
libxml1 so it does the right thing? Still hex encoded strings is not
a bad solution for the meantime. Thanks for the explaination.


On Wed, Oct 24, 2001 at 01:02:43AM -0400, Jeffrey Stedfast wrote:
I had to make bonobo-conf hex encode string because we were saving UTF-8
strings. Unfortunately libxml1 does some whacked out shit with strings
you pass to it instead of just strduping them and leaving them alone.

Thus, for non use-ascii locales, config settings that had non us-ascii
chars in them broke horribly.

There were basically 2 ways to fix the problem... either:

1. Force the bonobo-conf to only allow UTF-8 strings (which'd make it a
royal pain in the ass for other projects to use since gnome is not based
on utf-8) and set the libxml1 doc's locale to UTF-8 and pray that it


2. hex encode the strings...

I was talking to Havoc the other day and it seems he has run into the
same problem in GConf which may be why GConf 1.0.5 (or whatever) broken
GtkHTML if it linked against GConf for many Debian users. (just a
theory, I could be 100% wrong here...I don't follow GConf development).


On Tue, 2001-10-23 at 23:27, Thomas O'Dowd wrote:
Hi all,

Just wondering why the strings in ~/evolution/config.xmldb are in hex?
This makes it harder to check/edit configuration, which is one of the
good things about xml. I know they used to just use plain text. Is there
a particular reason the strings are stored in hex now?

<entry name="source_url_0" type="string" value="6d626f783a2f686f6d652f746f6d2f4d61696c2f65766f626f78"/>


Thomas O'Dowd. - Nooping -
tom nooper com - Testing -

evolution maillist  -  evolution ximian com

Thomas O'Dowd. - Nooping -
tom nooper com - Testing -

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]