<?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: Raphael</title>
    <description>The latest articles on DEV Community by Raphael (@signorbusi).</description>
    <link>https://dev.to/signorbusi</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%2F4213567%2F4a2d15e8-7a2a-4b83-af86-3a80c7934f3f.png</url>
      <title>DEV Community: Raphael</title>
      <link>https://dev.to/signorbusi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/signorbusi"/>
    <language>en</language>
    <item>
      <title>Ten years of Angular i18n in Swiss finance made me hate translation keys</title>
      <dc:creator>Raphael</dc:creator>
      <pubDate>Tue, 03 Nov 2026 14:00:00 +0000</pubDate>
      <link>https://dev.to/signorbusi/ten-years-of-angular-i18n-in-swiss-finance-made-me-hate-translation-keys-11h9</link>
      <guid>https://dev.to/signorbusi/ten-years-of-angular-i18n-in-swiss-finance-made-me-hate-translation-keys-11h9</guid>
      <description>&lt;p&gt;I've been building frontends for Swiss banks and financial software companies for over ten years. First AngularJS, then Angular, with some React in between. Switzerland has four national languages, so almost every one of these projects had to ship in German, French and English, and often Italian too.&lt;/p&gt;

&lt;p&gt;So I've done a lot of Angular i18n. And I've come to a strong opinion: &lt;strong&gt;translation keys are built for the translation process, not for the developers who have to live with them.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Every project starts the same way
&lt;/h2&gt;

&lt;p&gt;Someone sets up ngx-translate, creates &lt;code&gt;en.json&lt;/code&gt;, and the templates start to look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;h2&amp;gt;&lt;/span&gt;{{ 'PORTFOLIO.OVERVIEW.PERFORMANCE_TITLE' | translate }}&lt;span class="nt"&gt;&amp;lt;/h2&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;button&amp;gt;&lt;/span&gt;{{ 'COMMON.ACTIONS.SAVE' | translate }}&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It feels clean for about two sprints. Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Nobody knows whether &lt;code&gt;PORTFOLIO.OVERVIEW.PERFORMANCE_TITLE&lt;/code&gt; is still used anywhere, so nobody dares to delete it. The JSON files only grow.&lt;/li&gt;
&lt;li&gt;There are three keys with the text "Save", because searching the JSON before adding a key is nobody's favourite activity.&lt;/li&gt;
&lt;li&gt;In code review, the diff shows a key. To know what the user actually sees, you open a second file.&lt;/li&gt;
&lt;li&gt;When a key is missing in one language, the user sees &lt;code&gt;PORTFOLIO.OVERVIEW.PERFORMANCE_TITLE&lt;/code&gt; on the screen.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Angular's built-in i18n is not the escape
&lt;/h2&gt;

&lt;p&gt;I like that the &lt;code&gt;i18n&lt;/code&gt; attribute keeps the text in the template. That part is right. But then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;ng extract-i18n&lt;/code&gt;, XLF files, and a merge step every time the text changes.&lt;/li&gt;
&lt;li&gt;Generated message IDs change when the text changes, so you start adding &lt;code&gt;@@custom-ids&lt;/code&gt;. Congratulations, you have translation keys again.&lt;/li&gt;
&lt;li&gt;One build per locale. Switching the language means loading a different app.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a public website that might be acceptable. For an internal dashboard where a portfolio manager switches between German and English, it's a lot of build pipeline for very little.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shared component libraries make it worse
&lt;/h2&gt;

&lt;p&gt;At one company I helped build a shared Angular component library used by several projects. The components had their own texts: "No results", "Show more", validation messages, table paging.&lt;/p&gt;

&lt;p&gt;Who owns those translations? The library, so every app inherits texts it can't change? Or every app, so every consumer has to provide the same 40 keys? We went back and forth on this more than on any actual component.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real cost is waiting
&lt;/h2&gt;

&lt;p&gt;In a bank, a new text is rarely just a new text. The developer adds the key with the English value. Then someone has to provide French and Italian, ideally someone from the business side who knows the domain terms. Until that happens, the feature is done, tested, and can't be released.&lt;/p&gt;

&lt;p&gt;The irony: most of these screens were internal tools used by a few dozen specialists.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I do now
&lt;/h2&gt;

&lt;p&gt;When I started my side project &lt;a href="https://chordpic.com" rel="noopener noreferrer"&gt;ChordPic&lt;/a&gt;, I didn't want any of this. So the text just stays in the template, gets translated by AI, and the result is cached. When users asked for their language, adding it was one line, and it was live the same day.&lt;/p&gt;

