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 344231 - Wrong gettext catalog name
Wrong gettext catalog name
Status: RESOLVED OBSOLETE
Product: eel
Classification: Deprecated
Component: general
2.14.x
Other Mac OS
: Normal trivial
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-08 02:04 UTC by Daniel Macks
Modified: 2011-09-22 04:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Macks 2006-06-08 02:04:50 UTC 
It's pretty confusing that the gettext message catalog files have a name that doesn't correspond to the soname of the library that uses them. As of eel-2.14.1 (and CVS HEAD appears the same), I get libeel-2.2.dylib but eel-2.0.mo, whereas eel-2.2.mo would make more sense. Patch configure.in:

-GETTEXT_PACKAGE=eel-2.0
+GETTEXT_PACKAGE=eel-2.2
Comment 1 Christian Persch 2007-02-20 18:42:13 UTC 
Why would the gettext domain follow the SONAME of the library? I think this is NOTABUG, but you may want to discuss this on nautilus-list@gnome.org.
Comment 2 Akhil Laddha 2011-09-21 09:50:15 UTC 
eel as a standalone product is no longer maintained. However, large parts of eel was imported into the eel sub directory in nautilus.

Can you please check again whether this issue still happens in nautilus 3.0.2 or upcoming nautilus 3.2.0 and update this report by adding a comment so that the bug can be reassigned to nautilus if it's still valid.
Comment 3 Cosimo Cecchi 2011-09-22 04:23:35 UTC 
Not relevant anymore since we're not a standalone library.