<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: GTE LOCALIZE</title>
    <description>The latest articles on DEV Community by GTE LOCALIZE (@gtelocalize).</description>
    <link>https://dev.to/gtelocalize</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4229649%2F09809b27-b976-4492-bc16-9d02b7295cd2.jpg</url>
      <title>DEV Community: GTE LOCALIZE</title>
      <link>https://dev.to/gtelocalize</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gtelocalize"/>
    <language>en</language>
    <item>
      <title>Five i18n Bugs We Keep Finding in Real Projects (and How to Catch Them Early)</title>
      <dc:creator>GTE LOCALIZE</dc:creator>
      <pubDate>Mon, 16 Nov 2026 02:49:28 +0000</pubDate>
      <link>https://dev.to/gtelocalize/five-i18n-bugs-we-keep-finding-in-real-projects-and-how-to-catch-them-early-253n</link>
      <guid>https://dev.to/gtelocalize/five-i18n-bugs-we-keep-finding-in-real-projects-and-how-to-catch-them-early-253n</guid>
      <description>&lt;p&gt;Most localization problems are not translation problems. They are engineering problems that only become visible once a second language shows up. Here are five bugs that keep appearing in real projects, with a way to catch each one before release.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Strings glued together in code
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Looks harmless&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;msg&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"You have "&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;count&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s2"&gt;" new "&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;count&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="s2"&gt;"message"&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"messages"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Word order, plural rules and grammatical gender differ by language, so concatenation cannot be translated. Use a message format that carries the whole sentence and the plural rules:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"inbox.new"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{count, plural, one {You have # new message} other {You have # new messages}}"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Languages such as Arabic and Polish have more plural categories than English, so the format must allow them.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Layouts that assume English length
&lt;/h2&gt;

&lt;p&gt;German and Finnish strings are often much longer than English ones. A fixed-width button that fits "Submit" will clip a longer equivalent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to catch it:&lt;/strong&gt; use pseudo-localization in development. Replace every string with a longer, accented version such as &lt;code&gt;[Ŝûbmîţţţ]&lt;/code&gt; so truncation, hardcoded widths and missing glyphs show up immediately, before any translator is involved.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Hardcoded formats
&lt;/h2&gt;

&lt;p&gt;Dates, numbers and currencies are formatted differently around the world. &lt;code&gt;1,250.50&lt;/code&gt; is &lt;code&gt;1.250,50&lt;/code&gt; in much of Europe, and &lt;code&gt;03/04/2026&lt;/code&gt; is ambiguous without a locale.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Intl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;NumberFormat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"de-DE"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;style&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"currency"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;currency&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"EUR"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;format&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mf"&gt;1250.5&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="c1"&gt;// "1.250,50 €"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use the platform's locale APIs rather than string manipulation, and store dates in an unambiguous format such as ISO 8601.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Right-to-left as an afterthought
&lt;/h2&gt;

&lt;p&gt;Arabic and Hebrew need more than text direction. Layout, icons that imply direction and mixed-direction text all behave differently. Prefer logical CSS properties over left and right:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.card&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;margin-inline-start&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1rem&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nl"&gt;padding-inline-end&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.5rem&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then test with real RTL content, not just a flipped screenshot.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Strings without context
&lt;/h2&gt;

&lt;p&gt;A translator who sees only &lt;code&gt;"Book"&lt;/code&gt; cannot know whether it is a noun or a verb. Add a short description or screenshot to every key, and keep keys stable so translation memory keeps working.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"reservation.cta"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Book"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Button label: reserve a table"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  A quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No concatenated sentences&lt;/li&gt;
&lt;li&gt;Plural-aware message format&lt;/li&gt;
&lt;li&gt;Pseudo-localization in CI&lt;/li&gt;
&lt;li&gt;Locale APIs for dates, numbers and currencies&lt;/li&gt;
&lt;li&gt;Logical CSS properties&lt;/li&gt;
&lt;li&gt;Context for every key&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  About this series
&lt;/h2&gt;

&lt;p&gt;We are a localization team and we will keep writing short, practical posts like this one about the engineering side of shipping in many languages. Comments and corrections are welcome.&lt;/p&gt;

</description>
      <category>i18n</category>
      <category>webdev</category>
      <category>localization</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
