|
2008-01-16
, 19:08
|
Posts: 12 |
Thanked: 2 times |
Joined on Dec 2007
|
#12
|
|
2008-01-16
, 20:41
|
Posts: 215 |
Thanked: 44 times |
Joined on Dec 2007
|
#13
|
|
2008-01-16
, 21:34
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#14
|
|
2008-01-16
, 22:05
|
Posts: 215 |
Thanked: 44 times |
Joined on Dec 2007
|
#15
|
|
2008-01-17
, 02:18
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#16
|
|
2008-01-17
, 05:05
|
Posts: 215 |
Thanked: 44 times |
Joined on Dec 2007
|
#17
|
|
2008-01-17
, 05:56
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#18
|
|
2008-01-17
, 19:10
|
Posts: 215 |
Thanked: 44 times |
Joined on Dec 2007
|
#19
|
|
2008-01-17
, 23:41
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#20
|
I'm creating an Excel spreadsheet vcf cleaner to take care of the Yahoo vcf -> GPE problems. I'll post a link when it's done. I'm understanding the character set encoding problem better now - it looks like Yahoo exports genuine UTF-8, but then further encodes the UTF-8 output for HTML compatibility (e.g., the accented character a-acute is E1h in the standard Windows ANSI character set - that becomes two 8-bit characters C3h A1h in UTF-8, but then gets further altered to the 6 characters =C3=A1 in Yahoo's exported vcf file - but GPE Contacts can't read any of these forms without choking).