<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sunil Gupta on Medium]]></title>
        <description><![CDATA[Stories by Sunil Gupta on Medium]]></description>
        <link>https://medium.com/@nsit.sunilgupta?source=rss-d02de710055e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wv-vVCrYq9i_mdWLWORs7Q.jpeg</url>
            <title>Stories by Sunil Gupta on Medium</title>
            <link>https://medium.com/@nsit.sunilgupta?source=rss-d02de710055e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:26:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nsit.sunilgupta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building For Vernacular: Challenges and Opportunities]]></title>
            <link>https://medium.com/sheroes-tech/building-for-vernacular-challenges-and-opportunities-605633d2d12d?source=rss-d02de710055e------2</link>
            <guid isPermaLink="false">https://medium.com/p/605633d2d12d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Sunil Gupta]]></dc:creator>
            <pubDate>Wed, 28 Nov 2018 10:46:38 GMT</pubDate>
            <atom:updated>2018-11-29T06:31:49.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NexWC6yyksR15Gwe1x_-HA.jpeg" /></figure><p>Nowadays people speak about 3–4 languages including their mother tongue and English but knowing a language isn’t the same as preferring or even using it. In a developing country like India, where a huge population is not still comfortable with English, it is a huge challenge to reach the masses with diverse language backgrounds, to make them aware and literate about the new products.</p><p>In this era of globalization, we have to ensure the best services should be available to all. We believe that language is a medium of expression of knowledge. We are committed to serving even the remotest parts of the country. To achieve this goal we felt the necessity to make our products available in multiple languages.</p><h4><strong>Challenges that we overcame</strong></h4><p>Initially, as SHEROES was not designed to provide multilingual support, making the content accessible in multiple languages was a challenging task. There were a set of problems before us to serve content into multiple languages like selecting or making our existing database conducive to support multiple languages, modifying SHEROES’ existing architecture, content translation, string formation, handling creatives for different languages, static data, and hardcoded strings.</p><h4><strong>Handling dynamic data</strong></h4><p>We started with modification of our database and selected a design which would suit our system and fulfil our needs.</p><p>We made a mirror of our existing tables which would store data in row format for multiple languages. For every table, take out all localizable columns into a corresponding new table &lt;name&gt;_Translations which contains a unique id and a language column.</p><p>For every unique id, there will be multiple rows, one for each language.</p><p>The original table will join on this table on unique_id to fetch the data for the desired language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/0*lPjSmz_0sALCDzz2" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*Te1_h4oT7AW7di7Vx2cdfA.png" /></figure><p>So here we created a translation community_translations table for parent table community which contains the translated data. The translation table in which community_id remains the same for a field value in any translated language. A composite primary unique key community_id, language (this is an enum type column) is stored in the translation table, and it stores the same translation_id i.e. id for each field against multiple languages.<br>We follow a similar approach for our other tables.</p><p>We marked every content generated by the user with language tag and it stored in the single bucket i.e. table so that we could easily separate them while retrieving.</p><h4>Advantages</h4><p>There are multiple benefits to using this approach:</p><ol><li>It allows for easy retrieval of data.</li><li>Easy deletes, inserts, completely flexible and simple adding support for new languages</li><li>It can fetch the required language data without having to deal with other language data.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZLknpHyap4BK4lZNpZpoQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*UEKYfZ5RRibknl56ynXVcA.jpeg" /></figure><h4><strong>Things to take care while building for vernacular languages</strong></h4><ol><li>You can use language as enum instead of ids like ‘en’ for English and ‘hi’ for Hindi, would ensure both read-ability and avoid one extra join.</li><li>A fallback mechanism should be present if language content could not be fetched.</li><li>One should not modify language when a user edits the content and it should be only marked while creating the content.</li><li>Avoid hard-coding for static content, as this would be a blocker when adding new languages.</li><li>We converted our content into a utf8mb4 character set (4-Byte UTF-8 Unicode Encoding) for persisting in the MySQL database. Similarly, you’d also need to ensure that your database supports the full unicode character set.</li></ol><h4><strong>Conclusion</strong></h4><p>Given the high scalability of this approach, we went ahead despite its limitations. The best part about this approach is that we were able to implement all these changes in merely three weeks.</p><p>Handling Right-to-Left (RTL) language systems, localization, and internationalization based on geolocation are few other projects in the pipeline. We are excited about future possibilities like an end to end translation of user-generated content and much more.</p><p>The road ahead is long and we’re learning and growing as we take each step further. Come help us scale faster as we expand and bring out new features. Check out <a href="https://angel.co/sheroes-2/jobs">here</a> for more.</p><p><a href="https://www.youtube.com/user/sheroesindia/videos">YouTube Channel</a> | <a href="http://twitter.com/sheroesindia">Twitter</a> |<a href="http://facebook.com/sheroesindia">Facebook</a> |<a href="https://www.linkedin.com/company/fleximoms/">LinkedIn</a> | <a href="https://www.instagram.com/sheroesindia">Instagram</a> |<a href="https://sheroes.tech/">SHEROES</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/269/1*UAzWQYrrmeWDSNkxPrT0iw.png" /></figure><p><strong><em>The SHEROES women’s community platform is a safe, high-trust, high empathy space where women engage everyday around all aspects of their growth journey via </em></strong><a href="https://sheroes.com/"><strong><em>Sheroes.com</em></strong></a><strong><em> and the </em></strong><a href="https://shrs.me/ijH6O8qrOO"><strong><em>SHEROES app</em></strong></a><strong><em>.</em></strong></p><p>Thank You for reading! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=605633d2d12d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sheroes-tech/building-for-vernacular-challenges-and-opportunities-605633d2d12d">Building For Vernacular: Challenges and Opportunities</a> was originally published in <a href="https://medium.com/sheroes-tech">SHEROES</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>