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 532784 - Character corrupted
Character corrupted
Status: RESOLVED OBSOLETE
Product: l10n
Classification: Infrastructure
Component: Czech [cs]
git master
Other Windows
: Normal normal
: ---
Assigned To: Petr Kovar
Lucas Lommer
Depends on:
Blocks:
 
 
Reported: 2008-05-12 15:15 UTC by Ondrej Brandejs
Modified: 2008-08-29 06:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
replace → with -> to solve this bug (4.03 KB, patch)
2008-05-12 19:49 UTC, Lucas Lommer
none Details | Review
GIMP tips screenshot (16.21 KB, image/png)
2008-08-27 20:19 UTC, Petr Kovar
  Details

Description Ondrej Brandejs 2008-05-12 15:15:49 UTC
Incorrect translation
Application: GIMP

Incorrect text:
It seems that some (between "Úpravy" and "Vykreslit) character is corrupted in "Nápověda>>Tip dne" ("Help>>Tip of the day" i guess).

OS version: Windows XP SP2 x64 version, english

Gimp version:2.4.5 for windows, czech (downloaded from http://downloads.sourceforge.net/gimp-win/gimp-2.4.5-i686-setup.exe)

Screenshot : http://img383.imageshack.us/my.php?image=tipyj4.png

Should be:
Comment 1 Lucas Lommer 2008-05-12 19:49:24 UTC
Created attachment 110800 [details] [review]
replace → with -> to solve this bug

Package http://l10n.gnome.org/POT/gimp.HEAD/gimp-tips.HEAD.cs.po

It seems Windows is unable to show → (→) UTF-8 entity (0xE2
0x86 0x92)

Slovak language solves this with "->" instead of "→", this is a set of
changes to change czech translation likewise

Any suggestions if this is even a gimp bug not windows? :)
Comment 2 Kamil Páral 2008-05-12 20:53:42 UTC
I use this character every day on Czech Ubuntu wiki, Windows have no problem displaying it in HTML. Maybe GIMP should somehow indicate it's a Unicode application. I think this should be solved on developer level, not on localization level. I wonder whether english users don't have this problem? The developers should look into it and fix it or possibly change the msgstr strings.
Comment 3 Petr Kovar 2008-05-13 21:47:52 UTC
Good points, Kamil.

Now I wonder to whom should we re-assign the bug. Let's list the candidates:

The GIMP
Pango
GTK+
GTK+ for Windows packager(s)

May be incomplete... Any thoughts?
Comment 4 Petr Kovar 2008-08-27 20:19:26 UTC
Created attachment 117485 [details]
GIMP tips screenshot

Unfortunately, I've no Windows XP SP2 x64 here, but interestingly Windows XP SP1 works for me (with GIMP 2.4.7). Thus the issue could lie in x64 platform, or in the now outdated GIMP version (i.e. 2.4.5). I don't expect WinXP Service Packs to affect this.
Comment 5 Kamil Páral 2008-08-27 22:32:47 UTC
I can confirm that with GIMP 2.4.5 on Windows Vista Business 32b this problem appears but with GIMP 2.4.7 this problem is fixed, the arrow is visible. I think you can close this bug, it has been solved by GIMP developers.
Comment 6 Petr Kovar 2008-08-28 13:30:37 UTC
Thanks for testing it out.

So I'm closing the bug. Feel free to reopen it if the issue persists on your end, Mr. Brandejs.
Comment 7 Ondrej Brandejs 2008-08-28 15:07:40 UTC
In Gimp 2.4.7 (GTK 2.10.0?) problem still persists. It seems that only arrows are corrupted, so Lucas Lommer could be right. Could it be caused by wrong font - is it possible to change it?
Comment 8 Kamil Páral 2008-08-28 19:35:02 UTC
Try to create new user account and examine it there. Be sure to install Gimp with the bundled GTK, it could also be fixed in GTK.
Comment 9 Ondrej Brandejs 2008-08-28 21:10:56 UTC
Same bug appeared in Windows Vista 64bit. I uninstalled it and removed remaining files in user profile folder. Problem seems to be fixed. Tomorrow, I will try it on XP64.
Comment 10 Ondrej Brandejs 2008-08-29 06:28:14 UTC
Problem on Win-XP64 was solved by same way as on Win-Vista 64 - clear instalation. I think that this bug coud be caused by upgrading 2.2.x to 2.4.x