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 267876 - incompatible character encoding
incompatible character encoding
Status: RESOLVED DUPLICATE of bug 214611
Product: evolution
Classification: Applications
Component: Do Not Use
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: JP Rosevear
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-10-09 06:14 UTC by Byeong-taek Lee
Modified: 2013-09-13 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Byeong-taek Lee 2004-10-09 06:14:16 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
I have two visor, prism and platinum.
Before meeting evolution, I used jpilot.
After I used evolution, I missed pims in the evolution.
However, there is just one reason that I cannot use evolution with my
pims tool.
That is the problem about the character code.
Mail component of the evolution became better and better.
I think that it is best among some mail clients.
But Mail component had the same problems, that is character
encoding/decoding problem.
So I hesitated several times, but now it seems to be perfect.
However, still contact, calendar and other components with a conduit
have the same problem.
Specifically, my visor or palm record the korean character as euc-kr.
So I cannot read data imported from visor.
So jpilot with gtk 1.x version has no problem, but jpilot with gtk2 has
the same problem.
I think that this problem is caused from the conversion utf8 to/from
euc-kr, which, I think, is originated from gtk2.
I hope that this problem will be solved as the mail component did.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen? 
always

Additional Information:
Comment 1 JP Rosevear 2004-12-21 16:13:34 UTC
Hmm, I'm sure this is a duplicate.
Comment 2 Gerardo Marin 2004-12-21 17:54:20 UTC

*** This bug has been marked as a duplicate of 214611 ***