Comment # 5 on bug 1052205 from Ladislav Slez�k

(In reply to Fabian Vogt from comment #3)
> I'd suggest to move the calls to gettext to the actual code instead.

The problem is not calling the gettext, the problem is to mark the texts for
translation so they are extracted into the POT file and translated by
translators.

That already works for YCP, Ruby and XML (we use a glade compatibility hack).

> If the lack of comments is an issue, there could be a comment hash entry for
> the entries that need it.

Yes, that's the usual workaround for the JSON format.