I have sent you a sample UTF8-encoded CSV file created by Yahoo! Mail to zautrix@users.sourceforge.net. You use it to test KAPI.
Another problem I found in KAPI is that the data file "kdepim/apps/kabc/std.vcf" used by KAPI accidentally breaks some double-byte characters used by Asian language. Therefore I added some Chinese characters in the comment field of the last contact in the CSV file. You can see this problem if you open std.vcf in vim directly.
Let me know if you need more help. Thanks!
Shreks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77177\"][{POST_SNAPBACK}][/a][/div]
Thx for the sample file.
I hope I have fixed the problems. Please try new version 2.1.3 and let me know if it works or not.
z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77322\"][{POST_SNAPBACK}][/a][/div]
I tried 2.1.3 and test the import function of CVS file, the missing "CATEGORY" is added and works correctly. So far I found one more bug:
When a CSV file is imported, the BIRTHDAY field can be selected to match the actual column of birthdays. But after importing, the actual contacts in KAPI do NOT contain birthday information. I think it was left out by accident.
I have another suggestion which I think is critical:
For all columns of data in CSV which cannot be matched to any pre-defined fields of KAPI, it is better use "NOTES" filed (predefined in KAPI)to include all unmatched data such that all information in user's CSV file is kept. Right now KAPI simply discards all "UNDEFINED" data, which may usually lose significant amount of data in CSV file. After importing CSV file, user can manually move unclassified data from NOTES area to corresponding places. Does this sound good?