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 701908 - Documentation references AM_GLIB_GNU_GETTEXT which should not be used?
Documentation references AM_GLIB_GNU_GETTEXT which should not be used?
Product: gtkmm
Classification: Bindings
Component: documentation
Other Linux
: Normal normal
: ---
Assigned To: gtkmm-forge
Depends on: 622991 624186
Reported: 2013-06-09 22:49 UTC by Sandro Mani
Modified: 2016-01-20 15:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Sandro Mani 2013-06-09 22:49:20 UTC
The internationalization documentation [1] references AM_GLIB_GNU_GETTEXT, however, according to [2], upstream gettext, i.e.


should be used. Perhaps the documentation could be updated? See also [3].

Comment 1 Kjell Ahlstedt 2013-06-13 15:18:31 UTC
[2] refers to glib bug 624186, which suggests that AM_GLIB_GNU_GETTEXT shall be
deprecated. That bug was filed almost 3 years ago. It has not been commented
or implemented. It depends on bug 622991, which has been commented, but not
implemented. The comments are mildly critical. It's not obvious that the
patch in that bug will be implemented, and that AM_GLIB_GNU_GETTEXT will
really be deprecated. I let this bug depend on the two glib bugs.

Is there anything wrong with AM_GLIB_GNU_GETTEXT? If not, perhaps we can leave
the gtkmm tutorial as it is until AM_GLIB_GNU_GETTEXT really is deprecated.
Comment 2 Sandro Mani 2013-06-17 11:24:41 UTC
From what I can see, AM_GLIB_GNU_GETTEXT works fine, but so does AM_GNU_GETTEXT. My reason for reporting this issue was the referenced blog post [2]. But I'm ok with having it depend on the glib bugs.
Comment 3 Kjell Ahlstedt 2016-01-15 09:56:02 UTC
Now  AM_GLIB_GNU_GETTEXT has been deprecated. It's time to change the gtkmm
tutorial. But I suspect that it's not quite as simple as replacing

When I tested in a small program, ./ stopped with
  config.status: error: po/ was not created by intltoolize.

That error message is mentioned in comment 0's ref [3]. It's not obvious to me
what's the best way to fix the problem.

This requires more investigation. If I shall change the gtkmm tutorial, I want
to be reasonably sure that it becomes correct.
Comment 4 Kjell Ahlstedt 2016-01-20 15:11:04 UTC
I have updated the gtkmm tutorial.

To avoid the error message mentioned in comment 3, call intltoolize after
autoreconf, autopoint or gettextize in