Re: [Evolution] why use hex in config.xmldb?
- From: Jeffrey Stedfast <fejj ximian com>
- To: "Thomas O'Dowd" <tom nooper com>
- Cc: evolution ximian com
- Subject: Re: [Evolution] why use hex in config.xmldb?
- Date: 24 Oct 2001 01:02:43 -0400
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
worked
or:
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).
Jeff
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?
Example:
<entry name="source_url_0" type="string" value="6d626f783a2f686f6d652f746f6d2f4d61696c2f65766f626f78"/>
Cheers,
Tom.
--
Thomas O'Dowd. - Nooping - http://nooper.com
tom nooper com - Testing - http://nooper.co.jp/labs
_______________________________________________
evolution maillist - evolution ximian com
http://lists.ximian.com/mailman/listinfo/evolution
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]