<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gettext on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gettext/</link>
    <description>Recent content in Gettext on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gettext/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Internationalization in 2026: go-i18n vs gotext vs golang.org/x/text</title>
      <link>https://www.pistack.xyz/posts/2026-10-31-go-i18n-libraries-go-i18n-gotext-x-text/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-31-go-i18n-libraries-go-i18n-gotext-x-text/</guid>
      <description>&lt;p&gt;Adding a second language to a Go service looks like a two-hour task until you hit plural rules. English has two forms, Polish has four, Arabic has six, and Japanese has one — and the moment a product manager asks for &amp;ldquo;3 pliki&amp;rdquo; versus &amp;ldquo;5 plików&amp;rdquo; you discover that &lt;code&gt;fmt.Sprintf&lt;/code&gt; with an &lt;code&gt;if count == 1&lt;/code&gt; branch is not an internationalization strategy. Go has no blessed answer in the standard library; there are three credible packages and they disagree about almost everything: message format, translation workflow, and who owns plural logic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
