GNOME Bugzilla – Bug 618523
Need a way to mark summary/description as translatable
Last modified: 2010-06-19 03:24:47 UTC
We need a way to mark summary and description as being translatable. In addition intltool needs to be made aware of gsettings schema files (see https://bugs.launchpad.net/intltool/+bug/579888). It would be nice if this could then also be supported in the simple gsettings schema format. In addition it would be cool if there was a way to have translator comments in the simple schema format, which would then be translated to inline XML comments in the xml schema format.
The way you mark these as translatable is just like with the gconf schemas: Put <_summary>text</_summary> in your foo.gschema.xml.in and use @INTLTOOL_XML_NOMERGE_RULE@ in your Makefile.am to produce the foo.gschema.xml file.
Will that also strip the _ in the resulting foo.gschema.xml? Also, we still would need a way to do this in the simple format too (or drop the simple format). Maybe the simple format could support _summary/_description (and output <_default> when l10n="..." is set)?
Ok it seems no additional support is needed in intltool. There is just the support for this in the simple format if possible.
For the simple format, we need to chat with Danilo what would be appropriate.
https://bugs.launchpad.net/bugs/580526 <- bug for the simple format.
(In reply to comment #3) > Ok it seems no additional support is needed in intltool. There is just the > support for this in the simple format if possible. We need a way to translate <default l10n=...> even in the XML format. Currently this is not marked for translation, and I'm not sure marking it as <_default...> would work.
(In reply to comment #6) > (In reply to comment #3) > > Ok it seems no additional support is needed in intltool. There is just the > > support for this in the simple format if possible. > We need a way to translate <default l10n=...> even in the XML format. Currently > this is not marked for translation, and I'm not sure marking it as > <_default...> would work. Why wouldn't it work? Have you tried?
Well, there are the messages and context params to take into account, so I don't think it would work. And Ryan is currently working on intltool support for this, so I guess that's a good hint to doesn't work ATM. ;-)
i'm currently looking into adding GSettings support to intltool
I sent a patch here: https://bugs.launchpad.net/intltool/+bug/580526. so it's an intltool issue now. The schema conversion script will be moving out of the glib tree soon, with only support for the XML format "officially" remaining.