<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Localization on Uday K</title><link>https://uday.dev/tags/localization/</link><description>Recent content in Localization on Uday K</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 21 Feb 2021 16:14:59 -0400</lastBuildDate><atom:link href="https://uday.dev/tags/localization/index.xml" rel="self" type="application/rss+xml"/><item><title>Simplifying Globalization: The Power of Standalone Localization Repositories</title><link>https://uday.dev/posts/localization/</link><pubDate>Sun, 21 Feb 2021 16:14:59 -0400</pubDate><guid>https://uday.dev/posts/localization/</guid><description>&lt;p&gt;In today&amp;rsquo;s globalized world, catering to a diverse audience is essential for businesses. To effectively serve localized content to users across the globe, it&amp;rsquo;s crucial to streamline the localization process. This blog post explores a practical solution by pulling out localization files from your project and placing them in a standalone repository. We&amp;rsquo;ll focus on using Rails project conventions for simplicity reasons.&lt;/p&gt;&#10;&lt;h2 id="motivation"&gt;Motivation&lt;/h2&gt;&#10;&lt;p&gt;Leading a significant feature in a shared code base often leads to the creation of a Long Standing Changelist (LSC). In such cases, translation files tend to be rapidly evolving due to other team members working on smaller fixes and features. This can become a major headache when merging changes with the upstream codebase.&lt;/p&gt;</description></item></channel></rss>