<?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 Washington Botelho</title><link>http://www.wbotelhos.com/tags/i18n/</link><description>Recent content in i18n on Washington Botelho</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 29 Jul 2021 00:00:00 -0300</lastBuildDate><atom:link href="http://www.wbotelhos.com/tags/i18n/index.xml" rel="self" type="application/rss+xml"/><item><title>I18n With Phoenix</title><link>http://www.wbotelhos.com/i18n-with-phoenix/</link><pubDate>Thu, 29 Jul 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/i18n-with-phoenix/</guid><description>It&amp;rsquo;s a good idea to translate your texts, even if you&amp;rsquo;ll display your site only in one language. With this technique, the texts will be centralized in only one place and you can separate them by domains. Phoenix uses gettext to do the translation and we&amp;rsquo;ll see how to do that.
Goal Translate and understand how translation in Phoenix works.
Setup Let&amp;rsquo;s create a Phoenix project:
mix phx.new i18n_with_phoenix cd i18n_with_phoenix mix deps.</description></item></channel></rss>