From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Engster Subject: Re: org-caldav: New version with proper two-way sync Date: Wed, 16 Jan 2013 22:45:13 +0100 Message-ID: <87ip6w3iqe.fsf@engster.org> References: <87bocr4ej2.fsf@engster.org> <877gnd4wcv.fsf@ucl.ac.uk> <8738y14tv5.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59112) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvanY-0003aV-Gz for emacs-orgmode@gnu.org; Wed, 16 Jan 2013 16:46:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TvanO-0005A3-Jv for emacs-orgmode@gnu.org; Wed, 16 Jan 2013 16:45:28 -0500 Received: from randomsample.de ([83.169.19.17]:49907) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvanO-00057e-6w for emacs-orgmode@gnu.org; Wed, 16 Jan 2013 16:45:18 -0500 Received: from dslc-082-082-160-140.pools.arcor-ip.net ([82.82.160.140] helo=spaten) by randomsample.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1TvanL-0002YP-MJ for emacs-orgmode@gnu.org; Wed, 16 Jan 2013 22:45:15 +0100 In-Reply-To: <8738y14tv5.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 16 Jan 2013 15:17:10 +1030") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Emacs Org mode mailing list Eric S. Fraga writes: > I've tracked down the root of the various problems I have encountered > with the synchronisation. It all comes down to character sets. I > have some entries that have UTF-8 characters that are not present in > ASCII, specifically accented characters and similar (latin1, > basically, but not exclusively). Any such entries cause the > synchronisation to fail. Could you post an example entry where this happens? > Resuming a failed synchronisation seems to forget to try to bring in > the external calendar entries into org? That happens last, so I wouldn't know why this would be skipped on resume. It's kinda hard to debug, though. > The fact that descriptions are not synchronised for changed entries is > something I understand but probably need to think about some more (in > terms of default behaviour). Is there a practical limitation on the > size of the description entry that could be synchronised? The default > is 100 but would there be any harm in having this 1, 2 or even 3 > orders of magnitude larger? Or even unlimited? Just wondering. I was wondering about that, too, but couldn't find any definite statements on the maximum length of the DESCRIPTION field. I only skimmed RFC 2445, though. Even if there is such a definite limit, I wouldn't count on servers to correctly implement that. I guess you just have to try what works. > Anyway, with respect to my problems, would you please have a look to > see if you are assuming ASCII or similar and whether there is anything > you can do about this? I (and many others, I assume) really do need > to be able to work in UTF-8 at the very least. I will look into that. I'm pretty sure this is fixable. -David