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 349396 - Dictionary; some problem with data conversion
Dictionary; some problem with data conversion
Status: RESOLVED NOTGNOME
Product: gnome-utils
Classification: Deprecated
Component: gdict-applet
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-31 07:26 UTC by Daniel Holbach
Modified: 2006-09-01 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Daniel Holbach 2006-07-31 07:26:58 UTC 
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-utils/+bug/48409

Ubuntu 6.06 i386 desktop; Dictionary 2.14.0
Applications/Accessories/Dictionary

When I try to search word "moses" I get this error:

Error while looking up definition
Error while reading reply from server:
Invalid byte sequence in conversion input

After this error, Dictionary doesn't work anymore (it cannot find anything). I have to restart it.

I guess that this is more general problem, not only one word.
Comment 1 Emmanuele Bassi (:ebassi) 2006-07-31 08:07:34 UTC 
cannot reproduce with gnome-dictionary HEAD.

seems like a dupe of bug #349335, which in turn seems a dupe of bug #330782 (fixed in 2.15).

which dictionary source are you (or the original reporter) using?
Comment 2 Daniel Holbach 2006-07-31 08:36:19 UTC 
It seems to be dictionary-server.org which seems to be the default (we don't change that in Ubuntu). I use de_DE.UTF-8 as locale, if that matters.
Comment 3 Emmanuele Bassi (:ebassi) 2006-07-31 08:44:29 UTC 
the default is dict.org and it should pass UTF-8 data unless something happens on the wire.

I'll try to reproduce, but the only times I saw something like this was when the dictionary server didn't correctly encode the data in UTF-8.
Comment 4 Daniel Holbach 2006-07-31 09:08:25 UTC 
Ah no, it was dictionary-server.dict.org. (aspen.miranda.org dictd 1.9.15/rf on Linux 2.4.27-2-k7 <auth.mime> <47332762.22225.1154336807@aspen.miranda.org> - if that helps in any way.)
Comment 5 Emmanuele Bassi (:ebassi) 2006-08-25 11:46:16 UTC 
currently, we can't do anything to prevent this problem: if the dictionary server sends us badly encoded UTF-8 there is no fallback conversion available.
Comment 6 Sebastien Bacher 2006-09-01 13:27:52 UTC 
the distribution bug submitter argue than the dictionnary should display a message about the incorrect encoding and not stop working fine, he has a point, reopening