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 268800 - Needs to specify the translation domain explicitly in the shlib components code
Needs to specify the translation domain explicitly in the shlib components code
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: general
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: JP Rosevear
Evolution QA team
Depends on:
Blocks: 236276
 
 
Reported: 2004-10-26 13:31 UTC by Changwoo Ryu
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Changwoo Ryu 2004-10-26 13:31:34 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

The shlib components can sometimes be run by other processes instead of
evolution itself.  One example is the ximian connector.  In such a case,
implicit gettext() looks the translation up in the default domain
("ximian-connector-2.0"), not in the "evolution-2.0" domain.

To correct this problem, BONOBO_EXPLICIT_TRANSLATION_DOMAIN can be defined
before including bonobo-i18n.h.  (Or any other way to define _() as dgettext())


Steps to reproduce the problem:
1. run evolution with ximian connector in a non-English locale.

Actual Results:
In the Exchange window, some strings are untranslated.  For example, "New"
button and its menu items.

Expected Results:
They should be translated by the evolution translations.

How often does this happen? 
always.

Additional Information:
Comment 1 André Klapper 2004-12-27 18:57:12 UTC
adding dependency
Comment 2 André Klapper 2005-03-23 17:48:16 UTC
retargetting the string translation bugs that were targetted to 2.1 to
2.3. for an entire list see bug 236276.
Comment 3 Not Zed 2005-08-10 02:19:15 UTC
as far as i'm aware, this is either fixed, or covered by other bugs. e.g. 300891