<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Internationalization on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/internationalization/</link>
    <description>Recent content in Internationalization 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/internationalization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unicode Text Encoding &amp; Character Detection Libraries: ICU4C vs simdutf vs encoding_rs vs uchardet</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-unicode-encoding-libraries-icu4c-simdutf-encoding-rs-uchardet/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-unicode-encoding-libraries-icu4c-simdutf-encoding-rs-uchardet/</guid>
      <description>&lt;h2 id=&#34;why-text-encoding-still-matters-in-2026&#34;&gt;Why Text Encoding Still Matters in 2026&lt;/h2&gt;&#xA;&lt;p&gt;Unicode is the universal standard for text representation, but the underlying encoding libraries that handle conversion between UTF-8, UTF-16, UTF-32, and legacy encodings are often overlooked until they become a bottleneck or a source of bugs. When your application processes user-submitted text from browsers, parses CSV files with unknown encodings, or handles CJK (Chinese-Japanese-Korean) text at scale, the encoding library you choose directly impacts correctness, performance, and memory usage.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