&lt;p&gt;That turned into &lt;a href="https://magictranslate.io" rel="noopener noreferrer"&gt;Magic Translate&lt;/a&gt;, and it has an Angular client:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// app.config.ts&lt;/span&gt;
&lt;span class="nf"&gt;provideMagicTranslate&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;apiKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;YOUR_API_KEY&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;language&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;de&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;h2&amp;gt;&amp;lt;t&amp;gt;&lt;/span&gt;Portfolio performance&lt;span class="nt"&gt;&amp;lt;/t&amp;gt;&amp;lt;/h2&amp;gt;&lt;/span&gt;

&lt;span class="nt"&gt;&amp;lt;p&amp;gt;&amp;lt;t&amp;gt;&lt;/span&gt;Positions are revalued at &lt;span class="nt"&gt;&amp;lt;b&amp;gt;&lt;/span&gt;market close&lt;span class="nt"&gt;&amp;lt;/b&amp;gt;&lt;/span&gt;.&lt;span class="nt"&gt;&amp;lt;/t&amp;gt;&amp;lt;/p&amp;gt;&lt;/span&gt;

&lt;span class="nt"&gt;&amp;lt;input&lt;/span&gt; &lt;span class="na"&gt;[placeholder]=&lt;/span&gt;&lt;span class="s"&gt;"'Search positions' | t"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it. No keys, no JSON files, and the diff in code review shows exactly what the user will read. And because this is Switzerland, &lt;code&gt;formality: 'formal'&lt;/code&gt; is one option away. Nobody wants their bank to call them "du".&lt;/p&gt;

&lt;h2&gt;
  
  
  The tricky part: values in the text
&lt;/h2&gt;

&lt;p&gt;One of the challenges with translating plain text is that real UI text is full of values. "Hi Anna, you have 3 new alerts" and "Hi Marco, you have 5 new alerts" are different strings. Translate them as they are, and every name and every count is a new translation: slower, more expensive, and nothing gets reused from the cache.&lt;/p&gt;

&lt;p&gt;The fix is to tell Magic Translate which parts are values. In Angular you pass them in &lt;code&gt;[v]&lt;/code&gt; and reference them with &lt;code&gt;$name&lt;/code&gt; in the text:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;t&lt;/span&gt; &lt;span class="na"&gt;[v]=&lt;/span&gt;&lt;span class="s"&gt;"{ name: user.name, count: alerts().length }"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  Hi $name, you have $count new alerts
&lt;span class="nt"&gt;&amp;lt;/t&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What gets translated is the template, &lt;code&gt;Hi {0}, you have {1} new alerts&lt;/code&gt;. It's translated once and cached, whatever the values are, and the values themselves never leave the browser. The translation can also move the placeholders to wherever the other language needs them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I would still use keys
&lt;/h2&gt;

&lt;p&gt;To be fair, I wouldn't use this for everything:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Legally binding text.&lt;/strong&gt; Contracts, regulatory disclosures, anything compliance has to sign off string by string. You can edit translations by hand in the dashboard, but if every string needs a formal review, a classic workflow with translators is the right tool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Teams with professional translators.&lt;/strong&gt; If translators are already part of your process, keys and translation files are what their tools expect.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But for the internal tools, dashboards and side projects that make up most of what I've built? Keys were never worth it.&lt;/p&gt;

&lt;h2&gt;
  
  
  So, what's your setup?
&lt;/h2&gt;

&lt;p&gt;Are you on ngx-translate, Transloco, the built-in &lt;code&gt;i18n&lt;/code&gt;, or something else? And has a raw translation key ever made it to production on your watch?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I built Magic Translate. It has a free tier at &lt;a href="https://magictranslate.io" rel="noopener noreferrer"&gt;magictranslate.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>angular</category>
      <category>i18n</category>
      <category>webdev</category>
      <category>typescript</category>
    </item>
    <item>
      <title>There are countless i18n tools. I built another one anyway.</title>
      <dc:creator>Raphael</dc:creator>
      <pubDate>Wed, 28 Oct 2026 17:45:01 +0000</pubDate>
      <link>https://dev.to/signorbusi/there-are-countless-i18n-tools-i-built-another-one-anyway-2eih</link>
      <guid>https://dev.to/signorbusi/there-are-countless-i18n-tools-i-built-another-one-anyway-2eih</guid>
      <description>&lt;p&gt;I have a day job as a software engineer at a bank. In the evenings, I build my own things. One of them is ChordPic, a small tool for making guitar chord diagrams. People from all over the world started using it, and at some point I wanted it to speak their language.&lt;/p&gt;

&lt;p&gt;I knew exactly what that would mean. At work, I've used the usual i18n libraries in more than one app, and I didn't want to bring any of that into a project I build in my free time.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part nobody puts in the README
&lt;/h2&gt;

