<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Icalendar on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/icalendar/</link>
    <description>Recent content in Icalendar on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/icalendar/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>iCalendar &amp; vCard Libraries in 2026: ical4j vs ical.js vs libical vs ez-vcard</title>
      <link>https://www.pistack.xyz/posts/2026-10-10-icalendar-vcard-libraries-ical4j-icaljs-libical-ezvcard-comparison/</link>
      <pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-10-icalendar-vcard-libraries-ical4j-icaljs-libical-ezvcard-comparison/</guid>
      <description>&lt;p&gt;Calendar synchronisation looks like a solved problem until you ship it. Then you discover that &amp;ldquo;repeat every second Tuesday until December&amp;rdquo; is a recurrence rule with its own grammar, that a recurring event&amp;rsquo;s timezone lives in a &lt;code&gt;VTIMEZONE&lt;/code&gt; block that some clients omit, that an all-day event is a &lt;code&gt;DATE&lt;/code&gt; while a timed event is a &lt;code&gt;DATE-TIME&lt;/code&gt; and mixing them shifts everything by a day, and that one vendor writes vCard 3.0 while another writes 4.0 with the photo embedded as base64 and a third expects a URI.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
