From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Spiers <orgmode@adamspiers.org>
Subject: Re: Re: iCal export of repeated tasks
Date: Fri, 13 Jun 2008 15:16:02 +0100
Message-ID: <20080613141602.GI26718@atlantic.linksys.moosehall>
References: <20080613120135.GD8066@atlantic.linksys.moosehall>
	<87y7594hp2.fsf@gmail.com>
	<20080610101715.GF5498@atlantic.linksys.moosehall>
	<F1041FFA-7B5E-46C3-BD5D-B0F5A2C499D5@uva.nl>
	<20080612100559.GE19396@atlantic.linksys.moosehall>
	<EDCE1F04-B131-47E8-B43D-6601649DEF60@uva.nl>
	<20080612114705.GG19396@atlantic.linksys.moosehall>
	<A1A608FA-C9C7-4EDA-9F16-D22F5E55A1F9@uva.nl>
	<20080613092409.GA8066@atlantic.linksys.moosehall>
	<878wx964mw.fsf@gmail.com>
Reply-To: Adam Spiers <orgmode@adamspiers.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K7A4W-0001Ci-5f
	for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 10:16:08 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K7A4U-0001CK-0w
	for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 10:16:07 -0400
Received: from [199.232.76.173] (port=56578 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K7A4T-0001CH-Rs
	for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 10:16:05 -0400
Received: from mail.beimborn.com ([70.84.38.100]:41274)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <f5-sendmail@adamspiers.org>) id 1K7A4T-0006af-I5
	for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 10:16:05 -0400
Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1])
	by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id
	m5DEG4Bn026259
	for <emacs-orgmode@gnu.org>; Fri, 13 Jun 2008 09:16:04 -0500
Received: from localhost (localhost [[UNIX: localhost]])
	by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id
	m5DEG426026251
	for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 15:16:04 +0100
Content-Disposition: inline
In-Reply-To: <87y7594hp2.fsf@gmail.com> <878wx964mw.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: org-mode mailing list <emacs-orgmode@gnu.org>

On Fri, Jun 13, 2008 at 11:55:19AM +0200, Paul R wrote:
> [...] you can maybe implement a "go-between" layer that
> takes iCal file in input, and outputs the same iCal file with repeated
> events changed to dated events, with date set on next occurence.

On Fri, Jun 13, 2008 at 02:56:09PM +0200, Paul R wrote:
> This is a good use-case, and once again, I consider org export should
> provide full information, and later a convert tools should
> degrade/adapt it to the target software or device. Implementing such a
> processing in every calendaring tools would be a massive duplication.
> The "iCal to iCal" converter is the way to go, IMO.

I see your point.  The main disadvantage is that it doesn't work if
you want to apply the filter to the view in the client which
originally generated the iCal from the "master" event data (in our
case, org-mode) - you'd have to export it, pass it through the filter,
then reimport it ...