A fork of Gnome-control-center with some tweaks
95aec817a6
2005-10-01 Rodney Dawes <dobey@novell.com> * gnome-wp-capplet.c (gnome_wp_add_image): Remove utf8 validate check (gnome_wp_props_wp_set): If the filename we have for the image is not valid utf8, convert it to utf8 before setting the key in gconf (gnome_wp_load_stuffs, gnome_wp_file_changed): Make sure that the filename is valid utf8 and the file exists with utf8 encoding, or fall back to filename encoding as specified by the user with glib's environment variables * gnome-wpitem.c (gnome_wp_item_new): Make sure that the name field is always utf8 for displaying to the user with the tree view * gnome-wp-xml.c (gnome_wp_xml_load_xml): Make sure that the filename is valid utf8 and the file exists with utf8 encoding, or fall back to filename encoding as specified by the user with glib's environment variables (gnome_wp_xml_save_list): If the filename is not valid utf8, then convert to utf8 for storing in the XML file Fixes #168604 |
||
|---|---|---|
| archiver | ||
| capplets | ||
| control-center | ||
| debian | ||
| gnome-settings-daemon | ||
| help | ||
| idl | ||
| libbackground | ||
| libwindow-settings | ||
| m4 | ||
| po | ||
| root-manager | ||
| schemas | ||
| typing-break | ||
| vfs-methods | ||
| .cvsignore | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| control-center.spec.in | ||
| COPYING | ||
| MAINTAINERS | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
| TODO.xml | ||
GNOME Control Center ==================== Requirements - intltool >= 0.21 gtk+ >= 2.3.0 gconf >= 2.0.0 libgnome >= 2.0.0 libgnomeui >= 2.0.0 libglade >= 2.0.0 libbonobo >= 2.0.0 libbonoboui >= 2.0.0 libgnomevfs >= 2.0.0 gnome-desktop >= 2.0.0 gnome-icon-theme >= 1.1.3 Installation - See the file 'INSTALL' How to report bugs - Bugs should be reported to the GNOME bug tracking system under the product control-center. It is available at http://bugzilla.gnome.org. In the report please include the following information - Operating system and version For Linux, version of the C library How to reproduce the bug if possible If the bug was a crash, include the exact text that was printed out A stacktrace where possible [see below] How to get a stack trace - If the crash is reproducible, it is possible to get a stack trace and attach it to the bug report. The following steps are used to obtain a stack trace - Run the program in gdb [the GNU debugger] or any other debugger ie. gdb gnome-calculator Start the program ie. (gdb) run Reproduce the crash and the program will exit to the gdb prompt Get the back trace ie. (gdb) bt Once you have the backtrace, copy and paste this either into the 'Comments' field or attach a file with it included. Patches - Patches should be submitted to bugzilla.gnome.org or emailed to one of the people listed in the MAINTAINERS file. If using bugzilla, attach the patch to a new bug report [or preferably, check to see if there is already a bug report that corresponds to your patch]. Bug reports containing patches should include the 'PATCH' keyword. Patches should be created using the unified diff form. ie. cvs diff -u file-to-be-patched.c > patch.diff