Menu
▾
▴
opensync-devel — The place to coordinate the development of OpenSync
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(9) |
Apr
(84) |
May
(18) |
Jun
(12) |
Jul
(6) |
Aug
(7) |
Sep
(10) |
Oct
(31) |
Nov
(59) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(53) |
Feb
(15) |
Mar
(43) |
Apr
(40) |
May
(63) |
Jun
(142) |
Jul
(54) |
Aug
(31) |
Sep
(30) |
Oct
(39) |
Nov
(36) |
Dec
(64) |
| 2007 |
Jan
(128) |
Feb
(261) |
Mar
(156) |
Apr
(127) |
May
(76) |
Jun
(131) |
Jul
(83) |
Aug
(124) |
Sep
(83) |
Oct
(88) |
Nov
(180) |
Dec
(90) |
| 2008 |
Jan
(86) |
Feb
(93) |
Mar
(117) |
Apr
(104) |
May
(65) |
Jun
(35) |
Jul
(38) |
Aug
(111) |
Sep
(58) |
Oct
(33) |
Nov
(102) |
Dec
(194) |
| 2009 |
Jan
(193) |
Feb
(74) |
Mar
(111) |
Apr
(77) |
May
(31) |
Jun
(20) |
Jul
(1) |
Aug
(3) |
Sep
(57) |
Oct
(125) |
Nov
(50) |
Dec
(3) |
| 2010 |
Jan
(26) |
Feb
(5) |
Mar
(13) |
Apr
(3) |
May
(3) |
Jun
(12) |
Jul
(27) |
Aug
(47) |
Sep
(105) |
Oct
(53) |
Nov
(34) |
Dec
(21) |
| 2011 |
Jan
(115) |
Feb
(17) |
Mar
|
Apr
(6) |
May
(16) |
Jun
(15) |
Jul
(85) |
Aug
(21) |
Sep
(13) |
Oct
(12) |
Nov
(28) |
Dec
(23) |
| 2012 |
Jan
|
Feb
(13) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(5) |
Jul
(5) |
Aug
(31) |
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(33) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(4) |
| 2016 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Daniel G. <go...@b1...> - 2010-04-18 09:08:05
|
Hi Nicolas, On Saturday 17 April 2010 01:50:50 pm Nicolas wrote: > So you find in attachment a little patch to fix the serializer function. > looks good to me. Patch applied - r6045 Thanks for your contribution. Looking forward to more patches ;) 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 |
|
From: Nicolas <pr...@fr...> - 2010-04-17 11:51:06
|
Hi, I have made some tests with my Barry OpenSync plugin about the authentication feature. And, I have meet some issues :( Indeed, since new API have added about option supported flags, we have this issue. So you find in attachment a little patch to fix the serializer function. I use the new API : osync_plugin_authentication_option_set_supported(...) osync_plugin_authentication_option_is_supported(...) to set the supported_options variable in OSyncPluginAuthentication structure. Regards, Nicolas VIVIEN |
|
From: Michael B. <mic...@cm...> - 2010-03-29 09:26:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 libwbxml 0.10.8 release notes Download:https://sourceforge.net/projects/libwbxml/files/libwbxml/0.10.8/ Minor Changes ============= - Added a fix for the broken vFormat handling in the SyncML specification. All LFs are replaced by CRLFs in every vFormat object inside a SyncML message (ticket #38). - Added Nokia ConML support (ticket #35). There is no public documentation available from Nokia. The transformation tables were created from sniffed WBXML documents. The patch was supplied by Anton D. Kachalov. Internal Changes ================ - Removed OMA DM tests because the OMA did not grant a permission for the inclusion (ticket #36). Special thanks goes to Anton D. Kachalov who added the Nokia ConML support. Best regards Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuwckoACgkQ2L0ZGCAwWqvLoQCfet3cOj+lGH90KeVtmryOhYkh seAAoMvWvAH+tanQjD5ADyT8ImO0lJXN =GCb8 -----END PGP SIGNATURE----- |
|
From: Juha T. <Juh...@ik...> - 2010-03-16 13:27:24
|
On Mon, 15 Mar 2010, Chris Frey wrote: > Before you can have a community, you need one dedicated developer. > Unfortunately, nobody has any dedicated time for opensync, that I know of. > > It doesn't matter if 0.22 is out there or not. If 0.39 was better, > people would be using it. You mention slow sync problems in 0.22. > Are all your problems solved in 0.39? > > If the user can avoid the slow sync, or if the user always knows that > one side will be authoritative, 0.22 does work. It's not convenient, > but it can be wrestled and scripted into submission. Too many *if* words. Or enough of them. > There is no need to kill 0.22 to make 0.40 succeed. There are no > developers on 0.22 or 0.40 right now. And my talking about it isn't > getting any code written either. > > I think that if neither 0.22 nor 0.40 are available to the end user > on Debian, opensync might not even be considered when looking for > syncing solutions. For the record, I disagree completely. Tuju -- You want to throw out the baby with the bathwater! - K. Kofler Your baby is my bathwater. I don't want the OS you're building. - J. Keating |
|
From: Chris F. <cd...@fo...> - 2010-03-16 03:44:42
|
On Sat, Mar 13, 2010 at 04:15:32PM +0200, Juha Tuomala wrote: > In the reality where i live and lot of othres, it never succeeded > from slow sync. That means tons of duplicated entries and mess that > renders it useless. If my reality would be very different from rest > of the world, we would have userspace of millions of people. We > don't. [...] > In order to develop opensource software, you need a community > ecosystem that supports that development work. Developers, testers, > occasional bug fixers and end users each need each other. Before you can have a community, you need one dedicated developer. Unfortunately, nobody has any dedicated time for opensync, that I know of. It doesn't matter if 0.22 is out there or not. If 0.39 was better, people would be using it. You mention slow sync problems in 0.22. Are all your problems solved in 0.39? If the user can avoid the slow sync, or if the user always knows that one side will be authoritative, 0.22 does work. It's not convenient, but it can be wrestled and scripted into submission. But you can't script a lack of plugins into submission. I'd like to see 0.40 released even now, even if it is incomplete. I outlined what I thought was necessary before. Mostly, it just needs API changes loudly published. If worrying about the API hinders development, it's better to throw API stability out for now. There is no need to kill 0.22 to make 0.40 succeed. There are no developers on 0.22 or 0.40 right now. And my talking about it isn't getting any code written either. I think that if neither 0.22 nor 0.40 are available to the end user on Debian, opensync might not even be considered when looking for syncing solutions. Removing your last foot from the dock before you're in the boat just puts you in the water. :-) - Chris |
|
From: Michael B. <mb...@gm...> - 2010-03-13 14:35:18
|
On Fri, Mar 12, 2010 at 12:34:42PM +0100, Michael Bell wrote: > Michael Banck wrote: > > > > On Tue, Feb 23, 2010 at 02:16:08PM +0100, Michael Bell wrote: > >> FYI - I preparing a new libwbxml release because of a bug in the SyncML > >> specification. > > > > Seems this did not happen yet - what's the timeframe to expect this > > release? > > Actually I plan it for 2010-Mar-29 or 2010-Mar-30. Do you need an > earlier release? No that's fine, I was just wondering. Thanks, Michael |
|
From: Juha T. <Juh...@ik...> - 2010-03-13 14:15:42
|
On Fri, 12 Mar 2010, Chris Frey wrote: > Well, on the other hand, 0.22 has already shipped, and is in use already. > Until something better comes along, it's the defacto standard in the > opensync world. In the reality where i live and lot of othres, it never succeeded from slow sync. That means tons of duplicated entries and mess that renders it useless. If my reality would be very different from rest of the world, we would have userspace of millions of people. We don't. >> Apparently there is a strong will focus to that irrelvant, and it's >> doing well atm. > > Not sure I understand what you mean by this. In order to develop opensource software, you need a community ecosystem that supports that development work. Developers, testers, occasional bug fixers and end users each need each other. If you do actions that either prevent that ecosystem to exist in the first place or split it half - where other half has testers and users and other only developers, neither one is a healthy ecosystem nor work as expected and required. We need to get all hands into developmenet branch. Having something easy available in 0.2x branch drags focus there and the HEAD suffers from lack of activity. That's what i explained a year or more ago, suggested that we kill the whole 0.2x officially and recommend distros to drop it. It didn't happen nor did the 0.40 release. I see connection between these two, others don't. Someone may say that I'm wrong, but if the project has failed its own goals and mailstones, something is wrong and things are not working as planned. If I'm wrong, you probably have better explanation for that failure. I'd like to hear it. Br, Tuju -- You want to throw out the baby with the bathwater! - K. Kofler Your baby is my bathwater. I don't want the OS you're building. - J. Keating |
|
From: Chris F. <cd...@fo...> - 2010-03-12 22:28:35
|
On Fri, Mar 12, 2010 at 01:50:06PM +0200, Juha Tuomala wrote: > > On Thu, 11 Mar 2010, Chris Frey wrote: > > Remember Fedora's error. I have no problem with 0.40 being in testing > > and unstable. I do have a problem with 0.22 dying before a proper > > replacement is ready. > > The fact is that: > > there is no production ready product to ship Well, on the other hand, 0.22 has already shipped, and is in use already. Until something better comes along, it's the defacto standard in the opensync world. > Apparently there is a strong will focus to that irrelvant, and it's > doing well atm. Not sure I understand what you mean by this. - Chris |
|
From: Chris F. <cd...@fo...> - 2010-03-12 22:24:28
|
On Fri, Mar 12, 2010 at 01:34:44AM +0100, Michael Banck wrote: > Well, making it possible to run both and actually supporting the stable > version are two different things. If you look at the trac list for > 0.22, you see loads of tickets which look fatal. AFAICT, there were two > commits on the 0.2x branch in the last 2-3 years. > > Maybe it is my fault, but I stopped fowarding (or even looking) at 0.22 > bugs in Debian for a while now, assuming nobody else cares, either. While people aren't caring enough to fix bugs in 0.22, and while the 0.22 platform is shakey, it is still useable. Is it not ok to consider 0.22 as legacy software, only available for people to use if it works for them, but no support? > I believe the story is: libsyncml-0.4.7 (I think) and above use > libsoup-2.4, while the others use libsoup-2.2. The syncml plugin for > opensync-0.22 only works with libsyncml-0.4.6 (I think) and lower. Are these simple API changes, or wholesale APIs removed or changed? Going from 0.4.6 to 0.4.7 doesn't look like a huge change, from the version numbers. Is this patchable? Is it worth my time to send a patch to you? > I really don't want to point fingers, and I take the blame for the wrong > upload, but in the end, I would have just as well removed opensync-0.22 > for the next stable release even if 0.3x would still be in experimental. I have a hard time with this. This just makes it even harder for users who want to sync with opensync. Maybe people use 0.22 and then give up later due to bugs, but I know that some folks are quite happy that *any* form of sync is available for them on Linux. Whether there are bugs or not. If the next stable has no opensync at all, where will these users go? - Chris |
|
From: Juha T. <Juh...@ik...> - 2010-03-12 12:10:10
|
On Thu, 11 Mar 2010, Chris Frey wrote: > Remember Fedora's error. I have no problem with 0.40 being in testing > and unstable. I do have a problem with 0.22 dying before a proper > replacement is ready. The fact is that: there is no production ready product to ship I still fail to see, why distros should ship something that does not exist? Make people to fight with something that is known not to work? (that is, handle slowsyncs) However, I do see, how it's hurting the goal of getting something working finished. If there was only a SCM repository, there would be more people trying HEAD, feeding activity to that developmenet ecosystem. Apparently there is a strong will focus to that irrelvant, and it's doing well atm. Tuju -- You want to throw out the baby with the bathwater! - K. Kofler Your baby is my bathwater. I don't want the OS you're building. - J. Keating |
|
From: Michael B. <mic...@cm...> - 2010-03-12 12:09:09
|
Michael Banck wrote: > > On Tue, Feb 23, 2010 at 02:16:08PM +0100, Michael Bell wrote: >> FYI - I preparing a new libwbxml release because of a bug in the SyncML >> specification. > > Seems this did not happen yet - what's the timeframe to expect this > release? Actually I plan it for 2010-Mar-29 or 2010-Mar-30. Do you need an earlier release? Best regards Michael P.S. I have some time tomorrow if you really need it. -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mb...@de...> - 2010-03-12 00:36:27
|
Hi, On Thu, Mar 11, 2010 at 06:28:19PM -0500, Chris Frey wrote: > On Fri, Mar 12, 2010 at 12:17:28AM +0100, Michael Banck wrote: > > Does anybody else see another way forward? > > This is really unfortunate. An external dependency is killing 0.22 > when we've put real effort into making it possible to run 0.22 and > 0.40 side by side. Well, making it possible to run both and actually supporting the stable version are two different things. If you look at the trac list for 0.22, you see loads of tickets which look fatal. AFAICT, there were two commits on the 0.2x branch in the last 2-3 years. Maybe it is my fault, but I stopped fowarding (or even looking) at 0.22 bugs in Debian for a while now, assuming nobody else cares, either. > The only way to properly kill 0.22 is by making 0.40 better. And if > all those plugins have to go, 0.40 is not yet better. I agree. That is why I also mention delayed releases - I have the feeling that *some* plugins sometimes get ported after a release, but they're always catching up with the new changes. > Remember Fedora's error. I have no problem with 0.40 being in testing > and unstable. I do have a problem with 0.22 dying before a proper > replacement is ready. Well, 0.22 will live on in Debian stable, so probably supported until late 2011. > What is missing in libsyncml that 0.22 can't work with it? I'm afraid > I'm not up to speed on the syncml side of things. I believe the story is: libsyncml-0.4.7 (I think) and above use libsoup-2.4, while the others use libsoup-2.2. The syncml plugin for opensync-0.22 only works with libsyncml-0.4.6 (I think) and lower. I really don't want to point fingers, and I take the blame for the wrong upload, but in the end, I would have just as well removed opensync-0.22 for the next stable release even if 0.3x would still be in experimental. Michael |
|
From: Chris F. <cd...@fo...> - 2010-03-12 00:05:54
|
On Fri, Mar 12, 2010 at 12:17:28AM +0100, Michael Banck wrote: > Does anybody else see another way forward? This is really unfortunate. An external dependency is killing 0.22 when we've put real effort into making it possible to run 0.22 and 0.40 side by side. Trying to kill 0.22 because it's old is the wrong way to go, in my opinion. The only way to properly kill 0.22 is by making 0.40 better. And if all those plugins have to go, 0.40 is not yet better. Remember Fedora's error. I have no problem with 0.40 being in testing and unstable. I do have a problem with 0.22 dying before a proper replacement is ready. What is missing in libsyncml that 0.22 can't work with it? I'm afraid I'm not up to speed on the syncml side of things. - Chris |
|
From: Michael B. <mb...@de...> - 2010-03-11 23:19:12
|
Hi, finally libsyncml-0.5.4 got uploaded to Debian unstable (due to an accident on my side, but the pressure to drop libsoup-2.2 was ever increasing anyway). I also uploaded opensync-0.39 to unstable a while a go as well. That means opensync-0.22 will have to be removed (it doesn not work with libsyncml-0.5.4) and as a side-effect the following plugins will have to be removed, because there are no releases for 0.39 for them, as far as I know: gnokii, google-calendar, gpe, irmc, kdepim, moto, opie, palm, python and sunbird. As a side note, I would really suggest giving plugin maintainers the possiblity to make delayed releases of their plugins for a new opensync release. I will also request the removal of all opensync packages from testing, as 0.22 is abandoned and 0.3x is not ready - I don't see a way to support them through another Debian release. Sorry to say this. Does anybody else see another way forward? Michael |
|
From: Michael B. <mb...@gm...> - 2010-03-11 22:53:40
|
Hi, On Tue, Feb 23, 2010 at 02:16:08PM +0100, Michael Bell wrote: > FYI - I preparing a new libwbxml release because of a bug in the SyncML > specification. Seems this did not happen yet - what's the timeframe to expect this release? Michael |
|
From: Michael B. <mic...@cm...> - 2010-02-23 13:27:36
|
Hi, FYI - I preparing a new libwbxml release because of a bug in the SyncML specification. Several times in the past I had problems with the correct transport of vCards. vCards require CRLF as line break. XML processors normalize all line breaks to LFs. The SyncML authors did ignore this fact and store raw (not base64 encoded) vCards in XML files. If a normal XML processor like expat or libxml reads such a file then all CRLFs are gone. So libwbxml has no chance to only parse SyncML messages in XML format with a normal XML processor. The implemented workaround checks for Data elements with vFormat objects and replaces all included LFs with CRLFs. This behaviour is hard coded in libwbxml. Some weeks ago the first user of libwbxml opened a ticket for this issue. So a solution is required. Additionally I cannot write changes to my OCS without this patch. Minor: Additionally a copyright issue with the OMA DM tests was fixed. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Daniel G. <dg...@cr...> - 2010-02-06 12:49:25
|
On Sat, Feb 06, 2010 at 12:24:57PM +0100, Daniel Gollub wrote: > On Sat, Feb 06, 2010 at 10:48:36AM -0000, Paul Eggleton wrote: > > Hi all, > > > > Who here is currently at FOSDEM? If there is anyone, I'm also here so it > > would be great to organise a meetup of some kind. Perhaps a BOF session? > > > I'm currently in room Jason listing to one of the key notes.After that i don't have any specific plan to attend any talk before 14:00 ... > > > What about meeting after that keynote at the catering? Any suggestion for an alternative date? AFAIK Alban aka. parahal is also around. (I'm sitting in room Janson again) Best Regards, Daniel |
|
From: Daniel G. <dg...@cr...> - 2010-02-06 11:25:11
|
On Sat, Feb 06, 2010 at 10:48:36AM -0000, Paul Eggleton wrote: > Hi all, > > Who here is currently at FOSDEM? If there is anyone, I'm also here so it > would be great to organise a meetup of some kind. Perhaps a BOF session? I'm currently in room Jason listing to one of the key notes.After that i don't have any specific plan to attend any talk before 14:00 ... What about meeting after that keynote at the catering? The talk started delyed so i have no idea when it really ends ... Best Regards, Daniel > > Cheers, > Paul > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Opensync-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-devel |
|
From: Daniel G. <dg...@cr...> - 2010-02-06 11:24:14
|
Hi, if you're at FOSDEM this year and want to meet some opensync people, let me know. Best Regards, Daniel |
|
From: Paul E. <blu...@bl...> - 2010-02-06 11:10:10
|
Hi all, Who here is currently at FOSDEM? If there is anyone, I'm also here so it would be great to organise a meetup of some kind. Perhaps a BOF session? Cheers, Paul |
|
From: Nicolas <pr...@fr...> - 2010-01-31 17:50:28
|
By the way, have you doc or samples about merger features. I can implement a merger "plugin" for vcard, event, vjournal or/and vnote... as you want. Regards, Nicolas Le dimanche 31 janvier 2010 à 18:00 +0100, Daniel Gollub a écrit : > Hi Nicolas, > > On Sunday 31 January 2010 05:44:11 pm Nicolas wrote: > > Ticket #1206 > > > > I can improve (or try) my patch. Ask me what you wa > > > > the patch looks pretty good to me at first glance! > > I'm just running the testsuite with the patch to check if we need to adapt the > testsuite. > > Thanks a lot for the patch! > > Best Regards, > Daniel > |
|
From: Daniel G. <go...@b1...> - 2010-01-31 17:09:36
|
On Sunday 31 January 2010 06:00:14 pm Daniel Gollub wrote: > On Sunday 31 January 2010 05:44:11 pm Nicolas wrote: > > Ticket #1206 > > > > I can improve (or try) my patch. Ask me what you wa > > > > the patch looks pretty good to me at first glance! > > I'm just running the testsuite with the patch to check if we need to adapt > the testsuite. > Applied with changeset r6027. Looking forward to more flawless patches like this from you! ;) Thanks for your contribution to OpenSync - very appreciated! 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 |
|
From: Daniel G. <go...@b1...> - 2010-01-31 17:00:28
|
Hi Nicolas, On Sunday 31 January 2010 05:44:11 pm Nicolas wrote: > Ticket #1206 > > I can improve (or try) my patch. Ask me what you wa > the patch looks pretty good to me at first glance! I'm just running the testsuite with the patch to check if we need to adapt the testsuite. Thanks a lot for the patch! 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 |
|
From: Nicolas <pr...@fr...> - 2010-01-31 16:44:26
|
Hi, I have open a new ticket : Ticket #1206 I can improve (or try) my patch. Ask me what you want. Regards, Nicolas |
|
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 |
90 messages has been excluded from this view by a project administrator.
