<?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 Pierre-Henry Soria – CTO Insights, Software Architecture &amp; Product Leadership</title><link>https://blog.pierrehenry.be/tags/i18n/</link><description>Recent content in I18n on Pierre-Henry Soria – CTO Insights, Software Architecture &amp; Product Leadership</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Pierre-Henry Soria.</copyright><lastBuildDate>Sat, 22 Aug 2026 03:30:00 +1000</lastBuildDate><atom:link href="https://blog.pierrehenry.be/tags/i18n/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Internationalize a Web Product Without a Translation Widget</title><link>https://blog.pierrehenry.be/blog/how-i-internationalize-a-web-product-without-a-translation-widget/</link><pubDate>Sat, 22 Aug 2026 03:30:00 +1000</pubDate><guid>https://blog.pierrehenry.be/blog/how-i-internationalize-a-web-product-without-a-translation-widget/</guid><description>A translation widget does not create a multilingual product. URLs, content, formats, accessibility, and search discovery need one coherent implementation.</description></item></channel></rss>