Version: (using KDE KDE 3.0.99) Installed from: Debian testing/unstable Packages OS: Linux When syncing with Palm, KPilot does not include locale into result file, so if there i18n data in Todo, AddressBook, DateBook and so this data is shown in Latin-1(?) encoding. Tip: JPilot can point Palm encoding and Host encoding and converts i/o accordinly.
Same thing happens to me. Since everything else in KDE has such a pretty i18n, and this bug renders kpilot (and various other KDE PIM producs) useless for non-english, I think this deserves a _way_ higer "rating" if you call it like that... Anyways, since iconv will do most of the work for you, this shouldn't be a problem to implement (or fix) at all. Good luck :)
C'mon, give me some more information. What is your KDE language set to? What 8-bit encoding does that have? What 8-bit encoding is your Pilot producing? Where is the information showing up in the wrong encoding? In KPilot's memo viewer? In KNotes? I _don't_ have this problem syncing a PalmV (english) with KNotes while my KDE desktop is in C locale. Since I can't reproduce the problem, it may be trivial to fix in _your_ mind, but I can't see it.
Here you have your additional information: My japanese Sony Clie SJ30 (PalmOS 4.1) seems to produce SJIS output. All I see in korganizer, knotes (and all others) are just squares and question marks, and some other _very_ random things, all but what originally is stored in my pilot. I think all versions of PalmOS running in japanese produce SJIS output. Windows (so most probably CE too) uses SJIS as encoding for japanese characters. So PalmOS and WinCE seem to have this in common. Linux on the other hand, uses a encoding called "EUC-JP" in most cases, so Ipaqs or Zauruses having a japanese linux installed will hold all japanese stuff in EUC-JP. And, about the reason you don't experience that problem: C locale on linux _is_ english :) If you still need additional informations, or help with bug-testing or maybe coding (note: I haven't taken a single look at the kpilot sources at the current point), just contact me again. Tho, I can only help you with things regarding japanese. But, since there are quite many translators for each language, I think you will find one using a palm in each language quite easily :) As I said, I'd love to help you with the japanese stuff. I'll take a look at the code in a minute.
Ack, sorry, forgot to add: KDE (korganizer and that kind of stuff to be more precise) seems to use EUC-JP as encoding to display. iconv is a powerful tool to convert between manymany (almost all that exist) charsets, and maybe there are even functions for autodetecting the encoding of a certain string. I will try to find some informations on this. Maybe taking a look at Jpilot or Evolution will help, since it worked for me with them before.
This bug is mostly fixed in KPilot 4.3.7 (in BRANCH, or on the website). In particular, Japanese encodings are now supported. You _will_ need to edit the config file to enable it though, see the messages on the kde-pim mailing list or the KPilot ChangeLog. In the address viewer, both the Kanji and Hiragana lines of the Pilot's address book show up. This will be addressed in 4.3.8. In the meantime, I'm going to guess that the original reported (paul romanchenko) is _not_ using a Japanese Palm Pilot. I need more information from him (preferrably a MemoDB and an AddressDB) before I support KOI-8R (I think the code is trivial, but I want something to test it with first). Fortunately I can read Russian beter than Japanese.
Subject: Re: KPilot does not include locale info into file What kind of information is need from me? I hope this would help: 1. I'm using Palm m505 with charset Windows-1251 2. I'm using KDE with locale ru_RU.KOI8-R 3. I'm using JPilot, which converts Palm (1251) <-> Linux (KOI8-R) It would be good to have the same behaviour in the KPilot. Anyway, KPilot must use system (kde) locale while synchronizing with Palm (in this case I just convert all my records in Palm into KOI8-R, what is not preferred). Feel free to ask me more. Feb 11, Adriaan De Groot: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > You are a voter for the bug, or are watching someone who is. > > http://bugs.kde.org/show_bug.cgi?id=52138 > adridg@cs.kun.nl changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |LATER > > > > ------- Additional Comments From adridg@cs.kun.nl 2003-02-11 23:59 ------- > This bug is mostly fixed in KPilot 4.3.7 (in BRANCH, or on the website). In particular, > Japanese encodings are now supported. You _will_ need to edit the config file to > enable it though, see the messages on the kde-pim mailing list or the KPilot > ChangeLog. In the address viewer, both the Kanji and Hiragana lines of the Pilot's > address book show up. This will be addressed in 4.3.8. In the meantime, I'm going to > guess that the original reported (paul romanchenko) is _not_ using a Japanese > Palm Pilot. I need more information from him (preferrably a MemoDB and an > AddressDB) before I support KOI-8R (I think the code is trivial, but I want something > to test it with first). Fortunately I can read Russian beter than Japanese. >
*** Bug 58390 has been marked as a duplicate of this bug. ***
In _BRANCH, we can't add a dropdown to select the codepage because it adds strings. You will have to wait for KDE 3.2 for this one. In the meantime, from the ChangeLog: * pilotMemo.{h,cc} memoWidget.cc [BRANCH] Use the codec for the returned title of the memo. This is the first step on making PilotMemo return everything in QString format suitable for any encoding. In order to change the encoding, add Encoding=<name> to the kpilotrc file in the top part (ie. after DeviceName). In particular, Encoding=CP1251 will help for CP1251 Pilots.
This bug is not completely solved :( Although the data display is working if I enter the "Encoding" option, this does not affect the drop down menu that displays the "category". It still uses the iso-8859-7 encoding and not the one povided.
Subject: Re: KPilot does not include locale info into file On Monday 26 May 2003 17:06, you wrote: > Although the data display is working if I enter the "Encoding" option, this > does not affect the drop down menu that displays the "category". It still > uses the iso-8859-7 encoding and not the one povided. Here's the culprit: c->insertItem(QString::fromLatin1(info->name[i])); which I missed in pilotComponent.cc. It should be fixed in CVS now.