GNOME Bugzilla – Bug 747810
Fix the build with GLib >= 2.45
Last modified: 2015-04-14 09:15:36 UTC
The glib-compile-schemas tool has become more strict, and it's catching the mangling of gschema files that are getting translated via intltool by merging translations back into the XML. The resulting gschema file is not valid, and never has been, and it has caused bugs like dconf-editor showing random strings into the UI, instead of the correctly translated one. The proper fix is to not have intltool extract the strings from the gschema.xml file: gettext is perfectly capable of doing that by itself.
Created attachment 301497 [details] [review] Do not use intltool to translate GSettings schema There's no need to do that, and since intltool merges translations into the XML by default, it actively breaks the gschema format.
Review of attachment 301497 [details] [review]: Thanks for doing this! Much appreciated! So, is this needed for 3.16 or only 3.17? Feel free to commit. Note that gnome-3-16 is branched of. Thanks again.
(In reply to Jonas Danielsson from comment #2) > Thanks for doing this! Much appreciated! > So, is this needed for 3.16 or only 3.17? This is needed when compiling against current GLib master, so I think we can avoid backporting to the gnome-3-16 branch; I'd also avoid it because I'm not sure how well the tools we use for translations cope with that case.
Attachment 301497 [details] pushed as 3903262 - Do not use intltool to translate GSettings schema