|
From: Daniel G. <go...@b1...> - 2010-01-29 20:01:47
|
Hi Chris, On Friday 29 January 2010 05:31:12 am Chris Frey wrote: [...] > I'm sure others have handled this before, but I just can't find it. > > How does opensync handle international characters? The plugins, such > as evolution2, don't seem to care what charset the data is in... do > they assume everything is utf-8? iso? the synchronization plugins should actually pass through the content. In case of the evolution2 plugin, it should just just retrieve the VCARD or so in pass it along to the OpenSync framework. The framework then pass it to the suitable format-plugin to convert it to a common-format (e.g. xmlformat). In the case of evolution2 it's the vformat-plugin which convertes the vcard to xmlformat-contact. The vformat-plugin should take care about charset and convert it to UTF-8. > > I see some bits of code to look for CHARSET in the format plugin, you mean src/vformat.c and the iconv calls - right? > but > this is outside the VCARD itself, and in the MIME header. If I'm > passing data to opensync from a plugin, do I include these MIME > headers? Could you give me the complete background of the problem? Which kind of data are you talking about? Some data which get passed to OpenSync via a OSyncChange struct? (e.g. OSyncData ...) Or some other information passed to OpenSync? Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner FOSS Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |