GNOME Bugzilla – Bug 707946
Utilize intltool 0.50 gsettings support
Last modified: 2013-09-16 19:38:42 UTC
I don't think the appdata is being translated properly due to use of @INTLTOOL_XML_NOMERGE_RULE@. Bijiben seems to be making due with both @INTLTOOL_XML_RULE@ and @INTLTOOL_XML_NOMERGE_RULE@ in the same Makefile.am, but this does not seem right. We can drop the nomerge rule by modernizing the gsettings build a bit. I verified that this doesn't affect translators by running `intltool-update cs` (a random up-to-date language) from the po directory.
Created attachment 254752 [details] [review] Utilize intltool 0.50 gsettings support This lets us replace @INTLTOOL_XML_NOMERGE_RULE@ with @INTLTOOL_XML_RULE@ so that we can merge the appdata translations into the installed file
Review of attachment 254752 [details] [review]: ::: data/org.gnome.documents.gschema.xml.in @@ +19,3 @@ <default>true</default> + <summary>Window maximized</summary> + <description>Window maximized state</description> I don't understand how these get to be translated if the <_...> tag is removed... Is @INTLTOOL_XML_RULE@ smart enough to look for <summary> and <description> automatically?
(In reply to comment #2) > Is @INTLTOOL_XML_RULE@ smart enough to look for <summary> and <description> > automatically? intltool 0.50 (Dec. 2011) will handle .gschema.xml files automatically without need for any macro. @INTLTOOL_XML_RULE@ is there to merge the appdata translations into the installed appdata file (which was the motivation for this change).
Review of attachment 254752 [details] [review]: Thanks for the clarification, Michael. Patch looks good to me.
Attachment 254752 [details] pushed as e921ba3 - Utilize intltool 0.50 gsettings support