Re: base64 encoding
Christian Mollekopf <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | Kolab Systems AG |
| Message-ID | <1413681.O6AHJsbEDY__40720.9197561771$1361269117$gmane$org@myhost2> |
On Friday 15 February 2013 11.35:37 Mihai Badici wrote: > When testing synkolab I encountered an issue we discussed in a previous > thread. > > In fact, contacts modified in thunderbird are transfered in kolab v3 format > but base 64 encoded: > > > --Boundary-00=EE071EE390D7733C > Content-Type: application/vcard+xml; > name="kolab.xml" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename="kolab.xml" > > > There are not decrypted nor in roundcube or kontact; > So the question is: base64 can be considered as valid encoding for kolab > objects? That is currently not supported, see http://wiki.kolab.org/Kolab_3.0_Storage_Format#XML_Object_Part We may improve that though if there are good reasons to use base64 over quoted-printable. Cheers, Christian -- Christian Mollekopf Software Engineer Kolab Systems AG Zürich, Switzerland e: [email protected] w: http://kolabsys.com pgp: EA657400 Christian Mollekopf _______________________________________________ Kolab-devel mailing list [email protected] https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEABECAAYFAlEjUVYACgkQF4TVOOpldAAzjACeKp21hxqj5Mvo6zFD8pER4Rr6 u+UAnja9WRPTuJDNiNdUM3LRlmmLUMt8 =YC8i -----END PGP SIGNATURE-----