&lt;p&gt;If you've done this, you know the drill. Every piece of text in your app turns into a key. &lt;code&gt;"Create chord chart"&lt;/code&gt; becomes &lt;code&gt;t('editor.toolbar.create')&lt;/code&gt;. The actual sentence moves to &lt;code&gt;en.json&lt;/code&gt;. Then you copy &lt;code&gt;en.json&lt;/code&gt; to &lt;code&gt;de.json&lt;/code&gt;, &lt;code&gt;fr.json&lt;/code&gt;, &lt;code&gt;es.json&lt;/code&gt;, and so on, and you get them translated somehow.&lt;/p&gt;

&lt;p&gt;And then you keep shipping.&lt;/p&gt;

&lt;p&gt;You change a button label, and now eleven files are out of date. You add a feature and forget one key in one language, and someone in Brazil sees &lt;code&gt;editor.toolbar.share_tooltip&lt;/code&gt; on their screen. You open a component and can't read it anymore, because all the words are gone, replaced by dotted paths. You spend an evening on a "quick" copy change and most of it goes into JSON files.&lt;/p&gt;

&lt;p&gt;For a big company with a localization team, maybe that's fine. For one person working evenings, it was the reason I kept putting off translating at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I actually wanted
&lt;/h2&gt;

&lt;p&gt;What I wanted was simple: write my app in English, the way I always do, and have it show up in other languages. No keys. No files to keep in sync. If I change a sentence, every language should follow.&lt;/p&gt;

&lt;p&gt;So in December 2022 I started building it for myself. That became &lt;a href="https://magictranslate.io" rel="noopener noreferrer"&gt;Magic Translate&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It works like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;T&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@magic-translate/react&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Toolbar&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;T&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Create chord chart&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;T&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's the whole idea. The text stays in your component. Magic Translate translates it with AI the first time it's seen, caches it, and serves the cached version after that. Change the sentence, and it gets translated again. Adding a new language is a single line of code, instead of translating hundreds of keys.&lt;/p&gt;

&lt;p&gt;Along the way it grew into something I'm honestly proud of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It renders translations on the server for Next.js and React Server Components, so search engines see real translated pages, not English that gets swapped out later.&lt;/li&gt;
&lt;li&gt;There are clients for React, Vue, Angular and plain JavaScript.&lt;/li&gt;
&lt;li&gt;If you don't like a translation, you can override it by hand and your override wins.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;ChordPic now runs in 13 languages, including Arabic, Hindi, Persian and Chinese. I didn't write a single translation file for it. When I change some text on the site, I don't think about languages at all anymore. That still feels a bit like magic to me, which is where the name came from.&lt;/p&gt;

&lt;p&gt;My favorite moments are when a ChordPic user writes to me and asks for their language. I add one line, and it's live in production the same day. Seeing someone's reply when the thing they asked for in the morning is there by the evening never gets old.&lt;/p&gt;

&lt;h2&gt;
  
  
  And then I tried to tell people about it
&lt;/h2&gt;

&lt;p&gt;This is the part I didn't expect to be the hard one.&lt;/p&gt;

&lt;p&gt;Search for "react i18n" and count the libraries. Then the translation management platforms. Then the "AI translation for your app" startups that seem to launch every week. The space is incredibly crowded. Whenever I post about Magic Translate, it disappears into that sea within a day. To a stranger scrolling past, it looks like one more i18n tool, and I get why. I'd scroll past it too.&lt;/p&gt;

&lt;p&gt;But here's the thing I keep coming back to. If there are this many solutions, the problem isn't solved. Nobody builds the hundredth library for something that already works well. Every new i18n tool exists because somebody, somewhere, got as fed up with key files as I did. The sheer number of options isn't a sign that the space is done. It's a sign that developers are still looking.&lt;/p&gt;

&lt;p&gt;I believe the answer is to stop making developers manage translations at all. I might be wrong about that. But I've been using it in production for years now, and I'm not going back.&lt;/p&gt;

&lt;h2&gt;
  
  
  So, a question for you
&lt;/h2&gt;

&lt;p&gt;I'm good at building things. I'm clearly not good at getting them seen. So I'd love to hear from you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do you deal with translations in your apps today? What annoys you most?&lt;/li&gt;
&lt;li&gt;If you've launched a developer tool into a crowded space, what actually worked for you?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And if you're curious, try it on a side project and tell me what's wrong with it: &lt;a href="https://magictranslate.io" rel="noopener noreferrer"&gt;magictranslate.io&lt;/a&gt;. There's a free plan, and I read every message I get.&lt;/p&gt;

&lt;p&gt;Thanks for reading.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>i18n</category>
      <category>react</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
