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 506556 - Translators namelist contain ? chars
Translators namelist contain ? chars
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: User Interface
1.0.0
Other All
: Normal trivial
: 2.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-31 10:57 UTC by Kalman Kemenczy
Modified: 2010-11-16 07:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot showing the problem (18.33 KB, image/png)
2008-07-17 20:10 UTC, Bertrand Lorentz
  Details
Force the translator extraction in utf-8 (512 bytes, patch)
2008-07-17 21:30 UTC, Bertrand Lorentz
committed Details | Review

Description Kalman Kemenczy 2007-12-31 10:57:35 UTC
Please describe the problem:
it looks not handle well the UTF-8 encoding
http://workshop.connor.hu/tmp/screen_20071230124744.png



Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Bertrand Lorentz 2008-07-17 16:42:53 UTC
Thank you for your bug report.
This problem seems to be fixed in banshee 1.0. Feel free to reopen it if you still experience it.
Comment 2 Kalman Kemenczy 2008-07-17 18:43:19 UTC
Unfortunately not solved, please checked the translator list e.g Hungarian, French, Lithuanian, Spanish
Comment 3 Bertrand Lorentz 2008-07-17 20:09:18 UTC
You're right, it is still happening. I'll attach a screenshot.

The strange thing is that it only happen if I run my system-wide banshee. As I'm using Gentoo, installing banshee means compiling it. During the compile, the translator.xml file is regenerated, but with the wrong encoding.

We should find a way to regenerate the file correctly, and maybe not regenerate it if it is not needed.

I guess this might not happen on other distros. Which one are you using ?
Comment 4 Bertrand Lorentz 2008-07-17 20:10:03 UTC
Created attachment 114730 [details]
Screenshot showing the problem
Comment 5 Kalman Kemenczy 2008-07-17 20:27:24 UTC
I am using openSUSE 11.0
Comment 6 Bertrand Lorentz 2008-07-17 21:30:55 UTC
Created attachment 114732 [details] [review]
Force the translator extraction in utf-8

This is a one line patch that forces the translator extraction to be done with a utf-8 locale.
You have to run "./autogen.sh" after applying it.

As the bug probably only happens in a specific context (emerge'ing on Gentoo or creating a package on another distro), it would be nice to test it by installing a package created with this patch.
Comment 7 Kalman Kemenczy 2008-07-25 08:45:03 UTC
ok, it looks it's working from the trunk.
many thanks
Comment 8 Bertrand Lorentz 2008-07-25 08:55:23 UTC
Re-opening, because the patch hasn't been committed, and so the bug still happens if you build banshee with a non utf-8 locale.
Comment 9 Aaron Bockover 2008-07-25 19:21:22 UTC
Committed, thanks!
Comment 10 Emmanouel Kapernaros 2010-11-16 07:38:46 UTC
Hello,

The bug still exists on Ubuntu 10.10 which has Banshee 1.8. I also tried Ubuntu 9.10, 10.04 and Mint Debian Edition which have Banshee 1.6 and the bug is there too.

OpenSUSE with Banshee 1.6 is fine.. no bug there..

Could it be the way they compile banshee? Is there anything I can do to help resolving this?

Thanks.