This means that you can use Gettext.put_locale/2 in a new process in order to change the locale for that process. One more thing, Gettext stores the locale per-process (in the process dictionary) and per Gettext module. The tasks will be responsible for creating the files for this domain.
To use a custom domain, use: dgettext "errors", "Here is an error message to translate". Ecto uses a custom domain called errors for validations. All your translations will be stored in the default domain. You can create domains to scope assess your translations.
#ELIXIR ECTO LONG TEXT PORTABLE#
POT means Portable Object Template and these files are generated automatically by: mix gettext.extractĪ new Phoenix project already has a gettext call in the web/template/pages/ with <%= gettext "Welcome to %" For now, we have only the file errors that are used by Ecto. Gettext uses two kinds of files: *.po and *.pot. Before, let’s take a look at the Gettext structure when we start a new Phoenix project.
#ELIXIR ECTO LONG TEXT HOW TO#
In this post, we will show you how we did that and how to translate effectively your app when the time comes in the future by running two tasks. Given those benefits, we have decided to tag already our strings with gettext calls, saving us from future work without a loss in productivity or maintainability. We maintained applications in the past that relied heavily on “ssage” strings and the extra level of indirection was always hard to work with. We can translate our applications without losing context since we keep the original text. Using gettext is a single step as it will use the given string if no translation is available The first was to use “view.welcome” in our templates and then add the translated string to a configuration file. When using “view.welcome” strings, it always required two steps from developers.We have noticed this approach comes with two large benefits: For example, instead of specifying translations as keys, as in translate "view.welcome", we simply use the gettext "Hello there!" function for every string in the app. The idea behind Gettext is that it translates messages based on the string itself and not on “keys”. Gettext is a tool for writing multilingual programs used as a standard by many communities, meaning there is a great set of tooling for developers and translators. The Phoenix framework ships with internationalization (i18n) and localization (l10n) system called Gettext since version 1.1.
Even though internationalizing our application is planned a bit ahead in our roadmap, we have decided to do an initial evaluation of the translation tools in the Elixir ecosystem, and we were pleasantly surprised by what it has to offer. To translate or not to translate? We have been asking ourselves the same question in one of our latest Phoenix projects. Using Gettext to internationalize a Phoenix application Mar 15, 2016
0 kommentar(er)
