GNOME Bugzilla – Bug 706789
gschema will not be translated because of invalid gettext-domain
Last modified: 2013-08-26 13:30:47 UTC
org.gnome.clocks.gschema.xml.in has @GETTEXT_PACKAGE@ as the output variable for its domain name. However, it is not substituted with the proper domain, "gnome-clocks", in the build process. @GETTEXT_PACKAGE@ remains in org.gnome.clocks.gschema.xml. As a result, the strings in the schema file won't be translated. Here is org.gnome.clocks.gschema.xml: <?xml version="1.0" encoding="UTF-8"?> <schemalist> <schema path="/org/gnome/clocks/" id="org.gnome.clocks" gettext-domain="@GETTEXT_PACKAGE@"> (...snip...) </schema> </schemalist>
Created attachment 253107 [details] [review] Replace @GETTEXT_PACKAGE@ with actual package name This is just a quick fix. I think it's worth reforming the build scripts, but that would have a too large impact for imminent 3.10.
Created attachment 253115 [details] [review] Replace @GETTEXT_PACKAGE@ with actual package name Oops, the gschema files has other schemas. So, we should put the gettext-domain attribute in the <schemalist> element rather than each <schema> element.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. https://git.gnome.org/browse/gnome-clocks/commit/?id=46e23d1e5035cc5d7b10d3f9cd9888bd3e770cf2
Created attachment 253132 [details] [review] Move gettext-domain attr from schema to schemalist Thank you for fixing it. But there is one more thing to do. We need to move the gettext-domain attribute from <schema> element to <schemalist> element or add the attribute to each <schema>.
Reopened.
Review of attachment 253132 [details] [review]: sure, go ahead
Review of attachment 253132 [details] [review]: Thanks. Committed: https://git.gnome.org/browse/gnome-clocks/commit/?id=a65981b332d005da35e2a045aa295b564392a75d