<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>I18n on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/i18n/</link>
    <description>Recent content in I18n on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/i18n/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DateTime Parsing Libraries: dateparser vs Chrono vs Joda-Time vs python-dateutil (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-self-hosted-datetime-parsing-libraries-dateparser-chrono-jodatime-dateutil/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-self-hosted-datetime-parsing-libraries-dateparser-chrono-jodatime-dateutil/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every self-hosted service that ingests data from external sources eventually confronts the datetime parsing problem. RSS feeds use RFC 2822. API responses use ISO 8601. Log files use whatever format the developer chose in 2008. User input arrives as &amp;ldquo;next Tuesday at 3pm&amp;rdquo; or &amp;ldquo;2026年6月20日&amp;rdquo;. A single misparsed date can cascade into missed alerts, duplicate billing cycles, or corrupted analytics. In a self-hosted data ingestion pipeline processing 100,000 documents per hour, even a 0.1% date parsing error rate means 100 corrupted records every hour.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
