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 640997 - catalog.init() should be called at the start of application.
catalog.init() should be called at the start of application.
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on: 630110
Blocks:
 
 
Reported: 2011-01-31 04:35 UTC by Zhou Ting
Modified: 2020-03-17 08:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Move locale init to app start (2.58 KB, patch)
2011-01-31 04:36 UTC, Zhou Ting
accepted-commit_after_freeze Details | Review

Description Zhou Ting 2011-01-31 04:35:46 UTC
catalog.init() should be called at the start of application.

Otherwise, any call of catalog.getstring() before  catalog.init() can not get translated string.


For example, the call of catalog.getstring() below in file src/Extensions/Banshee.MeeGo/Banshee.MeeGo/MeeGoPanel.cs  can not get translated "media"
 embedded_panel = new PanelGtk ("banshee", Catalog.GetString ("media"),
                    null, "media-button", true);


Please refer to meego defects: http://bugs.meego.com/show_bug.cgi?id=7190
Comment 1 Zhou Ting 2011-01-31 04:36:45 UTC
Created attachment 179688 [details] [review]
Move locale init to app start
Comment 2 Gabriel Burt 2011-03-22 15:25:14 UTC
Comment on attachment 179688 [details] [review]
Move locale init to app start

As is, this will break our Windows build's i18n b/c we don't yet use Booter.  I think we will after 2.0 when we merge the dbus-sharp branch and land the Windows remoting patch.
Comment 3 André Klapper 2012-02-02 20:20:16 UTC
(In reply to comment #2)
> I think we will after 2.0 when we merge the dbus-sharp branch and land the
> Windows remoting patch.

Gabriel: Is this still the plan / can this be done now?
Asking as the patch still has accepted-commit_after_freeze status.
Comment 4 André Klapper 2012-03-31 19:19:33 UTC
(In reply to comment #2)
> I think we will after 2.0 when we merge the dbus-sharp branch and land the
> Windows remoting patch.

Gabriel: Is this still the plan / can this be done now?
Asking as the patch still has accepted-commit_after_freeze status.
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2012-03-31 19:31:37 UTC
AFAIK the remoting patch has not landed yet. And I think the reason for that is that some maintainer wanted to know/check if dbus-sharp worked on Windows, which would be a better/easier solution.
Comment 6 André Klapper 2012-06-26 12:20:06 UTC
(In reply to comment #5)
> AFAIK the remoting patch has not landed yet. And I think the reason for that is
> that some maintainer wanted to know/check if dbus-sharp worked on Windows,
> which would be a better/easier solution.

Will this ever happen? And who is "some maintainer" exactly?
Comment 7 André Klapper 2020-03-17 08:59:27 UTC
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.