After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618523 - Need a way to mark summary/description as translatable
Need a way to mark summary/description as translatable
Status: RESOLVED NOTABUG
Product: glib
Classification: Platform
Component: gsettings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-05-13 10:32 UTC by jessevdk@gmail.com
Modified: 2010-06-19 03:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jessevdk@gmail.com 2010-05-13 10:32:36 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.
Comment 1 Christian Persch 2010-05-13 11:31:02 UTC
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.
Comment 2 jessevdk@gmail.com 2010-05-13 12:09:50 UTC
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)?
Comment 3 jessevdk@gmail.com 2010-05-13 12:36:56 UTC
Ok it seems no additional support is needed in intltool. There is just the support for this in the simple format if possible.
Comment 4 Vincent Untz 2010-05-14 14:12:47 UTC
For the simple format, we need to chat with Danilo what would be appropriate.
Comment 5 Ignacio Casal Quinteiro (nacho) 2010-05-14 14:27:06 UTC
https://bugs.launchpad.net/bugs/580526 <- bug for the simple format.
Comment 6 Milan Bouchet-Valat 2010-06-07 14:19:19 UTC
(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.
Comment 7 Christian Persch 2010-06-07 16:33:21 UTC
(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?
Comment 8 Milan Bouchet-Valat 2010-06-07 17:35:57 UTC
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. ;-)
Comment 9 Allison Karlitskaya (desrt) 2010-06-07 21:07:16 UTC
i'm currently looking into adding GSettings support to intltool
Comment 10 Allison Karlitskaya (desrt) 2010-06-19 03:24:47 UTC
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.