All Versions
29
Latest Version
Avg Release Cycle
108 days
Latest Release
-
Changelog History
Page 2
Changelog History
Page 2
-
v0.17.0 Changes
June 24, 2019- Require Elixir 1.6 and later
- Add stats reporting when merging PO files
-
v0.16.1 Changes
November 13, 2018- Optimize default locale lookup
-
v0.16.0 Changes
August 31, 2018- Fix bugs related to expanding arguments to Gettext macros
- Fix a bug where you couldn't have filenames with colons in them in reference comments
- Add
handle_missing_translation/4
andhandle_missing_plural_translation/6
callbacks to Gettext backends - Fix a bug in
mix gettext.extract
, which was ignoring the--merge
option
-
v0.15.0 Changes
February 19, 2018- Generate correct plural forms when dumping new messages in PO files
- Fix a bug where we were losing translator comments for fuzzy-merged messages
- Don't make an exact match when merging prevent later fuzzy matches
- Allow multiple messages to fuzzy-match against the same message when merging
- Bump the Elixir requirement to v1.4 and on
-
v0.14.1 Changes
February 14, 2018- ๐ Copy flags from existing translations when merging translations
-
v0.14.0 Changes
December 10, 2017- Introduce a global locale (per-process) for all Gettext backends
- Warn when compiling and raise at runtime for missing plural forms
- Separate flags with commas when dumping and parsing .pot files
- Add support for extracted comments via
gettext_comment/1
- Require Elixir v1.3 and fix warnings
- Improve compilation time of Gettext backends in roughly 20%
- Add
:one_module_per_locale
for parallel compilation of backends (requires Elixir v1.6) - Use the
elixir-format
flag to mark autogenerated messages
-
v0.13.1 Changes
January 30, 2017- Fix a bug with Dialyzer specs for the
Gettext.Backend.ngettext_noop/2
callback - Parse
msgctxt
entries in PO and POT files so that they don't cause syntax errors, but ignore them in the parsed result
- Fix a bug with Dialyzer specs for the
-
v0.13.0 Changes
December 12, 2016- Add the
gettext_noop/1
,dgettext_noop/2
,ngettext_noop/3
, anddngettext_noop/4
macros to Gettext backends. These macros can be used to mark messages for extractions without translating the given string
- Add the
-
v0.12.2 Changes
February 14, 2018- Fix a bug where we failed miserably with a "no process" error when
extracting messages without having the
:gettext
compiler run - Slightly revisit the indentation of subsequent literal strings in dumped PO(T) files; before, they were dumped one per line, indented one level more than the parent message, while now they're indented at the same level as the parent message
- Fix a bug where we failed miserably with a "no process" error when
extracting messages without having the
-
v0.12.1 Changes
- Ensure the Gettext application is started before running Mix tasks