<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>All Day Event Handling from Outlook</title>
  <pubDate>Fri, 04 Jul 2008 17:38:56 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/4487</link>
  <atom:link rel="self" type="application/rss+xml" title="All Day Event Handling from Outlook" href="http://bugs.horde.org/ticket/4487/rss" />
  <description>All Day Event Handling from Outlook</description>

  
  
  <item>
   <title>Quoting Muskingum Web Manager:

&gt; Since using Horde, I've </title>
   <description>Quoting Muskingum Web Manager:

&gt; Since using Horde, I've grown accustomed to the fact that it 
&gt; recognizes All Day appointments as &quot;Start: Day1 12:00am&quot; to &quot;End: Day2 
&gt; 12:00am&quot; (24 Hour Event). However, Outlook (at least, possibly others) 
&gt; recognizes All Day appointments as &quot;Start: Day1 12:00am&quot; to &quot;End: Day1 
&gt; 12:00am&quot;. Horde, of course, only recognizes this as a 0 hour/0 minute
&gt; appointment.
&gt;
&gt; My question/concern is-- what would be involved with allowing Horde to 
&gt; recognize both formats as &quot;All Day&quot; events? Is this something that 
&gt; should be done to accommodate those of us who frequently rely on both?
&gt;
&gt; Aaron Hall

It makes sense to me to do this just for 12am to 12am events (not 6am to 6am, for example). If that sounds right to you, I say go ahead and create an enhancement ticket for it.

-chuck
----------
Yes, that's exactly what I had in mind, Chuck.</description>
   <pubDate>Wed, 04 Oct 2006 15:29:41 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/4487#t24596</link>
  </item>
  

 </channel>
</rss>
